writing-plans

To turn a project spec into an implementation plan, this skill automates the translation of high-level requirements into a structured, step-by-step breakdown. It documents required file touch points, tests, and documentation checkpoints to bridge the gap between specs and engineering execution.

Writing implementation plans with test-driven development requires enforcing TDD, DRY, and YAGNI principles. This skill generates concise plans by explicitly specifying tests to write and responsible components for each task, ensuring reliable and actionable engineering steps.

Task splitting for software engineering involves breaking down a spec into explicit file modifications and acceptance criteria. This skill automates that task splitting by producing a comprehensive, organized plan that engineers can execute with confidence.

Yes, the plan-writing workflow saves generated documentation directly to a specific markdown file format. It automatically stores the complete implementation plan at docs/plans/YYYY-MM-DD-<feature-name>.md to maintain organized project records.

Yes, you can use this for product development and research task planning. It is primarily used for software engineering, product development, or research tasks that require structured task breakdown, explicit file touch points, tests, and documentation checkpoints.

Generating an implementation plan prevents the gap between high-level specs and actionable engineering steps. By producing an organized plan with documented required files, tests, and acceptance criteria, it ensures engineers execute tasks with confidence and avoids missed requirements.