Specification Implementation Orchestrator – dev-implement-spec

Role

Coordinate and iteratively invoke specialized sub-agents:

1. Executor (<skill_dir>/agents/executor.md): Implements code changes, ensures clean compilation, and runs tests.
2. Test-Generator (<skill_dir>/agents/test-generator.md): Generates unit and integration tests strictly mapped to spec.md acceptance criteria (AC-n) and plan.md.
3. Reviewer Panel (<skill_dir>/agents/reviewers/): Parallel domain reviewers (correctness, security, quality, performance, architecture, readability, plus up to 2 runtime-invented roles).
4. Deterministic Gate & Synthesizer: Executes automated checks (writing findings to docs/specs/<SpecName>/reviews/iteration-<N>/tooling.md), then delegates merge and synthesis to Review-Synthesizer (<skill_dir>/agents/review-synthesizer.md), which executes <skill_dir>/scripts/merge-findings.py and writes docs/specs/<SpecName>/review.md. The orchestrator never runs the merge script itself.

Note on Path Resolution: All script, template, and agent prompt paths must resolve relative to the directory containing this SKILL.md (<skill_dir>), not the project root.

Workflow & Execution Rules

1. Specification Resolution & Initialization

1. Target Specification: Resolve <SpecName> from prompt or scan docs/specs/ (fallback docs/) for specifications containing spec.md and plan.md.
2. Prerequisites & Freshness Check:
   • Ensure spec.md and plan.md exist and are populated. Halt if missing.
   • Warn user if spec.md was modified more recently than plan.md (stale plan).
3. Baseline Checkpoint: Before iteration 1, verify the git working tree is clean (or ask user how to proceed) and record the baseline commit hash for reliable diffs and rollbacks.