shapeup-sdlc 3.18.2 → 4.0.0

package/skills/tech-lead/SKILL.md

@@ -1,151 +0,0 @@
----
-name: tech-lead
-description: "Use this skill whenever the user wants to orchestrate a whole feature end-to-end across the harness skills — ba-pitch-analyzer (planner), task-executor (generator), spec-evaluator (judge) — acting as the tech lead that owns the run and reports to the PO at round boundaries. Trigger on: \"run the full harness\", \"act as tech lead\", \"ship this feature end to end\", \"from pitch to ship\", \"orchestrate the build\", \"plan build evaluate\". Use it even when the user describes a multi-step build flow without naming the skills."
----
-
-# Tech Lead (harness orchestrator)
-
-## ▶ RUN THIS FIRST — do not summarise this file
-
-**Your first output must be a tool call, not a plan.** Everything you emit before the first tool
-call is narration, and a narrated run is a failed run — it reads like a clean success and leaves
-escaped defects behind it. `hooks/gate-zerowork.mjs` (Stop) blocks a session
-that **reached the orchestrator and left no receipt** — where "reached the orchestrator" means
-dispatching this skill or launching a `shapeup-*` workflow by either surface, and the receipt is
-what `harness init run` writes. Working around the harness is not an exemption: a busy session used to
-switch this gate off and no longer does. Loading these instructions is not running them.
-
-**Step 1 — open the run.** Write the requirement to a file first, then pass the path — a
-multi-line requirement inlined into a shell argument is where this step goes wrong. Keep the command
-on ONE line: a grant matches a single-line command, and a `\`-continued one comes back "requires approval":
-
-```bash
-node "${CLAUDE_PLUGIN_ROOT}/kernel/harness.mjs" init run --slug <slug-from-the-request> --intake-file <path/to/the/requirement.md> --auto-level <interactive|auto|unattended> [--dimensions <a,b>] [--gate-answers <ci|guarded|path.json>] [--wall-clock-budget <seconds>] [--max-rounds 3] [--breadboard <path>]
-```
-
-**After a compaction, or in a fresh session over an open run, re-derive before you act.** One
-command answers where the run stands, from artifacts and never from memory:
-
-```bash
-node "${CLAUDE_PLUGIN_ROOT}/kernel/harness.mjs" reduce graph --slug <slug> --subgraph run
-```
-
-**Exit 3 means a run is ALREADY OPEN.** Resume it; do not re-open it. The refusal prints the
-derived RESUME STATE (slug, status, round, board counts) — read it and go straight to Step 2;
-`shapeup-run.js`'s own fast-forward will re-derive exactly where to continue from disk, never from
-this session's memory. `--force` re-opens deliberately and discards the round history the breaker
-counts.
-
-**If this command comes back "requires approval", stop and say so** — the scripts need a one-time grant
-(`npx shapeup-sdlc init`); never route around it or hand-build the feature. Know a grant by running the
-command, never by reading `.claude/settings.json` — Preflight runs the project's probes and reports.
-
-**Language gate (delegated to `translator`, not this skill):** before Step 1 opens the run, dispatch
-an Agent (model: exec) calling `Skill(shapeup-sdlc-plugin:translator) --check` on the pitch *and* its
-breadboard. English → proceed as-is. Non-English → a second Agent translates both (`--auto` under
-auto/unattended); Step 1 then names the `.en.md` files (a run already open on the original: re-open
-it with `--force` — nothing is dispatched yet). The tech lead detects and sequences; never translates.
-
-**Step 2 — pin GATE L0, then launch.** Collect the L0.1–L0.10 config (spec folder, lens, stack,
-eval dims, max_rounds, the model/budget matrix — see `references/gates.md` GATE L0 for the full
-collect-list), write the SHARED `project-profile.md` yourself (`{schema_version:1, archetype,
-entry_point}` — `shapeup-run.js` has no filesystem of its own), emit the `⏸ GATE L0` block, then
-check the lane:
-
-- **`--tiny`, or the spec has no committed `scopes/*.md` yet** (pre-v0.3.0 spec): `shapeup-run.js`
-  is out of scope for this lane by design (it targets scope-contract specs). Run the unchanged
-  legacy loop instead — `references/protocol.md` (BUILD(r)/EVAL) + `references/protocol.md`
-  carry the full step-by-step for both the tiny lane and a scope-less BUILD loop, verbatim, non-
-  regression. Stop reading this file here for that run.
-- **Otherwise** (the common case — a scoped spec, any auto level): resolve every switch the
-  operator typed (`references/gates.md` GATE L0.9b has the flag→field table) and run the kernel's
-  sole `RunArgs` writer: `node "${CLAUDE_PLUGIN_ROOT}/kernel/harness.mjs" init run-args --slug
-  <slug> --auto-level <level> --exec-model <n> [--eval-model <n>] [--qa-model <n>] --max-rounds <N>
-  --attempts <N> --plugin-root "${CLAUDE_PLUGIN_ROOT}" [--answers <a>] [--lane <l>] [--no-eval]
-  [--no-qa] [--adversarial-verify] [--parallel-scopes <N>]`. It writes `.shapeup/<slug>/run-args.json`
-  fresh on every launch/relaunch and prints that identical object — **pass it to `Workflow`
-  verbatim, never re-type it**. Then launch with the **`Workflow` tool** — naming `init run`'s
-  staged copy, never the install path:
-
-```
-Workflow({
-  scriptPath: ".shapeup/workflows/shapeup-run.js",
-  args: <the RunArgs object>
-})
-```
-
-`shapeup-run.js` (`domain.schema.json` `$defs/RunArgs`/`RunReturn`) owns everything from ORIENT
-through GATE H and the ship report — every gate inside that range resolves via `harness gate`'s
-exit code, in code, not by this skill's own reading of a paragraph. The `RunReturn` is the script's
-return value, and it arrives as the workflow's result.
-
-**Why the tool and not a Bash launcher.** The native runtime is what gives the run
-resume-from-journal, worktree isolation, and sub-agents that share this session's prompt cache
-instead of paying a cold start each. `npx shapeup-sdlc init` writes the `"Workflow"` grant the
-launch needs. That grant is UNSCOPED — it authorises every dynamic workflow script in the project,
-not only this one — so an install may decline it with `--no-native-workflow`, in which case the
-launch prompts for approval once per session and the unattended lane is unavailable. If the launch
-comes back "requires approval" in a headless session, stop and say so — do not hand-build the
-feature instead.
-
-**Why a project-local `scriptPath`.** The tool loads a script only from a directory the session may
-already read, and the plugin installs outside your project, so the shipped path is refused before the
-run begins — no permission rule repairs it. `init run` re-copies the scripts to `.shapeup/workflows/`
-on every open, never on a relaunch, so a run finishes on the orchestrator it started with. If staging
-failed, launch from the install path and have the operator `/add-dir` the plugin directory.
-
-## Step 3 — the pause protocol: branch on `RunReturn.status`
-
-| `status` | What the workflow is telling you | What you do |
-|---|---|---|
-| `paused` | A gate resolved "ask" — `paused_at` names it, `block` is composed and ready | Emit `block` **verbatim** (never re-summarise it — that is the paraphrase channel this design exists to close). Put it to the PO, get a decision. Write it to `.shapeup/<slug>/gate-answers.json` (`{"version":1,"preset":"custom","answers":{"<paused_at>":{"decision":"<answer>"}}}`, merging with any prior gate's answer already there). **Relaunch the SAME `Workflow` call, same `args`** — the fast-forward re-derives from disk and re-dispatches nothing already done (verify: `orders/` minus `results/` is empty before it proceeds) |
-| `aborted` | A gate resolved "abort", or a hard stop (spec-lint red, scope-hammer CANNOT SHIP) | Report `aborted_at` + `reason` to the PO. Do not relaunch without a human decision. A relaunch RESUMES the closed run (it reopens, keeping the abort under `prior_closes`); `--force` discards its history and only the PO may ask for it |
-| `gate_h` | A circuit breaker tripped (`breaker`: outer \| inner \| deadline) — `green_scopes` shipped nothing, `hammer_proposals` needs a census | Dispatch a fresh Agent (model: exec): `Skill(shapeup-sdlc-plugin:scope-hammer) --slug <slug> --breaker <breaker> [--scope <id>]` for the census + cut list, put the PO's decision to `references/gates.md` GATE H, then close out via Step 4 below |
-| `shipped` | The board's final round passed EVAL, QA ran, GATE H accepted the cut list, `report` names the frozen `shapeup/<slug>/REPORT.md` | Go straight to Step 4 |
-
-**Never** treat a `paused` return as a stall to work around, and never invent an answer this skill
-did not actually receive from the PO — an unattended lane with no answer for a gate is meant to
-`abort` (see `harness gate`'s `on_missing`), not silently proceed.
-
-## Step 4 — GATE L4 — Ship Sign-Off
-
-A `shipped`/`escalated` return already crossed L4 in the run and froze `REPORT.md`: never resolve it
-again (a row after the close is a second sign-off). A return that did not reach L4 freezes the report
-now and RESOLVES the gate (`references/gates.md` GATE L4). Either way, emit:
-
-```
-⏸ GATE L4 — Ship Sign-Off
-Feature   : [slug] — [SHIPPED (deployed) | BUILT & VERIFIED — deploy pending (PO)]
-Rounds    : [rounds_used]
-Verdict   : [verdict] (dims: [dims_evaluated]; not evaluated: [dims_not_evaluated])
-QA        : [qa_findings] findings | skipped
-Ledger    : harness-run.md
-```
-Ask (max 1): "Anything to record before I close the run?" On substantive feedback, delegate
-`Skill(shapeup-sdlc-plugin:coach)` for RLHF (its own GATE COACH-1 — the tech lead never
-categorizes feedback itself). Then output the final `✅ [slug] …` line.
-
-## Scope boundary
-
-Owns the Shape Up **Building phase (steps 7–11)** only. Shaping (1–4), Betting (5) and Kick-off
-(6) are PO-personal and upstream: intake is a *kicked-off pitch*, never a raw idea. The tech lead
-never orients, plans, builds, or judges itself — `shapeup-run.js` **sequences** the skills that do
-and returns to the PO at every gate.
-
-> **Gate collect-lists + output-block formats** → `references/gates.md`
-> **How each sub-skill is invoked + handoff files (the envelope port)** → `references/protocol.md`
-> **The round loop, stop conditions, three-level breaker rationale** → `references/protocol.md`
-> **Run ledger format + Hill report** → `references/protocol.md` (Part 4 — State)
-> **State ownership, the central domain registry, two-ledger split** → `references/protocol.md` (Part 4 — State)
-> **Hard rules this design enforces, and why** → `references/protocol.md`
-> **Full invocation examples + the complete flag table** →
-> **The small-change lane (`--tiny`)** → `references/tiny-lane.md`
-
-## Invocation
-
-`/tech-lead --pitch <shaping.md> --spec <spec/> --lens standard` for an interactive run; `--auto`
-(pause only at L1a/L1b/L3/L4), `--unattended` (headless/CI), `--from build` (resume), `--no-eval`/
-`--no-qa` to skip passes, `--parallel-scopes N` to set how many scopes build at once (default 4,
-`1` = sequential), `--adversarial-verify` to refute each FAIL finding before it costs a fix round. **`--tiny`** stays a prose-only lane (`references/tiny-lane.md`) —
-`shapeup-run.js` targets specs with committed scope contracts; a tiny change or a pre-scope-
-contract spec runs the unchanged v0.2.6 flow this file's Hard Rules already describe.