This document explains the Execution composition: entry, routing, and handoff. Internal step-by-step workflows live in each Skill's SKILL.md and references/.
implement— user-invoked general-purpose bounded executoragent-config— model-invoked host-capability mappertdd— model-invoked test-driven loopdiagnosing-bugs— model-invoked diagnosis loopresolving-merge-conflicts— model-invoked merge/rebase resolver
All are first-party and self-contained; no install of mattpocock/skills or sol-advisor is required.
| Situation | Entry | Typical path | Handoff / Stop |
|---|---|---|---|
| One clear ticket / SPEC slice | implement — user-invoked |
implement → inspect context → optional agent-config offer (when routing/review/independence materially helps) → execute → verify → hand to review-loop with the right reviewer |
bounded diff + focused tests + verification evidence; stop at ticket scope |
| Need to decide execution topology | agent-config — model-invoked |
requires: bounded task + acceptance authority + change units with ownership + current host evidence; returns multi-model/multi-agent / single-model/multi-agent / single-model/single-agent / BOUNDARY |
execution plan, not execution; Controller still performs work per plan |
| Code feature/fix should be test-first | tdd — model-invoked |
red → green → refactor with real tests |
tests + implementation slice |
| Hard bug / regression | diagnosing-bugs — model-invoked |
build a tight pass/fail signal → reproduce → hypothesize → instrument → fix → cleanup |
fix with feedback loop evidence |
| Merge/rebase conflict | resolving-merge-conflicts — model-invoked |
resolve conflicted files per git guidance | clean working tree ready for verification |
implement does not copy reviewer instructions. Coding work follows:
implement → tdd (when appropriate) → code changes + tests → review-loop → code-review
Non-coding work:
implement → artifact → review-loop → generic-review / domain reviewer
The reviewer is read-only; review-loop is the convergence engine; project-review (see review-system) owns final PASS/FAIL/BLOCKED when project acceptance is needed.
- Vague idea → clarification-system first.
- Approved SPEC →
project-ticketsbeforeimplement. - Completed project →
project-review/ review-system. - Unknown entry →
ask-light.