← ClaudeAtlas

dev-storylisted

Implements a story from its story file task by task, runs the Build & Test Gate by actually building and testing, verifies invariants and UI design, then hands off to an independent reviewer instead of reviewing its own diff. Use when a story is ready-for-dev, or when the user says "dev story", "implement story", or "dev {story file path}".
rterakedis/leanwheel-skills · ★ 2 · Testing & QA · score 65
Install: claude install-skill rterakedis/leanwheel-skills
# Dev Story Skill **Goal:** Implement all tasks until ACs satisfied and DoD passes. **Iron rule:** Only stop when: (a) all tasks done and DoD passes, (b) HALT condition, or (c) user says stop. ## Activation 1. Identify story: user path or first `Status: ready-for-dev` in `docs/epics/`. Stop if not found. 2. Read story file completely. 3. Read CLAUDE.md if exists (may override Dev Notes). 4. **Apple platform project** (`docs/setup/swift/` exists, or an `.xcodeproj`/`Package.swift` is present): read [apple-project.md](apple-project.md) — it routes the `docs/setup/swift/` files to read for this story's tasks, before implementing. 4b. **Web/SSG project** (`docs/setup/web/` exists, or `package.json` is present): read [web-project.md](web-project.md) — it routes the `docs/setup/web/` files to read for this story's tasks, before implementing. 4c. **Design contract** (UI stories): if the story changes user-visible UI, read [ui-stories.md](ui-stories.md). A `### Design Contract` in Dev Notes is the design source of truth. 5. Execute **TRANSITION** with `new_label: in-progress` (skip if unavailable). 5b. Record the review base: `git rev-parse HEAD`. The reviewer diffs everything since it, committed or not — note any unrelated uncommitted changes in Completion Notes. 6. Confirm: "Implementing {epic}.{story}: {title}. Starting..." ## Execution For each task in order: 1. Read task. Understand file, action, outcome. 1b. Apply the simplicity ladder from CLAUDE.md's `## Simplicity & An