From story-driven
Epic design document template. Use when creating new epic documents or need epic structure reference.
How this skill is triggered — by the user, by Claude, or both
Slash command
/story-driven:epic-templateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Status: Draft | In Progress | Completed
Status: Draft | In Progress | Completed Target version: [x.y]
These features are explicitly outside of the initial release:
[Why is this epic needed? What problem does it solve?]
Design goals:
[Goal 1] [Description of what this goal means]
[Goal 2] [Description]
[Goal 3] [Description]
[Detailed design information]
[Code examples, schema definitions, etc.]
[More details]
[Describe new user-facing features, APIs, UI components, or endpoints]
Examples:
[Example usage or interaction]
[List any changes to existing behavior]
[Implementation guidance, constraints, technical decisions]
[More technical notes]
[Error message example]
[How to handle this case]
Creates, edits, and verifies skills using a test-driven development approach with pressure scenarios and subagents.
npx claudepluginhub joshuarweaver/cascade-code-general-misc-4 --plugin kecbigmt-cc-plugins