spec-driven-storieslisted

Create user stories with acceptance criteria, technical specifications, and UI specifications through an 8-phase workflow with structural anti-skip enforcement. Prevents token optimization bias through per-phase reference loading, checkpoint persistence, Execute-Verify-Record enforcement, and artifact verification. Use when transforming feature descriptions into structured stories, generating stories from epic features, or creating follow-up stories for deferred work. Supports CRUD, authentication, workflow, and reporting story types with complete technical and UI specifications.
bankielewicz/DevForgeAI · ★ 4 · AI & Automation · score 66

Install: claude install-skill bankielewicz/DevForgeAI

# Spec-Driven Stories Produce a complete, implementation-ready user story file with acceptance criteria, technical specification, UI specification (when applicable), and Definition of Done — written to `devforgeai/specs/Stories/STORY-NNN.story.md`. The story-template schema is a load-bearing contract — every downstream skill (`/dev`, `/qa`, `/release`, `/fix-story`, `/validate-stories`, `backend-architect` Phase 2.5) consumes its output shape. **Single-file design principle (NON-NEGOTIABLE):** one story = one file. Sidecars (`STORY-NNN-notes.md`, `STORY-NNN/spec.md`, etc.) are forbidden — enforced deterministically by `stories-sidecar-write-blocker.sh` (PreToolUse[Write|Edit]). All story metadata, ACs, tech spec, UI spec, and DoD live in `STORY-NNN.story.md`. **Context files are THE LAW:** `tech-stack.md`, `source-tree/`, `dependencies.md`, `coding-standards.md`, `architecture-constraints.md`, `anti-patterns.md`. If ambiguous or conflicting — HALT and use AskUserQuestion. --- ## Execution Model This skill expands inline. After invocation, execute Phase 00 Initialization immediately. Do not wait passively, ask permission, or offer execution options. See **`.claude/rules/core/anti-skip-behavior.md`** for the canonical execution contract (Self-Check violation taxonomy; Token-Optimization-Bias prohibition; governed by ADR-076). **INLINE-skill contract:** the orchestrator executes phase steps directly (Read/Write/Edit/Glob/Grep/AskUserQuestion/Bash). Subagents are scoped to