sdlclisted

# SDLC Orchestrator Skill This skill drives the full development lifecycle from task description to merged PR. It is project-agnostic: all project-specific configuration (agents, waves, gates) is loaded from `.claude/sdlc-config.md` in the working directory. --- ## Step 0 — Boot (always first) Before doing anything else: 1. Read `.claude/sdlc-config.md`. If the file is missing, stop and tell the user: "No `.claude/sdlc-config.md` found. Create one using the template at the top of the sdlc skill before proceeding." 2. Parse the config into three structures: - **Agents map** — name → role + file path - **Waves list** — ordered array of `{ wave, agents[], isHardGate }` (hard-gate waves block on any failure before the next wave starts) - **Merge requirements** — per-agent rules (explicit APPROVED comment, test suite pass, no open blockers, etc.) 3. Parse any conditional-agent rules (e.g., bob is required only when certain file paths are touched). 4. Store these in working context — all subsequent steps reference them. Then branch based on the invocation flag: - `/sdlc <task>` → proceed to **Phase 1** - `/sdlc --review` → jump to **Phase 3** (PR already open) - `/sdlc --fix` → jump to **Phase 4** (findings already in context) - `/sdlc --merge` → jump to **Phase 6** --- ## Phase 1 — Plan & Implement **1.1 Plan** Enter plan mode (EnterPlanMode). Produce a concise implementation plan: - What files will be created or modified - What the key logic changes are - Which