skills.rest
thrawn01
thrawn01COMMUNITY
Explore all skills by this author →
Website𝕏@thrawn01GitHub

stories-review

Review user stories against a PRD using a three-pass agent workflow.

11|Updated Sep 5, 2025
Search Tags:#agile#quality-assurance#acceptance-criteria#requirements-analysis#story-review#prd-alignment#iteration-loop
One-click install
npx skills add https://github.com/thrawn01/claude-dotfiles --skill stories-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stories-review
Source: https://github.com/thrawn01/claude-dotfiles/tree/main/skills/stories-review
Command: npx skills add https://github.com/thrawn01/claude-dotfiles --skill stories-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams and engineers identify gaps, inconsistencies, and missing acceptance criteria in user stories by applying a disciplined three-pass review workflow against the PRD. It guides teams to ship stories that are complete, non-contradictory, and scoped correctly.

Core Features & Use Cases

  • Three-pass evaluation: a Review Agent detects issues, a Validation Agent confirms or rejects findings, and a Skeptic Agent challenges confirmed items to reduce false positives.
  • Iterative improvement: fixes are applied and the user stories are re-evaluated up to a maximum of three iterations until no new confirmed findings emerge.
  • Context-aware validation: can read the PRD, a domain glossary (CONTEXT.md), and architecture context via ADRs to ensure terminology and constraints are respected.

Quick Start

Supply the user stories file path and the PRD path to initiate the three-pass review loop and return findings.

Frequently Asked Questions about stories-review

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

FAQPage Schema
How do I review user stories against a PRD for missing acceptance criteria?▼

Reviewing user stories against a PRD requires a three-pass workflow that compares story documents with product requirements to identify gaps, inconsistencies, and missing acceptance criteria. This process loops iteratively until no new confirmed findings emerge.

What is the best way to validate user stories for scope alignment in agile?▼

Validating user stories for scope alignment involves applying a disciplined multi-agent review that checks stories against the PRD, domain glossary, and architecture records. This iterative validation confirms findings and challenges them to reduce false positives.

How do I use ADRs and CONTEXT.md for agile requirements analysis?▼

ADRs and CONTEXT.md provide architecture context and domain glossary terms for requirements analysis. The review workflow reads these files on demand to ensure user stories respect terminology and structural constraints defined in the PRD.

Can I automatically fix user story gaps found during a PRD alignment review?▼

Fixing user story gaps can be automated when appropriate. The review workflow supports auto-apply fixes for identified issues and prompts for clarifications on ambiguous items, re-evaluating the stories up to three iterations.

Do I need a separate PRD file to check user story quality?▼

A separate PRD file is required to check user story quality. The review workflow expects a user stories file and a PRD in the same directory to effectively analyze scope alignment and identify missing requirements.

Related Skills

Explore More Product & Management Skills→
bacocobacoco
67

bmad-product-planning

Generate PRD.md and epics.md from validated discovery insights.

Community
Advanced
yunshu0909yunshu0909
742

prd-doc-writer

Write and iteratively refine PRDs and user stories with ASCII wireframes and Mermaid diagrams.

Community
Advanced
qa-amanqa-aman
19

write-user-stories

Convert product briefs into user stories with Given/When/Then acceptance criteria.

Community
Advanced
HyperionBurnHyperionBurn

ralph

Run PRD-driven persistence loops until all acceptance criteria pass reviewer verification.

Community
Advanced