issue-refinement

Transform raw GitHub issues into structured user stories validated against INVEST criteria.

8|2|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/SebastienDegodez/skraft-plugin --skill issue-refinement-sebastiendegodez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-refinement
Source: https://github.com/SebastienDegodez/skraft-plugin/tree/main/plugins/skills/issue-refinement
Command: npx skills add https://github.com/SebastienDegodez/skraft-plugin --skill issue-refinement-sebastiendegodez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers and product managers transform raw issues into well-structured user stories, ensuring clear requirements and acceptance criteria.

Core Features & Use Cases

  • User Story Formatting: Offers templates and guidelines for writing effective user stories.
  • INVEST Criteria: Assists with validating user stories against INVEST criteria for clarity and completeness.
  • Story Splitting: Provides patterns to break down large stories into smaller, manageable pieces.
  • Acceptance Criteria Patterns: Offers various formats for writing testable acceptance criteria.
  • Definition of Ready: Lists the checklist for marking a user story ready for the next phase of development.

Quick Start

Run the issue-refinement skill with the issue text provided, and it will generate a structured user story for you.

Frequently Asked Questions about issue-refinement

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

FAQPage Schema
How do I refine raw GitHub issues into actionable user stories?

To refine raw GitHub issues into actionable user stories, provide the issue text to automatically generate structured user stories, validate them against INVEST criteria, and apply splitting patterns to break down large tasks.

What are the INVEST criteria for validating user stories?

INVEST criteria for validating user stories ensure your issues are Independent, Negotiable, Valuable, Estimable, Small, and Testable. This validation checks clarity and completeness before development begins.

What is the best way to split large user stories into smaller pieces?

The best way to split large user stories is by applying established story splitting patterns, which break down complex issues into smaller, manageable pieces that satisfy INVEST criteria.

How do I write testable acceptance criteria for my user stories?

To write testable acceptance criteria for user stories, use provided acceptance criteria patterns that format requirements clearly, ensuring the definition of ready is met before development starts.

Do I need prior knowledge to write user stories with issue refinement?

Yes, issue refinement requires basic knowledge of user story writing and acceptance criteria to effectively transform raw issues into well-structured requirements validated by INVEST criteria.

What should be included in a definition of ready for user stories?

A definition of ready for user stories should include a completed user story format, validated INVEST criteria, testable acceptance criteria patterns, and successful story splitting if needed.