Convert product intent into an implementation-ready story file with acceptance criteria and tasks.
npx skills add https://github.com/yabafre/aped-claude --skill aped-story
Please help me install this Agent Skill. Skill: aped-story Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-story Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-story
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.
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.
High-intent search queries and answers about installing and using this skill.
Implementation-ready story generation converts product intent and existing architecture context into a structured story file with Given/When/Then acceptance criteria and defined tasks. It enforces branch safety by preventing writes to protected branches.
Branch-per-story discipline ensures each story lives on its own feature branch. The generation process validates branch safety, gates user approval before writing, and supports deferred feature-branch creation in solo mode to avoid protected branches.
Story generation requires strict epic-context loading from epics.md plus PRD, UX, and architecture references. It applies scoped lessons and prior-story outcomes from these sources to maintain consistency within an epic.
Yes, single story creation produces one story at a time with detailed Given/When/Then acceptance criteria. It updates state.yaml to advance the story lifecycle and gates user approval before writing the ready-for-dev artifact.
Story generation requires strict epic-context loading from epics.md plus PRD and architecture references to prevent vague, under-specified requests. Without this context, it cannot maintain consistency within an epic or apply prior-story outcomes.
Aped-story supports both worktree mode and solo mode with deferred feature-branch creation. It prepares the next story for the current epic by loading existing context and ticket information before producing the ready-for-dev story artifact.
yabafreDecompose PRDs into user-value epics with exact FR coverage validation.
normcrandallConvert user stories into code and tests with sequential execution.
iamsteveholmesOrchestrate Momentum story development with isolated worktrees and completion signals.
ajstack22Automates backlog grooming and user-story creation across Atlas workflows with acceptance-criteria validation.
