implementation-workflow

A minimal-change implementation workflow enforces worktree-only edits and todo-driven task breakdown to keep diffs meaningful. It breaks feature development into structured phases: parse context, gather details, execute changes, test, and report back.

A worktree-based development workflow isolates feature implementation, testing, and debugging cycles in dedicated worktrees. Use it when you need disciplined, repeatable code changes that prevent drive-by edits and allow reviewers to easily verify every change serves the plan.

Break down a feature plan by decomposing the ticket into tracked todos during the parse and gather-context phases. Execute only the required edits in a dedicated worktree, maintaining minimal, plan-focused changes throughout the implementation cycle.

Yes, an autonomous test-and-debug loop runs tests and debugs until passing before reporting back. Use built-in code search tools and simple single-purpose shell commands for exploration during this cycle to verify implementation correctness.

No specific testing frameworks or dependencies are required. The workflow uses built-in code search tools and simple shell commands for exploration, applying to repository development work across small scoped changes, testing, and debugging cycles.

Avoiding drive-by edits ensures worktree-only changes remain minimal and plan-focused, keeping diffs meaningful for reviewers. This disciplined approach guarantees every code change directly serves the implementation plan and passes the test-debug cycle.