mirror of
https://github.com/obra/superpowers.git
synced 2026-04-22 01:19:04 +08:00
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:
@@ -58,11 +58,9 @@ After writing the spec document:
|
||||
3. If loop exceeds 5 iterations, surface to human for guidance
|
||||
|
||||
**Implementation (if continuing):**
|
||||
- Ask: "Ready to set up for implementation?"
|
||||
- Use superpowers:using-git-worktrees to create isolated workspace
|
||||
- **REQUIRED:** Use superpowers:writing-plans to create detailed implementation plan
|
||||
- Do NOT use platform planning features (e.g., EnterPlanMode, plan mode)
|
||||
- Do NOT start implementing directly - the writing-plans skill comes first
|
||||
When the user approves the design and wants to build:
|
||||
1. **Invoke `superpowers:writing-plans` using the Skill tool.** Not EnterPlanMode. Not plan mode. Not direct implementation. The Skill tool.
|
||||
2. After the plan is written, use superpowers:using-git-worktrees to create an isolated workspace for implementation.
|
||||
|
||||
## Key Principles
|
||||
|
||||
|
||||
@@ -73,6 +73,7 @@ These thoughts mean STOP—you're rationalizing:
|
||||
| "I'll just do this one thing first" | Check BEFORE doing anything. |
|
||||
| "This feels productive" | Undisciplined action wastes time. Skills prevent this. |
|
||||
| "I know what that means" | Knowing the concept ≠ using the skill. Invoke it. |
|
||||
| "I should use EnterPlanMode / plan mode" | If a loaded skill specifies the next step, follow the skill. EnterPlanMode is a platform default — skills override defaults. |
|
||||
|
||||
## Skill Priority
|
||||
|
||||
|
||||
@@ -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)
|
||||
|
||||
Reference in New Issue
Block a user