refine

Refine epics and stories through phase-gated cross-functional analysis.

10|1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/thoreinstein/beads-workflow --skill refine-thoreinstein
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refine
Source: https://github.com/thoreinstein/beads-workflow/tree/main/skills/refine
Command: npx skills add https://github.com/thoreinstein/beads-workflow --skill refine-thoreinstein

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refine epics and stories through cross-functional analysis and requirements gathering to produce actionable backlog items that align stakeholders and drive delivery.

Core Features & Use Cases

  • Agent delegation: Delegate requirements analysis, backlog refinement, and story breakdown to the agile-delivery-lead sub-agent to ensure clear business value.
  • Phase-driven workflow: Enforces phase boundaries (Epic Refinement, Story Refinement) with STOP prompts after each phase to secure alignment.
  • Execution-ready artifacts: Produces well-scoped tickets with mandatory flags (parent and description) ready for creation.
  • Cross-functional gaps: Identifies security, QA, and UX considerations during refinement to improve quality and compliance.

Quick Start

Start by delegating refinement tasks to the agile-delivery-lead sub-agent and initiating Phase 1 (Title & Description). Then proceed through Phases 2–5, stopping after each phase for user input. When ready, generate execution-ready stories with a command pattern like: bd create --parent <epic-id> --description "<desc + AC>" "<title>"

Frequently Asked Questions about refine

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

FAQPage Schema
How do I refine epics and stories for an agile backlog?

To refine epics and stories, this Skill delegates cross-functional analysis to an agile-delivery-lead agent, guiding requirements clarification through a phase-gated workflow. It identifies security, QA, and UX gaps to produce actionable, execution-ready backlog items.

How does cross-functional analysis work during story breakdown?

Cross-functional story breakdown works by evaluating requirements across security, QA, and UX domains during the refinement phases. This structured approach identifies compliance and quality considerations early, ensuring the generated tickets have comprehensive acceptance criteria.

What is the process for validating acceptance criteria in agile delivery?

Validating acceptance criteria involves a phase-driven workflow with STOP prompts after each phase to secure stakeholder alignment. The process requires mandatory flags for parent epics and descriptions, ensuring tickets are properly scoped before creation.

Can I generate execution-ready stories directly from a refined backlog?

Yes, you can generate execution-ready stories by completing the phase-gated refinement process and using a specific command pattern. This command creates tickets with mandatory parent IDs and combined descriptions with acceptance criteria.

Do I need an agile-delivery-lead agent to break down requirements?

Yes, requirements analysis and story breakdown are delegated to a dedicated agile-delivery-lead sub-agent. This ensures business value alignment and structured backlog creation throughout the epic and story refinement phases.