dev-stories

Generate user stories with DATO-QUANDO-ALLORA acceptance criteria from PRD documents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill dev-stories
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-stories
Source: https://github.com/MaxGiu67/plugin-MUCC/tree/main/dev-methodology/skills/dev-stories
Command: npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill dev-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms high-level product requirements into development-ready user stories with clear acceptance criteria, reducing ambiguity and accelerating handoff to engineering teams.

Core Features & Use Cases

  • Structured Story Generation: Converts features and epics from PRD and vision documents into user stories following the "As a..., I want..., so that..." format.
  • Robust Acceptance Criteria: Produces a minimum of four AC per story using the DATO-QUANDO-ALLORA pattern (happy path, error cases, edge case).
  • Planning & Traceability: Assigns story points (Fibonacci 1-13), MoSCoW priority, epic links, dependencies, orders stories by priority, and updates project status and changelog.
  • Use Case: Use during Phase 3 of spec-driven development to systematically convert PRD features into a specs/03-user-stories.md deliverable ready for sprint planning.

Quick Start

Create user stories from the PRD and vision files, generating specs/03-user-stories.md with detailed stories and at least four DATO-QUANDO-ALLORA acceptance criteria per story.

Frequently Asked Questions about dev-stories

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

FAQPage Schema
How do I generate user stories with acceptance criteria from a PRD?▼

To generate user stories with acceptance criteria from a PRD, convert features and epics into development-ready stories using the "As a..., I want..., so that..." format, adding at least four DATO-QUANDO-ALLORA acceptance criteria per story.

What is the DATO-QUANDO-ALLORA pattern for writing acceptance criteria?▼

The DATO-QUANDO-ALLORA pattern structures acceptance criteria by defining a given context, an event trigger, and an expected outcome, ensuring robust coverage of happy paths, error cases, and edge cases for user stories.

Can I automatically assign MoSCoW priority and story points to epics?▼

Yes, you can automatically assign MoSCoW priority and Fibonacci story points (1-13) to epics during story generation, ordering stories by priority to produce a sprint-ready deliverable.

What's the best way to structure user stories for sprint planning?▼

The best way to structure user stories for sprint planning is to create a table summary with detailed stories, epic links, dependencies, MoSCoW priority, and story points, outputting to a structured markdown file.

Does this user story generation approach update the project changelog?▼

Yes, this approach updates the project changelog and status files, automatically appending changes to specs/_status.md and specs/_changelog.md when generating the user stories markdown deliverable.