← ClaudeAtlas

ai-dlclisted

Run the full AI-DLC inception pipeline for a task — story → refine → design → tasks — with a human gate between each phase
paoloirrera/ccgraph · ★ 1 · AI & Automation · score 63
Install: claude install-skill paoloirrera/ccgraph
# /ai-dlc — inception pipeline orchestrator Walks a task through the AI-DLC **inception** phases end to end, pausing for human validation between each. A thin conductor over the per-phase skills — it does not re-implement them. ## Phases (each is a separate skill; run them in order) 1. **Story** → `story-new` — draft `story.md` from the idea. 2. **Refine** → `story-refine` — resolve open questions, verify facts, tighten scope. 3. **Design** → `design-doc` — architecture + task map (+ ADRs if warranted). 4. **Tasks** → `tasks` — expand the task map into `tasks/` (API surface per unit, not full code). `pr-draft` is deliberately **not** part of this orchestrator: it runs *after* the building phase, once real code exists on the branch. Inception stops at the task interfaces. **Spec-driven entry.** When the work starts from a factory spec (`specs/<name>.yaml`) rather than a rough idea, phases 1–2 are already satisfied — a spec *is* refined requirements. Enter at phase 3 via `spec-design` (spec → `design-doc.md`) instead of `design-doc`, then continue at phase 4 (`tasks`). The spec, not a `story.md`, is the source of truth; re-run `spec-design` when the spec changes. ## Input An idea and optional slug, e.g. `/ai-dlc weather-tool "MCP tool that fetches current weather"`. If resuming an existing story, pass just the slug and this skill picks up at the first incomplete phase. ## How to run 1. **Determine the starting phase.** First, if a `specs/<slug>.yaml` exists (spec-drive