What problem does it solve? It enforces a disciplined, issue-driven development workflow where no code is written without a ready GitHub issue, underspecified specs are rejected instead of guessed at, and every change ships with verifiable proof before QA review. ## Core Features & Use Cases - Issue-gated implementation: Picks up exactly one GitHub issue labeled flow:ready-dev, validates it against a Definition of Ready, and rejects weak specs back to the Product Agent with actionable feedback. - Isolated worktree workflow: Creates a dedicated git worktree and branch per issue, builds the full solution, and runs a per-session isolated test Director instance to avoid collisions with concurrent sessions. - Proof-based QA handoff: Commits implementation plus screenshots and an HTML report to the PR branch, enforces a clean-tree gate, and swaps labels to flow:ready-qa. - Use Case: A team running the CenCon Development Method invokes this agent to implement issue #142, which plans the change, builds cc-director.sln cleanly, captures before/after screenshots via the Control API, and hands off to QA with a linked proof report. ## Quick Start Ask the agent to implement the next GitHub issue labeled flow:ready-dev from the devthrottle repository.
