aped-discuss-epic
CommunityLock epic-wide implementation decisions early
Product & Management#Claude Code#spec review#epic planning#pipeline automation#SPIDR#implementation decisions#architecture consistency
Authoryabafre
Version1.0.0
Installs0
System Documentation
What problem does it solve?
It prevents epic-level implementation decisions from being re-derived differently for each story, reducing drift between aped-arch system choices and per-story execution plans.
Core Features & Use Cases
- Epic decision-locking: Captures concrete cross-cutting choices that must be shared across the stories inside one epic.
- SPIDR-driven completeness: Forces Spike/Paths/Interfaces/Data/Rules coverage so nothing essential is skipped.
- Reviewer-verified concreteness: Dispatches a spec reviewer to ensure decisions are binding (not aspirational) and consistent with
architecture.md. - Cache-first workflow: Reads required epic context cache and halts with guidance if
aped-storyhasn’t produced it yet.
Quick Start
Use the skill to lock decisions for epic 3 when you’re about to start story planning for that epic by asking: discuss epic 3 and lock its implementation decisions.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: aped-discuss-epic Download link: https://github.com/yabafre/aped-claude/archive/main.zip#aped-discuss-epic Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.