writing-plans

To generate an implementation plan from a minimal software spec, use this skill to break down requirements into bite-sized tasks with explicit file targets, testing guidance, and documentation notes for clear handoffs.

Planning multi-step codebase changes for engineers with no context is best handled by generating date-stamped plans in a docs/plans repository, ensuring every requirement and file modification is documented for predictable handoffs.

When task planning with test-driven development, you can enforce DRY, YAGNI, and TDD principles by generating lean, reliable steps that explicitly include testing guidance and documentation notes for each implementation phase.

Yes, this approach works for spec-driven software development by taking minimal specs and expanding them into comprehensive, executable steps that detail exactly what to implement, how to test, and how to commit.

To document and trace implementation plans in your repository, save the generated plans as date-stamped markdown files in a docs/plans directory using the YYYY-MM-DD-<feature-name>.md naming convention for traceability.