## Problem After a recent `/to-tickets` → `/implement-spec` MVP build most problems later in the build may have been prevented by some changes to the skills: 1. **Same-session review died under context pressure.** One chat ran ~12 hours through build + review. Near the end a decision form aborted; the orchestrator invented “safe defaults” and launched fixers. Twelve review decisions were never recorded. A fresh session then reviewed and fixed cleanly. 2. **Status lived in chat.** Unplanned stops were hard to resume (I had to restart laptop); ticket/branch/SHA/status was reconstructed from orchestrator prose. 3. **Shared domain rules were re-solved per ticket.** Hierarchy, ordering, error codes, active-card rules, etc. diverged; ~half of post-review fixes were duplication / naming. Owner modules only appeared after the fact. 4. **Spec sections fell between tickets.** Whole sections never got a ticket; end-of-run Spec review of a huge integration diff could not compensate. 5. **Review was once, over a huge diff.** Mergers already saw small diffs but had no standards step. 6. **Unbounded parallelism made tests unreliable.** Seven implementers at once; timeouts crept 5s → 120s; load was chased as product regressions. Cap of 4 worked after resume. 7. **Merger rewrote the integration tip** (`reset HEAD~1`), orphaning a commit another ticket had merged; later tickets debugged half-finished integration states. ## Proposed direction (concrete wording on a fork branch) Draft skill changes (not asking you to merge a fork PR — CONTRIBUTING says collaborators-only; this issue is the ask): Compare: https://github.com/mattpocock/skills/compare/main...gonogo:implement-spec-ledger-and-to-tickets-coverage Branch: `gonogo/skills` @ `implement-spec-ledger-and-to-tickets-coverage` ```diff /implement-spec - implementers (unbounded concurrency) - merger (no standards gate) - code-review + fixes in same session + implementers (cap 4; sync origin/ ) + merger (standards review → check → push → update ledger) + stop with ledger / decisions hand-off + fresh session: code-review + fix-forward /to-tickets + owner ticket for any rule ≥2 tickets need + coverage map: every spec section → ticket (or out of scope) ``` Also a small `ask-matt` blurb sync so the router matches. Happy to reshape into whatever form you want (smaller issues, different defaults, etc.).
