add-story-v3

Convert conversational input into structured GitHub issues with acceptance criteria.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams generate well-structured backlog stories for a project by engaging in a conversational flow, clarifying requirements, and producing GitHub issues that conform to internal story-writing standards.

Core Features & Use Cases

  • Conversational story creation: interactively elicit details and craft stories that fit the project's backlog style.
  • Standards-compliant output: produces GitHub issues with clear summaries, acceptance criteria, and branching/test guidance.
  • Automatic issue creation planning: outlines milestones and dependencies to help project planning.

Quick Start

Describe the backlog items you want, and I will ask clarifying questions and generate ready-to-file GitHub issues.

Frequently Asked Questions about add-story-v3

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

FAQPage Schema
How do I write backlog stories that conform to project standards?

To write backlog stories that conform to project standards, you can use conversational input to interactively elicit details and generate structured stories with clear summaries, acceptance criteria, and branching guidance.

Can I generate GitHub issues from conversational input?

Yes, you can generate GitHub issues from conversational input by describing your backlog items, which triggers clarifying questions and produces ready-to-file issues aligned with your project milestones.

What is the best way to create structured backlog stories for new initiatives?

The best way to create structured backlog stories for new initiatives is loading project context, referencing story-writing standards, and interactively confirming requirements to output ready-to-file descriptions.

Does this approach work with existing project backlogs and GitHub boards?

Yes, this approach works with existing project backlogs and GitHub boards by reading project context, aligning with current milestones, and producing ready-to-file story descriptions with implementation notes.

Why does my project need conversational story creation for GitHub issues?

Your project needs conversational story creation to clarify requirements interactively, ensuring generated GitHub issues conform to internal story-writing standards and include automatic issue creation planning with dependencies.