Docs

/ refine

Triage a raw capture or refine an existing issue's spec, priority, and estimate.

The /refine command takes a rough issue and makes it ready for development. It handles two scenarios: triaging quick captures that need classification, and refining backlog items that need fuller specs.

Usage

agent chat 
/refine ENG-145
agent chat 
triage the new issues in backlog
agent chat 
flesh out ENG-200, it needs acceptance criteria

Two Paths

Triage Path

For quick captures that came in without full details. FlyDocs classifies the issue type, applies the right template, and sets an initial priority. This turns a one-line note into a structured issue.

Refinement Path

For backlog items that need to be fleshed out before development. FlyDocs assesses the current description for completeness, refines the acceptance criteria, adds technical notes, sets an estimate, and transitions the issue to Ready.

Gates

An issue is not considered refined until all three gates are met:

  • Acceptance criteria defined: Clear, testable criteria for what "done" looks like
  • Estimate set: A complexity estimate from 1 to 5
  • Priority set: A priority level from 1 (urgent) to 4 (low)

What Happens

  1. Load the issue: Reads the current state and description
  2. Assess completeness: Identifies what's missing
  3. Fill gaps: Adds acceptance criteria, technical notes, estimate, and priority as needed
  4. Transition: Moves the issue to Ready when all gates pass
  5. Comment: Documents the refinement with a status comment

When to Use It

After capturing a batch of issues, run /refine to get them development-ready. Also useful when picking up an old backlog item that needs a fresh look before activation.

Related Commands