skills.rest
yabafre
yabafreCOMMUNITY
Explore all skills by this author →
GitHub

aped-discuss-epic

Lock per-epic implementation decisions into epics-context files before story planning.

2|Updated Mar 12, 2026
Search Tags:#Claude Code#spec review#epic planning#pipeline automation#SPIDR#implementation decisions#architecture consistency
One-click install
npx skills add https://github.com/yabafre/aped-claude --skill aped-discuss-epic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aped-discuss-epic
Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-discuss-epic
Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-discuss-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

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-story hasn’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.

Frequently Asked Questions about aped-discuss-epic

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

FAQPage Schema
How do I lock epic-wide implementation decisions to prevent story drift?▼

Epic implementation decision-locking prevents story drift by capturing concrete cross-cutting choices across the SPIDR axes (Spike, Paths, Interfaces, Data, Rules) and appending them to the epic context file. This ensures all stories within the epic share consistent architecture decisions.

What are epic-level implementation decisions and when do I need to lock them?▼

Epic-level implementation decisions are cross-cutting choices between system-level architecture and per-story execution plans. You need to lock them before spawning story files to prevent each story from re-deriving architectural choices differently and causing drift.

How do I ensure architecture consistency across all stories in an epic?▼

Ensure architecture consistency by dispatching a spec reviewer to verify decisions are binding and align with architecture.md. Capturing a concrete 3–7 decision set with full SPIDR axis coverage guarantees nothing essential is skipped across stories.

Do I need an epic context cache before locking implementation decisions?▼

Yes, you need the epic context cache produced during story preparation. The decision-locking workflow reads the required cache first and halts with guidance if the cache is not present, preventing decision-locking without prerequisite context.

Why does my epic planning fail when cross-cutting choices are inconsistent?▼

Epic planning fails because inconsistent cross-cutting choices cause drift between system architecture and per-story execution. Locking a reviewed 3–7 decision set ensures choices are binding rather than aspirational, maintaining alignment with architecture.md.

Related Skills

Explore More Product & Management Skills→
richardrimanrichardriman
2

crafter-map-project

Analyzes repository structure and generates .cftter/ context files.

Community
Intermediate
yabafreyabafre
2

aped-sprint

Orchestrate parallel story dispatch into per-story worktrees within an APED project.

Community
Advanced
ncptuanncptuan

bmad-quick-dev

Convert coding requests into scoped specifications and working code artifacts.

Community
Advanced
kanitmann01kanitmann01

fullstack-architect

Define and enforce scalable architecture decisions across the monorepo.

Community
Advanced