shapeup-sdlc-plugin: Instructions file for Codex

Shape Up SDLC Local Harness

Enforcement model

A three-phase Shape Up loop orchestrated by /tech-lead. Invariants live in the runtime, not this file — expect hook denials, not arguments.

Skills and commands are named short throughout this file; every one of them resolves only under the plugin's namespace — Skill(shapeup-sdlc-plugin:orient), /shapeup-sdlc-plugin:ship. A bare name is not a typo you get a warning for: an unknown skill name is rejected upstream of the hook layer, so the dispatch fires no hook, leaves no decision row, and is answered by improvisation.

Workflow at a Glance

flowchart TD
    SH["Phase 1 — Shaping\n(Set Boundaries, Find the Elements, Risks & Rabbit Holes)"]
    BT{"Phase 2 — Betting\nPO decides"}
    L0["L0 — Intake & Config"]
    L1a["L1a — Orient Review"]
    REQ["Requirements + Analyze\n(reviewed at L1b)"]
    L1a5["L1a.5 — Wiring Review"]
    L1b["L1b — Board Review"]
    ROUND["BUILD round\n(dispatch, T0-verify, round build gate)"]
    L2["L2 — Round Close"]
    L3["L3 — Verdict"]
    QA["QA Edge Hunt"]
    H["GATE H — Cut-List Review"]
    L4["L4 — Ship Sign-off"]
    COACH["GATE COACH-1 — Retro Ownership"]

    SH --> BT
    BT -- bet --> L0
    BT -- reject --> SH
    L0 --> L1a --> REQ --> L1a5 --> L1b --> ROUND
    ROUND --> L2 --> L3
    L3 -- FAIL --> ROUND
    L3 -- PASS --> QA --> H
    ROUND -- "round_budget or wall_clock_budget_s exhausted" --> H
    H --> L4 --> COACH

Gate Vocabulary & Symbol Legend

Every gate below pauses the run for a PO decision unless a pre-recorded gate-answer preset resolves it (ci/guarded/interactive); QA, H and COACH-1 are real gates too even though this file doesn't prefix them with the same ⏸ marker as the rest. The code is what shows up in decisions.jsonl, gates.jsonl and any gate-answers file; the plain name is what the rest of this document calls it.