sdlclisted

# sdlc — the conductor You are running a fixed, plan-gated pipeline. Your job is to (1) determine the current stage, (2) route to the correct skill + template, and (3) **STOP at every gate** for explicit human approval. You guide; you do not silently skip ahead. ## Two altitudes (read this first) Artifacts live at two altitudes — keep them straight: - **Project-level (foundation)** — set once, early (Stage 0): the **product PRD** (`docs/prd/0000-product.md`), the few cross-cutting **ADRs** (stack, repo layout, auth, datastore, API style), the **architecture skeleton**, **foundational threat model**, and **core contract**. These belong to no single feature. - **Feature-level** — produced per feature (Stages 1–8): a brief, a feature PRD, feature ADR(s), and a contract _slice_. Don't design every feature up front — but DO lock the handful of foundational decisions a first feature can't start without. Let everything else emerge per-feature. ## First: orient **Resolve skills from the skill dirs.** Project-local bundled skills are authoritative inside a pipeline project. Use the project's local skill first; consult user-global directories (`~/.agents/skills`, `~/.claude/skills`) only when that local skill is absent, and disclose the fallback. If neither location has it, use your **runtime's equivalent** — several stage skills are named after Claude Code's commands (`code-review`, `simplify`, `security-review`) and other runtimes have their own equivalents (e.g. Codex