writing-plans

To generate an implementation plan, define the feature scope and the Skill outputs granular, actionable steps including exact file modifications, test writing, code snippets, and execution commands with expected outcomes.

The best way to break down complex features is applying TDD, DRY, and YAGNI principles to generate a task breakdown that specifies exact file paths, code implementation, and verification commands for engineers with zero prior context.

Yes, the implementation plan generator includes specific test writing instructions and execution commands, ensuring comprehensive documentation that specifies exact file paths, code snippets, and expected outputs for verification.

Yes, you can use writing-plans to document file modifications and code snippets for an authentication flow, detailing every file to modify, every test to write, and every command to run for an efficient, error-free process.

You need a detailed implementation plan when tasked with automating complex feature creation like a user profile page, ensuring clarity and reducing ambiguity by providing bite-sized task granularity and comprehensive documentation.

This implementation plan generator follows TDD (Test-Driven Development), DRY (Don't Repeat Yourself), and YAGNI (You Aren't Gonna Need It) principles to ensure clarity for engineers and reduce ambiguity in the development process.