aped-story
CommunityTurn intent into an implementation-ready story
Software Engineering#acceptance criteria#product requirements#story generation#epic context#dev pipeline#branch-per-story#ticket integration
Authoryabafre
Version1.0.0
Installs0
System Documentation
What problem does it solve?
It prevents vague, under-specified “create story” requests by converting user intent plus existing PRD/UX/architecture context into an exact, dev-ready story artifact with disciplined file paths, tasks, and acceptance criteria.
Core Features & Use Cases
- Creates an implementation-ready single story: produces one story at a time with detailed Given/When/Then acceptance criteria.
- Enforces branch-per-story discipline: gates execution to avoid protected branches and ensures the story lives on its own feature branch (especially in solo mode).
- Leverages existing epic context and guidance: loads epics/PRD/UX/architecture/project-context and applies scoped lessons and prior-story outcomes to maintain consistency within an epic.
Quick Start
Tell your agent: Run aped-story to prepare the next story for the current epic, using the existing epics.md, PRD/UX/architecture context, and ticket information, and then produce the ready-for-dev story artifact.
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-story Download link: https://github.com/yabafre/aped-claude/archive/main.zip#aped-story 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.