writing-plans

To generate a zero-context implementation plan, you input a completed software design and the tool outputs exact file paths, code samples, tests, and documentation steps. It produces task-ready plans without requiring prior knowledge of your codebase.

A zero-context engineering plan is a comprehensive task breakdown detailing exactly what to implement, where to modify files, and how to verify success. You need one when a design is complete but engineers lack existing codebase knowledge to start coding.

Yes, the generated implementation plan includes specific testing strategies, acceptance criteria, review checkpoints, and deployment notes. It strictly enforces Test-Driven Development (TDD) principles alongside DRY and YAGNI to ensure verification-focused task breakdowns.

You create a comprehensive task breakdown by running the planning skill on a finished design. It produces precise, step-by-step tasks covering frontend, backend, tests, and documentation touchpoints, saving the plan to a standardized markdown file.

The best way to structure implementation plans for traceability is to save them to a standardized directory using a date-prefixed naming convention. The tool automatically saves generated plans to plans/YYYYMMDD-feature-name.md for consistent retrieval.

Yes, you can generate a task-ready implementation plan from a high-level design as long as the design phase is complete. The plan articulates exact modification locations, code examples, and verification steps, bridging the gap between design and coding without prior codebase knowledge.