Decompose a Feature into discrete, end-to-end stories for Jira and Azure DevOps.
npx skills add https://github.com/sean-m-cooper/ai_tools --skill story-splitter
Please help me install this Agent Skill. Skill: story-splitter Source: https://github.com/sean-m-cooper/ai_tools/tree/main/skills/story-splitter Command: npx skills add https://github.com/sean-m-cooper/ai_tools --skill story-splitter
This skill helps product teams decompose a Feature into smaller, independently deliverable stories, enabling precise planning and interactive refinement with the story-writer.
Provide a Feature description or reference, and I will decompose it into individually deliverable stories.
High-intent search queries and answers about installing and using this skill.
To split a Jira feature into deliverable user stories, provide a feature description to decompose it into discrete, end-to-end stories aligned with specific user actions. This story-splitting process enforces CRUD order and creates one-action-per-story units suitable for precise agile planning.
Decomposing full-stack features for Azure DevOps is best handled by breaking the feature down into individual, end-to-end stories aligned with user actions. The resulting feature hierarchy is then created, linked, and tracked directly within Azure DevOps to maintain progression context.
Yes, you can interactively refine individual stories during feature decomposition by pausing for Product Owner review between each generated story. This interactive collaboration ensures each end-to-end story aligns with feasibility and planning requirements before proceeding.
Feature decomposition preserves tracking context by implementing a step-by-step workflow that links the parent feature to its child stories. It enforces CRUD order and coordinates with story-writer tools to maintain the hierarchical relationship and progression state across Jira or Azure DevOps.
Story splitting works for backend-only features as well as UI and full-stack workflows. The feature decomposition process breaks down any feature type into discrete, end-to-end stories aligned with user actions, ensuring individually deliverable units regardless of the technical layer.
A step-by-step story splitter prevents misalignment by enforcing CRUD order and allowing interactive PO review between each generated story. Generating stories individually ensures each end-to-end unit is feasible and properly linked before moving to the next, preserving accurate tracking context.
thomasholknielsenConfigure Azure DevOps work items, pipelines, and branch policies.
Nir-BhayGuide backlog refinement sessions using the DEEP framework and Planning Poker.
dariopalminioCoordinate story refinement across DOING and READY states in a central backlog.
AlteriomBreak down complex tasks into interdependent subtasks with verification criteria.
