tech-leadlisted
Install: claude install-skill nguyenvanphituoc/shapeup-sdlc-plugin
# 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 `init-run.mjs` 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 (measured: six
turns fighting shell quoting):
```bash
node "${CLAUDE_PLUGIN_ROOT}/skills/tech-lead/scripts/init-run.mjs" \
--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]
```
**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 w