prd-v07-epic-scoping

Transform PRD requirements into context-window sized EPICs with dependencies.

193|9|Updated Jul 10, 2025
One-click install
npx skills add https://github.com/mattgierhart/PRD-driven-context-engineering --skill prd-v07-epic-scoping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-v07-epic-scoping
Source: https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v07-epic-scoping
Command: npx skills add https://github.com/mattgierhart/PRD-driven-context-engineering --skill prd-v07-epic-scoping

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

The skill translates broad PRD requirements into cognition-friendly EPICs that fit within working memory, enabling reliable AI-driven planning and execution.

Core Features & Use Cases

  • Context capsule sizing helps pre-load and working-room planning to prevent context overload.
  • Dependency mapping identifies build order, data, API, and UI boundaries, and enables parallel work.
  • Execution planning templates standardize EPIC outputs with IDs, references, and context windows for traceability.
  • Use Case: When starting a new PRD-driven project, generate EPICs that cover auth, data, API, and UI components with clear dependencies.

Quick Start

Create the first EPIC scaffold (EPIC-001) and load the SoT, then begin with Phase A: Plan.

Frequently Asked Questions about prd-v07-epic-scoping

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

FAQPage Schema
How do I break down a PRD into EPICs for AI context windows?

To break down a PRD into EPICs for AI context windows, the skill transforms broad PRD requirements into standardized EPIC entries with dependency mapping and pre-load token budgets. This sizing prevents context overload and enables reliable AI-driven execution during handoffs.

What is context capsule sizing in agile project planning?

Context capsule sizing in agile project planning is the process of pre-loading and bounding working-room capacity to prevent context overload. It matches EPIC boundaries to AI working memory limits, ensuring specifications remain cognition-friendly for reliable automated handoffs.

How do I map dependencies when splitting PRD requirements into EPICs?

To map dependencies when splitting PRD requirements, the skill identifies build order boundaries across API, DBT, FEA, and ARC artifacts. It outputs standardized EPIC entries with clear dependency tracking to enable parallel work and traceable AI execution handoffs.

Can I generate EPIC scaffolds for API and UI components from a PRD?

Yes, you can generate EPIC scaffolds covering API, data, and UI components directly from a PRD. The skill creates standardized EPIC outputs with unique IDs, references, and context windows, starting with an initial scaffold like EPIC-001 to load the Source of Truth.

Why do my AI planning handoffs fail when processing large PRD requirements?

AI planning handoffs fail when processing large PRD requirements because broad specifications exceed working memory and cause context overload. Enforcing pre-load token budgets and context window sizing resolves this by fragmenting requirements into cognition-friendly EPICs.