Generate implementation plans from feature specifications and save them to docs/plans.
npx skills add https://github.com/tizee/skills --skill writing-plans-tizee
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/tizee/skills/tree/main/superpowers-skills/writing-plans Command: npx skills add https://github.com/tizee/skills --skill writing-plans-tizee
Write comprehensive implementation plans assuming the engineer has zero context for our codebase. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, and how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
Provide a complete, step-by-step implementation plan for a given feature and save it to docs/plans/YYYY-MM-DD-<feature-name>.md.
High-intent search queries and answers about installing and using this skill.
To generate an implementation plan from a feature specification, provide the spec to produce a step-by-step task breakdown. The plan details required file changes, tests, and documentation, saving to docs/plans with a YYYY-MM-DD feature name format.
You need a task-by-task implementation plan for multi-step features requiring cross-file coordination, tests, documentation, and clear handoffs. It ensures frequent commits, traceability, and structured workflow across complex engineering tasks.
Write implementation plans by documenting everything an engineer needs to know: which files to touch, required tests, and docs to check. Follow DRY, YAGNI, and TDD principles, breaking the feature into bite-sized tasks for frequent commits.
Yes, the generated implementation plan includes testing and documentation steps. It creates end-to-end task breakdowns that specify files to touch, required tests, docs to check, and version-control steps to ensure comprehensive feature delivery.
The best way to standardize implementation plan tracking is to save plans as markdown files in docs/plans/YYYY-MM-DD-<feature-name>.md. This structured, task-by-task workflow enables frequent commits, traceability, and reusability across projects.
This plan generation workflow targets multi-step tasks requiring cross-file coordination, documentation, and tests. For single-file changes or simple modifications, a comprehensive task breakdown with handoffs may be unnecessary overhead.
cexllGenerate structured UI/UX prototype prompts for mobile and web applications.
lucasreydmanGenerate step-by-step implementation plans from a feature spec.
TruCol270Transform product or engineering specs into task-by-task Markdown implementation plans.
wachawoDecompose project specifications into vertical slices with dependency mapping.
