writing-plans

To write an implementation plan, you draft a comprehensive document enumerating required files, code changes, tests, and verification steps before coding. This structured task breakdown ensures clear scope, ownership, and testability for multi-step features.

The best way to break down a feature is generating a structured plan document with a consistent header and bite-sized tasks. Enumerating required files, tests, and integration steps in a single plan makes the work suitable for version control and review.

Planning before coding improves testability by explicitly documenting required tests and verification steps alongside code changes. Generating this end-to-end task breakdown upfront ensures clear scope and ownership for new features, fixes, or refactors.

You need a detailed task breakdown when applying features or projects with clear specs. Drafting an executable implementation plan before touching code ensures you enumerate all required files, documentation, and integration steps for easy reuse and auditing.

Yes, you can save generated plans to a standardized location with a consistent naming convention, such as docs/plans/YYYY-MM-DD-feature-name.md. This practice ensures your task breakdown documents are easy to reuse, audit, and review in version control.

Yes, generating a plan document works for refactoring, new features, and fixes. It drafts comprehensive, executable implementation plans by enumerating required files, code changes, tests, and integration steps, ensuring clear scope and ownership for any multi-step task.