dev:story

Analyze user stories to extract goals, scope, and acceptance criteria.

3|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/ryryo/dot-claude-dev --skill dev-story
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev:story
Source: https://github.com/ryryo/dot-claude-dev/tree/main/.claude/skills/dev/story
Command: npx skills add https://github.com/ryryo/dot-claude-dev --skill dev-story

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill analyzes a user story to extract goals, scope, and acceptance criteria, and converts it into a deterministic task plan that starts the story-driven development workflow.

Core Features & Use Cases

  • Analyzes user stories to derive goals, scope, and acceptance criteria.
  • Decomposes the story into a task list with TDD/PLAN classifications and generates story-analysis.json, task-list.json, and an initial TODO.md.
  • Supports subsequent steps: decompose-tasks, assign-workflow, plan-review, and dev:developing initiation.
  • Provides a repeatable, auditable starting point for feature development.

Quick Start

Run the dev:story command on a new user story to generate story-analysis.json, task-list.json, and TODO.md, ready for further steps.

Frequently Asked Questions about dev:story

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert user stories into structured task lists and TODOs?

Task decomposition uses TDD and PLAN classifications to break down user stories into deterministic, actionable items, generating story-analysis.json and task-list.json for structured workflow selection.

What is the best way to generate a deterministic task plan from a feature description?

Generating a deterministic task plan from a feature description involves analyzing the user story to extract acceptance criteria and decomposing it into a structured task list with TDD/PLAN classifications.

How does story-driven development workflow start from a new user story?

Story-driven development starts by running the analysis on a new user story to generate story-analysis.json, task-list.json, and TODO.md, which serve as the repeatable, auditable starting point for subsequent development steps.

Can I use task decomposition with TDD classifications for my project planning?

Yes, you can use task decomposition with TDD classifications to structure project planning, as it converts user stories into a deterministic task list that guides test-driven and planning-based workflow selection.

Do I need any external dependencies to generate story-analysis.json and TODO.md?

No external dependencies are required to generate story-analysis.json and TODO.md, as the skill operates independently to extract goals and scope to initialize your development workflow.

What happens after generating an initial TODO.md from a user story?

After generating an initial TODO.md from a user story, the outputs support subsequent workflow steps including decompose-tasks, assign-workflow, plan-review, and initiating the actual development phase.