stories

Name: stories
Availability: InStock
Author: Panaversity

Convert specs or PRDs into named-persona user stories with testable acceptance criteria.

28|19|Updated Mar 5, 2026

Search Tags:#persona #prd #stories #sprint #acceptance-criteria #story-writing #spec-to-stories

Ready to run

npx skills add https://github.com/panaversity/agentfactory-business-plugins --skill stories-panaversity

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stories
Source: https://github.com/panaversity/agentfactory-business-plugins/tree/main/product-strategy/skills/stories
Command: npx skills add https://github.com/panaversity/agentfactory-business-plugins --skill stories-panaversity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams convert vague specs and PRDs into concrete, named-persona user stories that are ready for development, ensuring clarity and testability from the start.

Core Features & Use Cases

Automatically derive As a [Persona], I want to [capability], So that [outcome] stories from a given spec or PRD.
Enforce Acceptance Criteria formatting: each AC is testable, uses Given/When/Then where possible, and avoids compound statements.
Flag coverage gaps and unusable ACs to keep the backlog complete and sprint-ready.
Ensure stories align with sprint goals by sizing and grouping by distinct user flows and personas.

Quick Start

Provide a set of named-persona user stories derived from the input spec for sprint planning.

Frequently Asked Questions about stories

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

FAQPage Schema

How do I convert a PRD into user stories for sprint planning?▼

To convert a PRD into user stories, translate the spec into 'As a [Persona], I want to [capability], So that [outcome]' statements grouped by user flow. This ensures each story is sprint-completable with independent, testable acceptance criteria.

What is the best way to write acceptance criteria that are testable?▼

The best way to write testable acceptance criteria is to use Given/When/Then formatting while avoiding compound statements with 'and'. This ensures each criterion is independent and can be verified as a distinct test case during development.

How do I identify coverage gaps when translating specs to user stories?▼

To identify coverage gaps when translating specs, review the generated user stories for missing flows or unusable acceptance criteria. Flagging these gaps keeps the backlog complete and ensures all requirements are expressible as testable stories.

Can I use named personas in user stories derived from a spec?▼

Yes, you can use named personas in user stories by referencing a defined product.local.md or a reasonable named alternative. This ensures translated specs group capabilities by distinct user flows and specific persona identities.

Why should user stories be completable in one sprint?▼

User stories should be completable in one sprint to align with sprint goals and ensure manageable development scope. Sizing stories by distinct user flows and personas keeps the backlog sprint-ready and delivery predictable.