add-story-v4

Generates TI-compliant user stories from existing project backlog items.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of TI-compliant user stories from an existing project backlog by transforming plain backlog items into detailed, review-ready stories that align with TI standards.

Core Features & Use Cases

  • Converts backlog items into TI-compliant stories with well-defined acceptance criteria, milestones, dependencies, and branching guidance.
  • Integrates current project board context to ensure new stories fit into ongoing sprints or milestones.
  • Provides ready-to-create GitHub issues that can be reviewed and refined before publication.

Quick Start

Describe the backlog goals and I will generate TI-compliant story drafts ready for review.

Frequently Asked Questions about add-story-v4

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

FAQPage Schema
How do I convert backlog items into TI-compliant user stories for GitHub?

Converting backlog items into TI-compliant user stories is automated by analyzing your existing project board and relevant standards to generate draft issues with acceptance criteria, milestones, and branch naming guidance.

What is the best way to ensure new GitHub issues align with current project milestones?

Ensuring new GitHub issues align with milestones involves analyzing the current project board context to map dependencies and workflow, producing ready-to-create stories that fit into ongoing sprints.

Can I generate acceptance criteria and branch naming guidance from existing project backlog items?

Generating acceptance criteria and branch naming guidance from backlog items is supported by transforming open tasks into detailed, review-ready draft issue content that aligns with TI standards.

Does this backlog-to-story automation work with existing GitHub project boards?

Backlog-to-story automation works directly with existing GitHub project boards, reading open backlog items and milestones to output compliant stories without requiring additional dependencies.

What is included in the draft issue content when transforming backlog items into stories?

Draft issue content includes a summary, acceptance criteria, milestone mapping, dependencies, and branch naming guidance, all ready for review before final creation on GitHub.

Do I need any specific dependencies to generate TI-compliant stories from my backlog?

No specific dependencies are required to generate TI-compliant stories; the Skill operates independently by analyzing your backlog goals and project board context to produce draft issues.