Refinement
Take one user story from Draft to Ready, grill sync, refine, plan tasks, and read the Assumptions and Open Questions it leaves on the card.
Goal: one Draft story becomes Ready: acceptance criteria, analysis, classification, sizing and tasks. About 30 minutes. Second step of the analysis and refinement workflow; the story can come from Brainstorming.
1. Refine
Phase 0, sync. /pair-capability-grill interviews you one question at a time (goal, edge cases, dependencies, risks). No section is written until you and the AI agree. This is a blocking gate.
Then the skill writes Given-When-Then acceptance criteria, the technical analysis, a classification and a size, and moves the card toward Ready. Detail: Iteration.
With pair-cli: pair-cli run --card 88 --prepare never --until ready refines alone and stops before implementation. With /pair-assistant (optional, Claude Code): ask it to set the prepare gate (how to ask); the run itself is pair-cli.
2. Plan tasks
Adds a task checklist, a dependency graph and an AC coverage table to the card. The card is now Ready (canonical states).
3. Read Assumptions and Open Questions
Two sections on the card record what the interview could not settle:
- Assumptions: a question, the answer the AI chose, and what would overturn it. Skim them; reject any you disagree with.
- Open Questions: unresolved items. Resolve or accept each before delivery.
When the prepare gate lets pair refine alone (autonomy), these sections are your review surface.
What you have
A Ready story. Next: Automated development, or /pair-process-implement by hand (Execution).