epic-scoping

Automate epic scoping through structured questioning to populate epic-spec.md.

91|10|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/marcusgoll/Spec-Flow --skill epic-scoping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-scoping
Source: https://github.com/marcusgoll/Spec-Flow/tree/main/.claude/skills/epic-scoping
Command: npx skills add https://github.com/marcusgoll/Spec-Flow --skill epic-scoping

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reduces ambiguity in epic scope by guiding interactive, structured questioning against a centralized question bank.

Core Features & Use Cases

  • 5-round interactive scoping: initial, refinement, success metrics, dependencies, complexity
  • Answers map to epic-spec.md sections (Business Value, Subsystems, Metrics, Constraints)
  • Progress indicators and completion summary

Quick Start

Load questions from the bank and answer in five rounds to populate epic-spec.md.

Frequently Asked Questions about epic-scoping

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

FAQPage Schema
How do I structure epic scoping to reduce ambiguity in planning?

Epic scoping uses structured, round-based questioning to populate a detailed epic specification. Five interactive rounds gather business goals, subsystem choices, success metrics, dependencies, and complexity estimates, capturing requirements across backend, frontend, database, and infrastructure layers in a centralized epic-spec.md file.

What's the best way to define epic requirements and success metrics?

A question bank guides you through conditional follow-ups based on your subsystem selections, ensuring you capture functional requirements, success metrics, constraints, and complexity in each round. Answers automatically update epic-spec.md with progress indicators and a completion summary.

Can I use interactive questioning to scope requirements across multiple technical layers?

Yes. The Skill automates scoping across Business Goal, Subsystems, Backend, Frontend, Database, and Infrastructure scopes in one workflow. Each layer's requirements are captured through structured questioning, then consolidated into a single epic specification.

How does a question bank improve epic planning consistency?

A centralized question bank standardizes the information gathered for each epic, eliminating gaps and inconsistencies. Conditional follow-ups tailor questions based on your subsystem choices, ensuring relevant requirements are captured for your specific technical context.

What does the epic-spec.md output include?

Epic-spec.md contains YAML frontmatter, sections for business value, subsystem architecture, technical scope per layer, success metrics, dependencies, constraints, and complexity ratings. Progress indicators and a completion summary track scoping progress.