Writing Plans

Create executable implementation plans that reduce ambiguity for whoever executes them. The skill walks Phase 1 → Phase 6 in a single turn for normal-sized plans; for unattended long runs, wrap in /goal (see below).

For unattended multi-turn runs

Wrap the invocation in Claude Code's built-in /goal (v2.1.139+):

/goal "Claude has narrated a successful plan commit (with commit hash) and reported the Phase 4 reflection sub-agent verdicts inline" /superpowers:writing-plans <design-path>

/goal provides multi-turn continuation — a fresh fast model checks the condition against the conversation transcript after each turn and re-prompts until satisfied. The evaluator does NOT read files or run commands (upstream docs) — phrase the condition as something Claude's own narration will demonstrate (commit-hash narration from git-agent commit, the literal Phase 4 reflection summary, an explicit completion statement). Conditions written against filesystem state (_index.md exists, Execution Plan YAML present, git commit clean) are unverifiable and will time out. For most reasonable-sized plans, /goal is unnecessary; the skill runs to completion in one turn.

CRITICAL: Bail-Out Check (run first)

Read bdd-specs.md from the resolved design folder. Count Scenario: occurrences. Bail out — do NOT decompose tasks — when EITHER: