writing-plans

To convert a software spec into an implementation plan, provide the feature spec to generate a comprehensive, task-by-task breakdown. The output details exact file paths, code blocks, shell commands, tests, and commit messages suitable for direct engineering execution.

The best way to decompose multi-step software tasks across subsystems is by generating a documentation-first plan. This approach breaks down specs into concrete, testable tasks with clear ownership, defined milestones, and exact file paths.

Documentation-first design improves engineering task planning by outlining exact files, interfaces, and testing strategies required before coding begins. This process reduces back-and-forth communication and minimizes rework by providing execution-ready guidance.

Yes, you can generate commit messages and shell commands directly from a feature spec. The plan produces execution-ready guidance containing exact file paths, code blocks, and commit messages structured for immediate implementation by engineers.

Implementation planning works for vague specs by transforming them into clear, actionable plans with defined ownership and milestones. It reduces ambiguity for stakeholders and engineers by detailing exact files, tasks, and testing strategies needed for execution.