story-coverage

Identify missing user stories in PRDs by cross-checking personas, goals, and archetypal flows.

3|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/infraspecdev/tesseract --skill story-coverage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-coverage
Source: https://github.com/infraspecdev/tesseract/tree/main/shield/skills/general/story-coverage
Command: npx skills add https://github.com/infraspecdev/tesseract --skill story-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Story coverage helps you spot gaps in a PRD by checking whether every persona and goal combination is represented, whether the expected domain flows are covered, and whether supporting sections introduce unaddressed actions.

Core Features & Use Cases

  • Persona-goal coverage analysis: Derives the stories that should exist for each user persona and goal pairing, then flags missing happy paths or missing recovery paths.
  • Domain archetype checking: Compares the PRD against common feature flows such as authentication, payment, content, lifecycle, billing, and observability to find missing archetypal scenarios.
  • Orphan reference detection: Scans NFR, rollout, GTM, and risk sections for actions like rollback, delete, migrate, or deactivate that do not have matching stories.
  • Use Case: A product manager drafts a PRD for a new internal workflow and uses this Skill to reveal that account deletion, recovery, and failure handling were never written down.

Quick Start

Ask the story-coverage skill to review this PRD and return the missing stories, missing archetypes, and orphan references in structured JSON.

Frequently Asked Questions about story-coverage

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

FAQPage Schema
How do I find missing user stories in a PRD before launch?

To find missing user stories in a PRD, cross-check defined personas and goals against existing sections to identify unaddressed actions. This analysis flags missing happy paths and recovery paths for each persona-goal pairing.

What is story coverage analysis in agile product management?

Story coverage analysis checks whether every persona and goal combination in a product specification is represented by expected user stories. It evaluates domain archetype flows and supporting sections to reveal coverage gaps with severity levels.

How do I check my PRD for missing archetypal flows like authentication and billing?

You check your PRD for missing archetypal flows by comparing the document against standard feature domain templates for authentication, payment, content, lifecycle, billing, and observability to find missing scenarios.

Can I detect orphan references in non-functional requirements and rollout sections?

Yes, you can detect orphan references by scanning NFR, rollout, GTM, and risk sections for actions like rollback, delete, migrate, or deactivate that lack matching user stories in the product specification.

What format does the PRD need to be in for user story gap analysis?

The PRD requires structured inputs for personas, goals, feature domain, and existing sections to perform user story gap analysis. This structure allows the review to return precise coverage gaps, missing archetypes, and orphan references in JSON.