Fix brainstorming-to-planning handoff using EnterPlanMode instead of writing-plans

EnterPlanMode's system prompt guidance fires every turn while skill content
loaded early in conversation fades in context. Three fixes:
- Add EnterPlanMode to using-superpowers red flags table (refreshed every turn)
- Make brainstorming handoff imperative: invoke Skill tool, not EnterPlanMode
- Update writing-plans description to explicitly say "not EnterPlanMode"
- Reorder: plan first (while context is fresh), worktree second (for implementation)
This commit is contained in:
Jesse Vincent
2026-02-08 17:35:01 -08:00
parent 84cd6e7c20
commit b4cbf642c8
3 changed files with 6 additions and 7 deletions

View File

@@ -1,6 +1,6 @@
---
name: writing-plans
description: Use when you have a spec or requirements for a multi-step task, before touching code
description: Use when you have a spec or requirements for a multi-step task, before touching code. After brainstorming, ALWAYS use this — not EnterPlanMode or plan mode.
---
# Writing Plans
@@ -13,7 +13,7 @@ Assume they are a skilled developer, but know almost nothing about our toolset o
**Announce at start:** "I'm using the writing-plans skill to create the implementation plan."
**Context:** This should be run in a dedicated worktree (created by brainstorming skill).
**Context:** This runs in the main workspace after brainstorming, while context is fresh. The worktree is created afterward for implementation.
**Save plans to:** `docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md`
- (User preferences for plan location override this default)