skills.rest
subvisual
subvisualOFFICIAL
Explore all skills by this author →
WebsiteGitHub

epics

Define and maintain durable epic documents that bundle PRD requirements into delivery workstreams.

Updated Jul 10, 2026
Search Tags:#requirements#product management#prioritization#epics#prd#delivery planning#moscow
One-click install
npx skills add https://github.com/subvisual/the-a-team --skill epics-subvisual
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: epics
Source: https://github.com/subvisual/the-a-team/tree/main/.claude/skills/epics
Command: npx skills add https://github.com/subvisual/the-a-team --skill epics-subvisual

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Delivery work often jumps straight from a PRD to tickets, losing the durable structure that ties requirements to user jobs and priorities. This Skill structures that middle layer by writing durable, id-stable epic files that trace requirement IDs to the jobs they serve. ## Core Features & Use Cases - Epic Definition: Create epics from a PRD's requirement IDs or standalone from an objective plus jobs, written to docs/product/epics/NN-<slug>.md. - Epic Revision: Refine, split, merge, park, complete, or supersede existing epics while preserving history — superseded epics are never deleted and milestone back-references are carried through unchanged. - Explicit Prioritization: Apply MoSCoW by default, or 2x2, Eisenhower, or RICE when trade-off data exists, with the rationale recorded in the epic. - Use Case: After a feature PRD is approved, run this Skill to bundle its requirement IDs (e.g. assisted-triage-v0: R1–R3) into epics traced to JTBD ids, ready for ticket-writer to decompose into the backlog. ## Quick Start Use the epics skill to decompose the requirements in docs/features/assisted-triage-v0/prd.md into epics under docs/product/epics/.

Frequently Asked Questions about epics

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

FAQPage Schema
How do I break a PRD into epics for delivery planning?▼

Run this Skill in DEFINE mode against the feature's prd.md. It bundles requirement IDs into epics shaped around one primary job-outcome each, writes them to docs/product/epics/NN-<slug>.md, and records the feature slug in frontmatter.

What prioritization methods does epic planning support?▼

MoSCoW is the default when shaping scope without effort/impact data. A 2x2 impact-versus-effort matrix is used when trade-off data exists, with Eisenhower and RICE offered as alternatives. The chosen approach and rationale are recorded in the epic.

Can I use this Skill for quarterly roadmap or portfolio planning?▼

No. Full roadmap and portfolio planning across quarters was deliberately not ported from the source skill. This Skill is scoped to defining and maintaining epics between a PRD and the ticket backlog for 0-to-1 delivery work.

What happens when an epic needs major changes?▼

A reshaped epic becomes a new file whose Related section cites supersedes [[epic:NN-...]], and the old epic flips to status: superseded with a pointer. Epics are never deleted or renumbered, and any existing milestone frontmatter is preserved.

Why must the milestone field never be edited in an epic?▼

The milestone frontmatter key is written only by the harness's issues phase after projecting the epic to GitHub. Dropping it during a revision strips the back-reference, causing the next run to create a duplicate milestone in GitHub.

Does the epics skill write tickets or acceptance criteria?▼

No. Ticket writing and acceptance criteria belong to the ticket-writer skill, which decomposes the epics this Skill produces. This Skill also never creates or revises jobs, which is the jobs-to-be-done skill's role.

Related Skills

Explore More Product & Management Skills→
Lia-CreativeLia-Creative
1

jtbd

Define jobs-to-be-done statements and map their requirements for epic planning.

Official
Basic
az9713az9713

plan-create-stories

Decomposes a PRD into engineer-ready Jira or GitHub issue tickets with acceptance criteria.

Community
Intermediate
curdxcurdx
4

requirements

Generate user stories and acceptance criteria from an active spec.

Community
Intermediate
getcrew44getcrew44
358

roadmap-planning

Produce outcome-driven product roadmaps with prioritized, dependency-aware epics.

Official
Intermediate