refine

Refine GitHub issues into action-ready engineering briefs.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/matteobortolazzo/claude-tools --skill refine-matteobortolazzo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refine
Source: https://github.com/matteobortolazzo/claude-tools/tree/main/ccflow/skills/refine
Command: npx skills add https://github.com/matteobortolazzo/claude-tools --skill refine-matteobortolazzo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refinement of GitHub issues into clear, unambiguous briefs that are ready for planning and implementation.

Core Features & Use Cases

  • Ticket intake and context parsing: Extracts ticket ID, optional user context, and current ticket metadata to inform refinement.
  • Pre-flight checks and guidance: Verifies ticket state, labels, and dependencies, then prompts for decisions when needed.
  • Structured outputs: Produces a focused briefing that includes summary, acceptance criteria, risks, and next-step actions.

Quick Start

Provide a ticket identifier and optional context to begin interactive refinement.

Frequently Asked Questions about refine

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

FAQPage Schema
How do I turn GitHub issues into clear, ready-to-plan briefs for engineers?

Backlog refinement automates turning GitHub issues into clear, action-ready briefs by reading ticket metadata, analyzing acceptance criteria, checking dependencies, and producing refined descriptions with risk notes and implementation considerations.

What does backlog refinement do for frontend, backend, and design tickets?

Backlog refinement processes frontend, backend, and design tickets by extracting ticket context, verifying state and dependencies, and generating structured outputs that include summary, acceptance criteria, risks, and next-step actions for planning.

How do I add acceptance criteria and dependency checks to GitHub issue planning?

Acceptance criteria and dependency checks are handled automatically by analyzing ticket metadata, prompting for clarifications at key decision points, and producing structured risk notes and implementation considerations for each issue.

Can I use backlog refinement for tickets within a specific workflow like ccflow?

Backlog refinement works within the claude-tools ccflow workflow, handling ticket context, acceptance criteria clarity, and dependencies for frontend, backend, and design tickets while prompting for decisions via AskUserQuestion at key points.

What do I need to provide to start refining a GitHub ticket into an action-ready brief?

To begin interactive refinement, provide a ticket identifier and optional user context, which the system uses to extract metadata, run pre-flight checks, and generate a focused briefing with summary, acceptance criteria, risks, and next-step actions.