Verified Agent Skill record

writing-plans · Superpowers

Use when you have a spec or requirements for a multi-step task, before touching code. Produces comprehensive implementation plans written as bite-sized tasks for engineers who may have zero codebase context.

Tasks

Map the file structure: list every file to create or modify with its single clear responsibility, following established codebase patterns and preferring focused files.
For each task, write the full checkbox step sequence with actual test code, exact run commands with expected output, complete implementation code, and the git commit command—no placeholders or TBDs.
Run the self-review checklist: verify every spec requirement maps to a task, scan for placeholder patterns, and confirm type and signature consistency across all tasks.
Save the plan to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md and present the execution handoff choice between subagent-driven and inline execution.

Inputs

A spec or requirements document for a multi-step task
Optional user preferences for plan save location

Outputs

A markdown plan document saved to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md containing the required header, global constraints, and fully detailed bite-sized tasks
An execution handoff offer with two options: subagent-driven development or inline execution

Limitations and checks

If the spec covers multiple independent subsystems and was not broken into sub-project specs during brainstorming, the skill can only suggest splitting—cannot auto-decompose
Does not itself execute the plan; execution requires the subagent-driven-development or executing-plans sub-skill
Cannot reference the using-git-worktrees skill for isolated worktree creation at plan-writing time—that is an execution-time concern
Confirm every section and requirement in the spec maps to at least one task; list and fill any gaps.
Search the finished plan for placeholder patterns (TBD, TODO, implement later, add appropriate error handling, write tests for the above without code, similar to Task N) and replace each with actual content.
Verify that function names, method signatures, parameter types, and return types referenced in later tasks match exactly what was defined in earlier tasks.
Verify every code-bearing step includes a complete code block and every test step includes the exact run command and expected output.
Confirm the plan file is saved to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md or a user-specified override location.