pair-process-refine-story

Refine user stories through structured analysis phases and update project management tools.

6|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/foomakers/pair --skill pair-process-refine-story
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pair-process-refine-story
Source: https://github.com/foomakers/pair/tree/main/.claude/skills/pair-process-refine-story
Command: npx skills add https://github.com/foomakers/pair --skill pair-process-refine-story

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires /pair-capability-write-issue, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of transforming raw user stories into development-ready specifications, ensuring clarity and completeness before coding begins.

Core Features & Use Cases

  • Structured Refinement: Guides the story through distinct phases: selection, requirements analysis (Given-When-Then), technical analysis, and sprint readiness.
  • Idempotency: Detects partially refined stories and resumes from the first missing section, preventing redundant work.
  • PM Tool Integration: Composes updates for project management tools, ensuring stories are accurately tracked and transitioned to a 'Refined' state.
  • Use Case: A product manager has a backlog of user stories in a 'Todo' state. This Skill can automatically select the highest priority story, guide the team through defining acceptance criteria and technical approach, and update the story in Jira to 'Refined', ready for sprint planning.

Quick Start

Use the pair-process-refine-story skill to refine the next highest priority story in the backlog.

Frequently Asked Questions about pair-process-refine-story

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

FAQPage Schema
How do I refine user stories for sprint readiness?

Refine user stories by guiding them through structured analysis phases including requirements, technical assessment, and sprint readiness to transition them to a 'Refined' state. This ensures clarity and completeness before coding begins.

What is the best way to write acceptance criteria for agile stories?

Writing acceptance criteria is handled during the requirements analysis phase using the Given-When-Then structure. This approach ensures the story meets specific conditions before moving to technical assessment and sprint planning.

Can I resume refining a partially processed user story?

Yes, you can resume refining a partially processed user story. The process detects partially refined stories and resumes from the first missing section, preventing redundant work through idempotency.

Does this workflow update story status in project management tools?

Yes, the workflow composes updates for project management tools, ensuring stories are accurately tracked and transitioned to a 'Refined' state, ready for sprint planning.

Do I need a specific skill to write issues before story refinement?

Yes, you need the pair-capability-write-issue skill to create initial issues. This refinement process depends on having raw user stories already broken down before applying structured analysis.