team-implementlisted

# Team Implement — Execute the Plan Run the IMPLEMENT phase. Three internal sub-steps: 1. **Test-first** — `test-architect` writes failing acceptance tests 2. **Slice execution** — `implementer` executes vertical slices with per-slice commits 3. **Code review** — 5 parallel reviewers + aggregate hard-gate retry loop ## Input `$ARGUMENTS` is the artifact directory: `docs/plans/<id>/`. If empty, the discovery block below resolves it. The agents read: - `$ARGUMENTS/plan.md` — file-level steps and per-slice tests - `$ARGUMENTS/structure.md` — slice ordering and verification checkpoints - `$ARGUMENTS/design.md` — context for what each test should assert - `$ARGUMENTS/repos.md` — repo scope (only present when the topic spans more than one repository). The implementer cd's between worktrees as the plan steps require - `$ARGUMENTS/task.md` — intent (for the implementer when in standalone mode) Resolve the artifact directory by running this self-contained block (one bash call — agent threads reset cwd between calls): ```sh # Three-tier artifact-directory discovery (archetype A). # ID_RE + PHASE_FILES canonical from hooks/session-start-recover.mjs. # PHASE_FILES recency mirrors findActiveTopic() in session-start-recover.mjs. # NOTE: this block is duplicated across 8 skills by design (see docs/architecture.md); future: shared discover-topic.sh. ID_RE='^([A-Za-z][A-Za-z0-9_]*-[0-9]+|[0-9]{4}-[0-9]{2}-[0-9]{2})-[a-z0-9][a-z0-9-]*$' PHASE_FILES="task questions research desig