story-workflow

Manage software development backlog workflows with story classification and Fibonacci estimation.

2|1|Updated May 27, 2025

Search Tags:#workflow #tdd #agile #story points #backlog management #shortcut

Ready to run

npx skills add https://github.com/PAIPalooza/chicommerce --skill story-workflow-paipalooza

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: story-workflow
Source: https://github.com/PAIPalooza/chicommerce/tree/main/.ainative/skills/story-workflow
Command: npx skills add https://github.com/PAIPalooza/chicommerce --skill story-workflow-paipalooza

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of managing software development stories, from initial creation and estimation to integration with issue tracking systems like Shortcut, ensuring a consistent and efficient workflow.

Core Features & Use Cases

Story Classification: Define and classify stories as Feature, Bug, or Chore.
Estimation: Utilize Fibonacci-style story points (0, 1, 2, 3, 5, 8) with clear guidelines for when to split stories.
Workflow Integration: Follows a defined process for PRs, CI, code review, and delivery, integrating with issue tracking for status updates.
Branching Strategy: Enforces a consistent branch naming convention ({type}/{shortcut-id}-{slug}).
TDD & Commits: Guides developers through a Test-Driven Development workflow with specific commit message conventions.

Quick Start

Use the story-workflow skill to create a new feature story for ticket XYZ-123 with the title "Implement user authentication".

Frequently Asked Questions about story-workflow

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

FAQPage Schema

How do I manage backlog stories and estimate story points using Fibonacci numbers?▼

Backlog story management involves classifying stories as Features, Bugs, or Chores, then estimating them using Fibonacci-style points (0, 1, 2, 3, 5, 8). This workflow includes guidelines for splitting stories when estimates exceed capacity, ensuring consistent task breakdown and progress tracking for development teams.

How do I integrate TDD workflow with branching strategies and commit messages?▼

A TDD workflow integrates with branching by enforcing a specific branch naming convention (`{type}/{shortcut-id}-{slug}`) and guiding developers through defined commit message conventions. This ensures consistent code review, CI processes, and delivery tracking alongside test-driven development practices.

How do I update story statuses in Shortcut issue tracking?▼

Story statuses in Shortcut issue tracking are updated by following a defined workflow process for PRs, CI, code review, and delivery. This integration automatically syncs status updates back to the issue tracking system as stories progress through the development lifecycle.

When should I split stories during agile estimation?▼

Stories should be split during agile estimation when their Fibonacci-style story point values become too large to fit within a sprint cycle. The workflow provides clear guidelines for breaking down tasks that exceed the maximum manageable point threshold to maintain efficient progress tracking.

Can I use this story workflow without an issue tracking system?▼

While story classification and Fibonacci estimation can function independently, the workflow is designed to integrate with issue tracking systems like Shortcut for automated status updates. Without an issue tracker, PR tracking, CI processes, and delivery status synchronization would require manual management.

What is the correct branch naming convention for feature stories?▼

The correct branch naming convention for feature stories follows the format `{type}/{shortcut-id}-{slug}`. This consistent naming strategy enforces organized version control and links branches directly to their corresponding issue tracking tickets throughout the development workflow.