writing-plans

To turn specifications into an implementation plan, provide a feature name and clear requirements. The tool generates a comprehensive Markdown plan with file-level instructions, test plans, and documentation prompts, saving it to docs/plans/YYYY-MM-DD-<feature-name>.md.

To break down development tasks for unfamiliar toolsets, generate a plan that assumes little domain knowledge. It documents which files to touch, code to write, testing steps, and necessary documentation, enforcing DRY and YAGNI practices.

Yes, you can generate a test-driven development plan with file-level instructions. The output explicitly enforces TDD practices alongside detailed task breakdowns, specifying exact files to modify and how to test them.

The best way to document requirements before coding is creating a structured Markdown plan. It captures code snippets, testing protocols, and documentation references, ensuring frequent commits and clear task execution.

Yes, this implementation planning approach works across diverse languages and frameworks. It processes provided feature requirements to generate explicit, file-level development guidance regardless of the specific technology stack used.