Decompose PRDs into user-value epics with exact FR coverage validation.
npx skills add https://github.com/yabafre/aped-claude --skill aped-epics
Please help me install this Agent Skill. Skill: aped-epics Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-epics Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-epics
This skill turns a PRD into an organized epic and story plan, ensuring every FR maps to exactly one epic and that coverage is validated before implementation.
Run aped-epics when you want to break your PRD into epics and a story list, and then confirm the A/P/C gate when prompted.
High-intent search queries and answers about installing and using this skill.
PRD decomposition into epics groups functionality by user value rather than technical layers, producing a per-epic story list with clear outcomes and FR mapping. It enforces exact FR-to-epic coverage validation before writing planning artefacts.
User story mapping organizes product requirements into user-value epics, ensuring every functional requirement maps to exactly one epic. This prevents coverage gaps and keeps planning focused on user accomplishments rather than technical architecture.
Yes, epic decomposition requires loading upstream PRD, architecture, and UX inputs along with APED configuration. These provide the functional requirements and design context needed to validate FR-to-epic coverage accurately.
FR coverage validation runs during epic design and surfaces a running coverage matrix checking that every PRD functional requirement maps to exactly one epic. It gates user approval before writing outputs to ensure no requirement is missed.
Yes, epic decomposition produces a per-epic story list and planning artefacts like epics.md without creating story files. When a ticket system is configured, it seeds ticket and milestone planning after user confirmation gates are passed.
User-value epic decomposition groups functionality by what users can accomplish, validating FR coverage and producing a story list with clear user outcomes. An approval gate ensures the plan meets coverage requirements before artefacts are written or tickets synced.
JingyiWngValidate implementation readiness of PRD, UX, architecture, and epics.
humansysCreate a story branch and scope commit from a development branch.
automatedigitalAutomate ticket lifecycle from ideation to merged pull request across ticket trackers and GitHub.
co-cddoDecompose product requirements into epics and stories with acceptance criteria.
