writing-plans

Generate an implementation plan by providing a feature spec to produce a detailed, step-by-step blueprint listing touched files, testing steps, verification criteria, and precise commit guidelines for incremental development.

Breaking down multi-step development tasks involves generating a shareable plan that enforces bite-sized tasks, applying TDD, DRY, and YAGNI best practices to ensure clear alignment among engineers, QA, and product teams.

Apply TDD best practices during plan generation by enforcing bite-sized task granularity that guides incremental development, ensuring the resulting plan explicitly specifies testing steps and verification criteria for each code change.

Yes, task-breakdown planning applies directly to multi-step software development tasks, transforming requirements into executable plans that cover code changes, tests, and documentation to enable clear team handoffs.

Implementation plan generation works without external dependencies, relying solely on the provided specification or requirements to output the detailed plan directly into your documentation directory.