refine-story-v4

Convert GitHub issues into implementation-ready specifications with acceptance criteria.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/drdatarulz/TheL10inator --skill refine-story-v4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refine-story-v4
Source: https://github.com/drdatarulz/TheL10inator/tree/main/.claude/skills/refine-story-v4
Command: npx skills add https://github.com/drdatarulz/TheL10inator --skill refine-story-v4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates turning a GitHub issue into a complete, implementation-ready specification, including context extraction and phased refinement.

Core Features & Use Cases

  • Orchestrator mode: auto-decisions, issue comments, and structured status reports when enabled.
  • Standalone mode: interactive refinement when orchestrator mode is not active.
  • Generates a complete specification document with sections like Summary, Technical Approach, Acceptance Criteria, Files Affected, and Tests.

Quick Start

Provide a refined specification for the given STORY_ID using either orchestrator or interactive mode.

Frequently Asked Questions about refine-story-v4

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

FAQPage Schema
How do I turn GitHub issues into implementation-ready specifications?

To turn GitHub issues into implementation-ready specifications, this Skill automates context extraction and phased refinement to generate a structured spec document with technical approach, acceptance criteria, and affected files.

What is orchestrator mode for issue refinement workflows?

Orchestrator mode for issue refinement provides auto-decisions, issue comments, and structured status reports without manual intervention, streamlining the transition from raw GitHub issue to ready-to-implement specification.

Can I interactively refine a GitHub feature specification instead of using orchestrator mode?

Yes, you can interactively refine a GitHub feature specification using standalone mode, which activates when orchestrator mode is not active and guides you through a phased refinement workflow.

What sections are included in a specification generated from a GitHub issue?

A specification generated from a GitHub issue includes Summary, Technical Approach, Acceptance Criteria, Files Affected, and Tests sections, enforcing a standardized template for product development workflows.

Does this specification workflow work for bugs and enhancements or only new features?

This specification workflow applies to features, enhancements, and bugs alike, extracting context and generating acceptance criteria for any GitHub issue requiring an implementation-ready specification.

Do I need additional dependencies to extract context and refine GitHub issues?

No additional dependencies are required to extract context and refine GitHub issues; the Skill operates independently to produce a complete specification document from the provided STORY_ID.