Plan
Break a feature into a detailed implementation plan with bite-sized tasksFrom its SKILL.md
npx -y skills add bromso/metapowers --skill planAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 341 tokens by cl100k_base, as published. Nobody here has run it
Plan
Create a detailed implementation plan for "$ARGUMENTS". Break the work into bite-sized tasks (2-5 minutes each) with exact file paths, test strategy, and commit points.
Prerequisites
None — this is the first phase of any development effort.
Process
-
Understand the feature:
- Clarify what "$ARGUMENTS" means — ask the user if ambiguous
- Identify acceptance criteria and constraints
- Determine scope boundaries
-
Explore the codebase:
- Read relevant existing code, tests, and configuration
- Identify files to create and files to modify
- Understand existing patterns and conventions
- Note dependencies and potential conflicts
-
Break into tasks:
- Each task should take 2-5 minutes to complete
- Each task produces a working, committable state
- Order tasks so each builds on the previous
- For each task specify: files to touch, steps, expected outcome
-
Define test strategy:
- What tests need to be written?
- What existing tests might break?
- How to verify the feature works end-to-end?
-
Write the plan using the template from
plugins/development/shared/plan-template.md -
Write the artifact to
.metapowers/development/$ARGUMENTS/01-plan.md
Output
The implementation plan written to .metapowers/development/$ARGUMENTS/01-plan.md. Present a summary to the user highlighting:
- Number of tasks
- Key architectural decisions
- Test strategy
- Estimated complexity
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.