writing-plans

To create an implementation plan for non-trivial software features, you must complete upfront prerequisites, design evaluation, and design assertions. This produces a structured plan saved as a markdown file with verifiable, bite-sized tasks.

Enforcing prerequisites and design evaluation before coding requires using a structured plan template with mandatory sections like Overview, Prerequisites, Tasks, Testing, Rollback, and Self-Audit. Design assertions prevent shortcuts and ensure plans reflect the design doc.

Breaking down software engineering tasks into bite-sized verifiable steps requires a fixed plan structure. This structure enforces design assertions to prevent shortcuts, ensuring every task is auditable and methodically executed.

Implementation plans for dev workflow task management should be saved to the docs/plans directory using the YYYY-MM-DD-<topic>.md file naming format. This organizes plans by date and topic for easy retrieval.

Methodical implementation plans generated for software engineering projects can be executed using the executing-plans skill. The writing-plans process outputs a structured markdown file designed specifically for this downstream execution.

You need a written, verifiable plan before building any non-trivial software feature. Detailed methodical planning reduces rework and aligns teams by forcing a structured plan with mandatory sections like Testing, Rollback, and Self-Audit.