skills.rest
ondrasek
ondrasekCOMMUNITY
Explore all skills by this author →
GitHub

refine

Refine GitHub issues into structured epics and user stories with acceptance criteria.

2|1|Updated Feb 15, 2026
Search Tags:#github#decomposition#backlog#INVEST#epic#refine#user-story
One-click install
npx skills add https://github.com/ondrasek/cc-plugins --skill refine-ondrasek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: refine
Source: https://github.com/ondrasek/cc-plugins/tree/main/plugins/github-issues/skills/refine
Command: npx skills add https://github.com/ondrasek/cc-plugins --skill refine-ondrasek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Transform vague GitHub issues into clearly defined epics and actionable user stories to improve planning, alignment, and delivery quality.

Core Features & Use Cases

  • Structured decomposition: Convert issues into epics and multiple stories using INVEST and decomposition guides.
  • Reference-driven refinement: Apply cross-cutting guides from epic-guide.md, user-story-guide.md, and splitting-techniques.md to shape acceptance criteria and scope.
  • Consistent documentation: Produce ready-to-use epic bodies and story templates with cross-links to related issues for traceability.
  • Review & governance: Provide prompts for team reviews, clarifying questions, and validation against scope constraints.

Quick Start

Tell me a rough issue description and I will generate an epic with suggested stories and acceptance criteria.

Frequently Asked Questions about refine

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

FAQPage Schema
How do I turn rough GitHub issues into structured epics and user stories?▼

You can refine rough GitHub issues into structured epics and user stories by applying INVEST principles and decomposition guides to generate a refined epic body and validated stories with acceptance criteria.

What is the best way to decompose a vague GitHub issue into actionable stories?▼

Decomposing a vague GitHub issue involves applying reference-driven splitting techniques to break the scope into multiple user stories, shaping clear acceptance criteria and cross-linked documentation for traceability.

How do I apply INVEST principles to validate user stories in a GitHub backlog?▼

Applying INVEST principles to validate user stories involves checking each story against Independent, Negotiable, Valuable, Estimable, Small, and Testable constraints using guided prompts to clarify scope and ensure readiness.

Can I generate acceptance criteria for epics directly from a rough issue description?▼

Yes, you can generate acceptance criteria for epics directly from a rough issue description by leveraging epic and user story reference guides to shape scope constraints and produce ready-to-use story templates.

Does this issue refinement approach support team reviews and scope validation?▼

Yes, this issue refinement approach supports team reviews by providing prompts for clarifying questions and validating generated stories against scope constraints before creation or linkage in GitHub.

When should I not use automated epic decomposition for backlog refinement?▼

You should avoid automated epic decomposition when a rough GitHub issue lacks sufficient context or domain detail, as reference-driven refinement requires baseline scope information to produce validated stories.

Related Skills

Explore More Product & Management Skills→
hoavdchoavdc
21

codexkit-backlog-refiner

Transform raw backlog items into INVEST-compliant user stories with acceptance criteria.

Community
Intermediate
Eric-Pacheco95Eric-Pacheco95

sprint-planning

Generate a Markdown sprint plan with committed and stretch stories and risks.

Community
Advanced
LGuguiLGugui

github-project-management

Automate GitHub issue management and project board synchronization with Claude Flow.

Community
Advanced
newkayak12newkayak12
1

user-story-splitting

Decompose large user stories into smaller stories using eight splitting patterns.

Community
Intermediate