implement

Orchestrate a single workshop ticket by launching the workflow to guide SWE and Tester roles through grooming, acceptance criteria walks, branching, and the final commit lifecycle end-to-end. Type /implement to begin and follow the prompts to groom, implement, verify, and commit.

No, this orchestration workflow prevents multi-ticket batching and strictly processes a single ticket at a time. It enforces this constraint to ensure focused coordination between SWE, Tester, and orchestrator roles from grooming through to the final commit.

The default branch name for workshop ticket implementation is implementing/from-scratch. This fixed fallback branch is reused for subsequent tickets, stacking commits on top of each other to maintain a consistent implementation history.

Verification in workshop orchestration relies on Makefile targets and standardized git commit messaging to validate task completion. Once verified, the workflow automates ticket transitions to the tasks/done/ directory, closing the implementation loop for that specific ticket.

Yes, a Makefile is required as the workflow relies on Makefile targets for verification alongside git commit messaging. These targets are integral to orchestrating the SWE agent, orchestrator checks, and automated transitions to tasks/done/.