refine-story-v3

Refine GitHub issues into implementation-ready specifications with phase-driven templates.

3|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/drdatarulz/TI-Engineering-Standards --skill refine-story-v3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refine-story-v3
Source: https://github.com/drdatarulz/TI-Engineering-Standards/tree/main/skills/archive/refine-story-v3
Command: npx skills add https://github.com/drdatarulz/TI-Engineering-Standards --skill refine-story-v3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refining GitHub issues into precise, implementation-ready specifications reduces ambiguity, speeds up handoffs, and creates a canonical design reference for teams.

Core Features & Use Cases

  • Orchestrator mode: automatic decisions, issue comments, and structured status reports to drive refinement without interactive prompts.
  • Standalone mode: interactive guidance when orchestrator mode is disabled.
  • Generates a complete refined issue template including stub, interface, consumers, DI registration, and related stories.

Quick Start

Provide the STORY_ID or issue number to the refine-story-v3 skill and run it to produce a fully fleshed-out spec ready for implementation.

Frequently Asked Questions about refine-story-v3

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

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

The best way to automate GitHub issue refinement is using an orchestrator tool that converts issues into phase-driven specifications without interactive prompts. It automatically generates structured status reports and implementation-ready templates.

What is orchestrator mode for GitHub issue refinement?

Orchestrator mode for issue refinement automates decisions, posts issue comments, and generates structured status reports to drive specification creation without requiring interactive prompts. It operates automatically once initiated with a STORY_ID.

How do I generate phase-driven specs from GitHub issues?

You generate phase-driven specs by passing a STORY_ID to an issue refinement automation skill. It enforces structured frontmatter-driven discovery and outputs a refined issue template featuring stubs, interfaces, consumers, and DI registration.

Does the issue specification skill support interactive workflows?

Yes, interactive standalone workflows are supported for issue specification. When orchestrator mode is disabled, the skill provides interactive guidance to help flesh out a complete, implementation-ready specification directly from a GitHub issue.

What sections are included in a refined GitHub issue template?

A refined GitHub issue template includes sections for stubs, interfaces, consumers, DI registration, related stories, changes, and tests. It serves as a canonical design reference to reduce ambiguity and speed up team handoffs.