prd-v07-epic-scoping
Epic Scoping
Position in workflow: v0.6 Technical Specification → v0.7 Epic Scoping → v0.7 Test Planning
Consumes
This skill requires prior work from v0.6 Technical Specification:
- API-* endpoint contracts (from v0.6 Technical Specification) — Endpoints define what must be built; API count signals complexity
- DBT-* data model specifications (from v0.6 Technical Specification) — Data entities and relationships inform natural boundaries
- ARC-* architecture decisions (from v0.6 Architecture Design) — System structure, module boundaries, and integration patterns define scoping boundaries
- FEA-* feature entries with MVP-SCOPE (from v0.3 Features Value Planning) — MVP boundary determines EPIC scope; post-MVP features defer to backlog
- Existing EPIC-* entries (if brownfield) — Inherited work packages constrain and sequence new EPICs
This skill assumes v0.6 Technical Specification is complete with API-/DBT- entries providing implementation contracts.
Produces
This skill creates/updates:
More from mattgierhart/prd-driven-context-engineering
prd-v05-technical-stack-selection
Determine technologies needed to build the product, making build/buy/integrate decisions during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on requests to select tech stack, evaluate technologies, make build vs. buy decisions, discover existing assets, or when user asks "what technologies?", "select tech stack", "build or buy?", "what do we reuse?", "existing stack", "technical decisions", "what tools do we need?", "evaluate solutions". Consumes FEA- (features), SCR- (screens), RISK- (constraints). Outputs TECH- entries with decisions, rationale, and trade-offs. Feeds v0.6 Architecture Design.
11prd-v09-gtm-strategy
>
8prd-v04-user-journey-mapping
Map user missions from trigger to value moment, organizing features into coherent paths during PRD v0.4 User Journeys. Triggers on requests to map user journeys, define user flows, describe how users accomplish goals, or when user asks "map user journeys", "define user flows", "user missions", "how do users accomplish X?", "journey mapping", "what steps do users take?", "pain to value flow". Consumes PER- (Persona Definition), FEA- (Feature Value Planning), KPI- (Outcome Definition). Outputs UJ- entries with step flows, pain points, and value moments. Feeds v0.4 Screen Flow Definition.
8prd-v03-features-value-planning
Define and prioritize features with strategic traceability during PRD v0.3 Commercial Model. Triggers on requests to define features, prioritize capabilities, scope MVP, map features to pricing tiers, identify parity vs. delta features, or when user asks "what features do we build?", "what's in MVP?", "which features matter?", "feature priority", "parity features", "what's our delta?". Consumes KPI- (Outcome Definition), BR- (Pricing Model, Moat), and CFD- (Market Moat Analysis) from v0.3. Outputs FEA- entries with strategic traceability and BR-FEA- governance rules. Feeds v0.4 User Journeys.
4ghm-gate-check
>
1prd-v08-runbook-creation
>
1