writing-plans

To convert requirements into a test-driven implementation plan, you provide written specifications to generate a structured plan with explicit file targets, testing steps, and command examples. This prevents premature code changes by enforcing bite-sized tasks that start with failing tests.

Test-driven development planning prevents premature code changes by enforcing bite-sized tasks where the implementer writes failing tests first, implements minimally to pass, and commits frequently. This ensures behavior verification before any functional code is added.

Yes, you can use git worktrees for executing multi-step software engineering plans. The generated plan assumes execution happens in a dedicated worktree-based execution context, ensuring isolation and providing an explicit handoff to a task execution subagent.

The best way to structure implementation plans for an agent with limited context is to provide explicit file-touch guidance, exact plan headers, and task granularity rules. This ensures deterministic planning and clarity on architecture without relying on the implementer's implicit taste.

Yes, implementation planning works for multi-step software engineering tasks requiring specific file targets. It produces a comprehensive plan with explicit file targets, testing steps, and command examples, guiding the implementer safely through zero-context execution.

You should use a structured plan instead of direct implementation to prevent vague requirements from causing premature or incorrect code changes. It applies assumption-aware engineering guidance, ensuring clarity on architecture, files, and verification before any code is touched.