ring:writing-plans

To create an implementation plan for zero-context engineers, you provide a feature name and context to generate exact file paths, complete code samples, and explicit verification steps. This ensures execution readiness without prior codebase knowledge.

A zero-context implementation plan provides comprehensive execution instructions including precise file paths, complete code examples, and explicit agent specifications. It enables engineers to execute tasks across multi-module repositories without prior codebase familiarity.

Yes, you can use this for design-to-development handoffs in multi-module repositories. It coordinates task breakdowns and execution readiness by enforcing precise file paths and zero-context validation across complex project structures.

The best way to validate an executable implementation plan is using the built-in checker after saving the document to docs/plans/YYYY-MM-DD-<feature-name>.md. This enforces zero-context validation and explicit target specifications.

Your engineering team needs formal task breakdowns to prevent misalignment and rework. Generating concrete plans with executable steps ensures alignment across engineering tasks before development begins.