Implement Issue
End-to-end issue implementation via orchestrator script.
Announce at start: "Using implement-issue to run orchestrator for #$ISSUE against $BRANCH"
Arguments:
- •
$1— GitHub issue number (required) - •
$2— Base branch name (required)
Invocation
Immediately launch the orchestrator:
bash
.claude/scripts/implement-issue-orchestrator.sh \ --issue $ISSUE_NUMBER \ --branch $BASE_BRANCH
Or with explicit agent override:
bash
.claude/scripts/implement-issue-orchestrator.sh \ --issue $ISSUE_NUMBER \ --branch $BASE_BRANCH \ --agent bulletproof-frontend-developer
Monitoring
Check progress via status.json:
bash
jq . status.json
Watch live:
bash
watch -n 5 'jq -c "{state,stage:.current_stage,task:.current_task,quality:.quality_iterations}" status.json'
Stages
| Stage | Agent | Description |
|---|---|---|
| setup | default | fetch, worktree, research, evaluate, plan |
| implement | per-task | execute each task from plan |
| task-review | spec-reviewer | verify task achieved goal |
| fix | per-task | address review findings |
| simplify | code-simplifier | clean up code |
| test | php-test-validator | run test suite |
| review | code-reviewer | internal code review |
| docs | phpdoc-writer | add PHPDoc blocks |
| pr | default | create/update PR |
| spec-review | spec-reviewer | verify PR achieves issue goals |
| code-review | code-reviewer | final code quality check |
| complete | default | post summary |
Schemas
Located in .claude/scripts/schemas/implement-issue-*.json
Logging
Logs written to logs/implement-issue/issue-N-timestamp/:
- •
orchestrator.log— main log - •
stages/— per-stage Claude output - •
context/— parsed outputs (tasks.json, etc.) - •
status.json— final status snapshot
Exit Codes
| Code | Meaning |
|---|---|
| 0 | Success, PR created and approved |
| 1 | Error during a stage |
| 2 | Max iterations exceeded |
| 3 | Configuration/argument error |
Integration
Called by handle-issues via batch-orchestrator.sh.