refine-story-v2

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates turning a GitHub issue into an implementation-ready specification, enabling consistent, repeatable refinement workflows.

Core Features & Use Cases

  • Orchestrator mode automates decisions, appends status reports, and comments on the issue.
  • Standalone mode provides interactive guidance to refine the spec with user input.
  • Outputs a concrete plan, including stub, interface, consumers, DI wiring, and acceptance criteria.

Quick Start

Provide a STORY-ID (e.g., AZ-014) to generate a complete, implementation-ready specification draft.

Frequently Asked Questions about refine-story-v2

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

FAQPage Schema
How do I turn a GitHub issue into an implementation-ready specification?

To turn a GitHub issue into a specification, provide a STORY-ID to automate parsing context into a ready-to-apply plan with stubs, interfaces, DI wiring, and acceptance criteria.

Can I automate issue refinement and automatically comment on the GitHub issue?

Yes, you can automate issue refinement using orchestrator mode, which automates decisions, appends status reports, and posts comments directly on the GitHub issue.

What is the best way to generate a specification plan with stub files and DI wiring from an issue?

Generating a specification plan with stubs and DI wiring requires parsing the issue context to identify interfaces and consumers, then outputting a ready-to-apply implementation plan.

Does this issue specification orchestrator support interactive refinement workflows?

Yes, the issue specification orchestrator supports standalone interactive mode, providing guided user input to refine the spec alongside orchestrator-enabled workflows.

What do I need to provide to start generating an implementation-ready specification draft?

You need to provide a STORY-ID, such as AZ-014, to generate a complete, implementation-ready specification draft from your existing GitHub issue context.

When should I use standalone mode instead of orchestrator mode for issue refinement?

Use standalone mode for interactive guided refinement with user input, whereas orchestrator mode automates decisions and appends status reports without manual intervention.