skills.rest
fcastrillo
fcastrilloCOMMUNITY
Explore all skills by this author →
GitHub

rai-epic-design

Frame strategic objectives into bounded epic scopes with ADRs and feature candidates.

Updated Feb 4, 2026
Search Tags:#planning#architecture#scoping#roadmap#feature-planning#epic-design
One-click install
npx skills add https://github.com/fcastrillo/carbtrack-ai --skill rai-epic-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rai-epic-design
Source: https://github.com/fcastrillo/carbtrack-ai/tree/main/.claude/skills/rai-epic-design
Command: npx skills add https://github.com/fcastrillo/carbtrack-ai --skill rai-epic-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams convert broad strategic objectives into a bounded epic with clear outcomes, architecture considerations, and actionable guidance.

Core Features & Use Cases

  • Structured objective framing, scope boundaries, ADRs, and feature decomposition for multi-feature initiatives (3-10 features).
  • Dependency mapping, risk assessment, and defined done criteria to enable predictable delivery.
  • Template-driven epic scope generation that feeds into the /work/epics workflow and parking-lot management.

Quick Start

Provide an initial epic scope using the template to define objective, scope, features, and ADRs.

Frequently Asked Questions about rai-epic-design

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

FAQPage Schema
How do I convert a strategic objective into a bounded epic scope?▼

Epic design transforms broad strategic objectives into structured multi-feature initiatives by defining scope boundaries, architectural decisions, feature decomposition, and done criteria to enable predictable cross-team delivery.

When do I need architectural decisions and cross-team alignment for feature planning?▼

Feature planning for epics requires architectural decisions and cross-team alignment when managing multi-feature initiatives of 3-10 features needing dependency mapping, risk assessment, and defined done criteria.

How do I break down a roadmap into features with dependencies and done criteria?▼

Break down a roadmap by generating feature candidates with sizes, mapping dependencies, assessing risks, and defining done criteria to produce a consolidated scope document for the initiative.

Does epic design work for single-feature tasks or smaller scoping initiatives?▼

Epic design targets multi-feature initiatives of 3-10 features requiring architectural decisions and cross-team alignment, making it unsuitable for smaller single-feature tasks or simple scoping initiatives.

What is the best way to document scope boundaries and ADRs for a new epic?▼

Document scope boundaries and ADRs using a template-driven approach that frames objectives and outputs a consolidated scope document, differentiating it from ad-hoc planning methods by ensuring structured cross-team alignment.

Why does feature planning fail without clear scope boundaries and risk assessment?▼

Feature planning fails without clear scope boundaries and risk assessment because multi-feature initiatives lack predictable delivery guidance, leading to unmanaged dependencies and undefined done criteria across teams.

Related Skills

Explore More Software Engineering Skills→
saolalabsaolalab
37

strategic-planning

Define company vision and generate measurable OKRs with quarterly timelines.

Official
Intermediate
DinxeshhDinxeshh

Sherpa

Decompose complex epics into 15-minute atomic steps with commit checkpoints.

Community
Advanced
foolpoet44foolpoet44
1

pm-knowledge-base

Provide Product Management frameworks for prioritization, goal setting, and strategy planning.

Community
Advanced
drusiferdrusifer
1

morpheus

Provide architectural oversight and refactoring guidance across engineering teams.

Community
Advanced