story-workflow

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.

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.

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.

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.

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.

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.