story-workflow

Automates backlog workflow planning and Fibonacci story estimation for agile teams.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/AINative-Studio/telemetry-agent --skill story-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-workflow
Source: https://github.com/AINative-Studio/telemetry-agent/tree/main/.ainative/skills/story-workflow
Command: npx skills add https://github.com/AINative-Studio/telemetry-agent --skill story-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Story management and estimation can be error-prone and slow when backlog items are vague or misaligned with development work. This Skill provides a repeatable workflow to turn backlog items into defined stories, estimate with Fibonacci points, and coordinate with Shortcut/issue tracking, ensuring consistent branch naming and acceptance criteria.

Core Features & Use Cases

  • Backlog-to-story workflow: starting work on the top unstarted story with clear acceptance criteria.
  • Fibonacci estimation: guiding points like 0/1/2/3/5/8 and splitting large stories.
  • Branch naming and work types: feature/bug/chore branches with type- and id-based naming, aligning with PR flow.
  • TDD workflow integration: red/green/refactor commits and end-to-end reviews.
  • Shortcut/issue tracking integration: linking stories to Shortcut items and tracking state transitions.

Quick Start

Begin by selecting the top unstarted backlog item, write acceptance criteria, and create a corresponding feature/bug/chore story with a concise branch name.

Frequently Asked Questions about story-workflow

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

FAQPage Schema
How do I estimate backlog stories using Fibonacci points?

Fibonacci estimation for backlog stories assigns point values of 0, 1, 2, 3, 5, or 8 to quantify effort. Stories exceeding 8 points should be split into smaller items to ensure manageable workloads and accurate tracking.

What's the best way to start work on an unstarted backlog item?

Starting work on an unstarted backlog item involves selecting the top story, writing clear acceptance criteria, and creating a corresponding feature, bug, or chore story. This process ensures alignment before development begins.

How do I create branch naming conventions for feature, bug, and chore stories?

Branch naming conventions use type- and id-based formats for feature, bug, or chore branches. This aligns branches with their corresponding stories and integrates smoothly with the pull request lifecycle.

Can I link Shortcut issue tracking with my story workflow?

Shortcut issue tracking integrates with the story workflow by linking backlog stories to Shortcut items. This allows teams to track state transitions and coordinate development work directly within the issue tracker.

Does TDD workflow guidance include red, green, and refactor steps?

TDD workflow guidance includes red, green, and refactor commit steps. It integrates these testing phases with end-to-end reviews to ensure code quality throughout the story development lifecycle.

When should I split large stories during agile estimation?

Split large stories during agile estimation when their Fibonacci point value exceeds 8. Breaking down these items ensures stories remain focused, actionable, and easier to track through the delivery pipeline.