coachlisted

# Coach Skill — RLHF for the harness The `/coach` skill closes the learning loop. After a feature ships, the PO/TL drops raw, unstructured feedback at the L4 Gate ("the executor keeps over-engineering DTOs", "the BA under-scopes mobile"). The coach distills that into durable **guidelines** and files them where the relevant worker will read them on its **next** run — so the lesson is learned once and applied by the whole team forever, not re-explained every sprint. Two properties make this useful and were missing before: 1. **Team-shared, not local.** Guidelines are written under `shapeup/knowledge-base/`, which is **committed** (the `.shapeup/` run-trace root is gitignored — guidelines written there would never reach a teammate). A `git pull` is all a team member needs to inherit the harness's accumulated judgment. 2. **Read back, not write-only.** Each guideline is filed under the **one skill that will act on it**, in that skill's own file, so the consumer loads only its own rules. `task-executor`, `ba-pitch-analyzer`, and `qa-edge-hunter` each read their file at the top of their run. ``` PO feedback at L4 ─► /coach ─► [parse into candidate rules] ─► ⏸ GATE COACH-1 (categorize, ask — never assume) │ shapeup/knowledge-base/<skill>.md ◄───┤ (one file per coachable skill, committed) │