reviewing-prd-scope

Evaluates PRD scope against decomposition signals and produces sequenced replacement PRDs.

Updated May 2, 2024
One-click install
npx skills add https://github.com/cman131/EatSomethingSourWhenYoureTired --skill reviewing-prd-scope-cman131
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewing-prd-scope
Source: https://github.com/cman131/EatSomethingSourWhenYoureTired/tree/main/.claude/skills/reviewing-prd-scope
Command: npx skills add https://github.com/cman131/EatSomethingSourWhenYoureTired --skill reviewing-prd-scope-cman131

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? PRDs that bundle loosely coupled features delay delivery and hide dependencies. This Skill analyzes a written PRD to determine whether its scope is appropriate or should be split into smaller, dependency-sequenced documents. ## Core Features & Use Cases - Three-Signal Analysis: Checks independent shippability, one-way dependency direction, and scope size (>10 stories or >20 ACs) to identify split candidates. - Guided Split Workflow: Presents candidates with quoted evidence, plans content distribution, and executes approved splits into cross-linked PRDs. - Safe Execution: Archives the original PRD, asks the user about ambiguous stories or ACs, and cross-links prerequisite and dependent documents. - Use Case: You have a 15-story PRD covering both an event store and a points system. The Skill flags the event store as independently shippable, proposes a two-PRD split, and writes both documents in dependency order. ## Quick Start Review the PRD at plans/feature-x.md and tell me whether its scope should be decomposed into smaller PRDs.

Frequently Asked Questions about reviewing-prd-scope

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

FAQPage Schema
How do I know if my PRD is too large and should be split?▼

A PRD is a split candidate when a feature cluster ships value independently, has a one-way dependency on another cluster, or exceeds soft thresholds of more than 10 user stories or 20 acceptance criteria. Size alone prompts scrutiny but does not mandate a split.

How to split a PRD into multiple documents?▼

Cluster goals, stories, and ACs by feature surface, then write new PRDs in dependency order using the PRD template. Move content to the owning PRD, cross-link prerequisite and dependent documents, and archive the original in plans/archive/.

What signals indicate a PRD should be decomposed?▼

Three signals: independent shippability (a cluster needs nothing from other clusters), one-way dependency direction (A needs B but not vice versa), and scope size. Mutual dependencies are not split candidates.

Where do shared decisions go when splitting a PRD?▼

Shared resolved decisions and open questions spanning both PRDs go in the prerequisite PRD, since it ships first and owns shared infrastructure decisions. The dependent PRD's dependencies section notes where the decision lives.

When should a large PRD not be split?▼

A large, tightly coupled PRD stays together. Scope size alone does not justify decomposition; only independent shippability or one-way dependency signals make the call. Splits that already exist as sibling documents are never proposed.