writing-plans

To generate an implementation plan for engineers with zero context, use this skill to create deterministic, step-by-step tasks from design to commit. It enforces a structured format with exact file paths, code samples, and version-control steps.

Yes, you can create a test-driven development plan with incremental commits. The skill encourages test-first planning, providing clear task granularity and integrating verification steps directly into the implementation workflow.

The best way to break down a feature design into actionable tasks is to automate generation of end-to-end plans. It covers feature development, testing, and integration scenarios, outputting explicit file paths and code examples for each step.

Yes, this implementation planning approach produces documentation-ready artifacts. The generated plans are structured with precise file paths, code samples, and testing guidance, making them suitable for sharing with teams and integrating into project docs.

To plan version-control steps and testing guidance for a new feature, the skill generates comprehensive plans from design to commit. It includes exact file paths, code samples, and TDD-oriented verification steps for engineers.