Create structured implementation plans from formal specs.
npx skills add https://github.com/DarkCodePE/quipu --skill writing-plans-darkcodepe
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/DarkCodePE/quipu/tree/main/docs/arquetipo/deliverables/skills/kernel/writing-plans Command: npx skills add https://github.com/DarkCodePE/quipu --skill writing-plans-darkcodepe
Planning complex software tasks from a formal spec can be tedious and error-prone. Writing Plans provides a structured workflow to translate requirements into a comprehensive, auditable task plan that guides engineers from design to verification.
Define your spec and run the writing-plans skill to produce a complete plan saved under docs/superpowers/plans/ with a date stamp.
High-intent search queries and answers about installing and using this skill.
To create an implementation plan from a spec, define your requirements and generate a structured document covering files, tests, and documentation. The plan enforces a consistent format with a header and task-by-task steps saved under a dated directory.
Task decomposition for engineering projects is structured using a consistent plan format that breaks down specs into auditable, task-oriented steps. This approach guides developers clearly from design through verification across files and tests.
Yes, you can generate TDD-friendly implementation plans designed for clear engineering team handoffs. The plans describe specific code changes and tests required, ensuring repeatable workflows and structured guidance across features.
An implementation plan document should include a Plan Document Header, detailed code changes, files to touch, tests, and documentation. This structure ensures the plan is auditable and guides engineering work comprehensively.
You need a formal implementation plan for project management when translating complex software requirements into comprehensive, auditable tasks. It provides a repeatable workflow that guides engineers from initial design to final verification.
Yes, this implementation planning workflow operates without external dependencies. It independently enforces a consistent plan structure to guide engineering work, requiring only a defined spec to produce the complete task-oriented output.
ashtonianGuide stakeholder sessions to document software requirements and draft specifications.
zotoioOrchestrate subagents to execute engineering plans with dependency checks and documentation.
duy-tungExecute iterative optimization loops against configurable code metrics with git-based change validation.
adolfoaranaes12Break down epics into user stories with acceptance criteria and sprint groupings.
