Slice stories and epics into vertical slices using codebase analysis and INVEST criteria.
npx skills add https://github.com/a53ali/ai-dev --skill story-slicing-a53ali
Please help me install this Agent Skill. Skill: story-slicing Source: https://github.com/a53ali/ai-dev/tree/main/skills/manager/story-slicing Command: npx skills add https://github.com/a53ali/ai-dev --skill story-slicing-a53ali
Large stories and epics often lead to missed sprint commitments, deferred feedback, and integration risks. This skill helps slice stories and epics into independently deliverable vertical slices, reducing complexity and risk.
Use the story-slicing skill to analyze and slice the 'User can log in with email and password' story into independently deliverable vertical slices.
High-intent search queries and answers about installing and using this skill.
Vertical story slicing splits epics into independently deliverable vertical slices using codebase analysis, Richard Lawrence's nine splitting patterns, and INVEST criteria to deliver usable increments after every sprint.
Break down Jira epics without a Premium license by using Jira Intelligence features for work breakdown, story enhancement, comment summarization, edge case generation, dependency detection, NL-to-JQL, and story point estimation.
Codebase analysis grounds story point estimation in real code complexity, ensuring vertical slices are accurately scoped to prevent missed sprint commitments and reduce integration risks.
Yes, you need Python libraries for codebase analysis and Jira API integration to execute story splitting, work breakdown, and dependency detection alongside Jira Intelligence features.
Yes, you can apply Richard Lawrence's nine splitting patterns with INVEST criteria to slice stories and epics into independently deliverable vertical slices that ensure usable increments after every sprint.
Avoid vertical slicing when your codebase lacks sufficient structure for complexity analysis, or when your Jira epics do not require independently deliverable increments to mitigate integration risks.
tomsoulage-dedalusAnalyze Jira tickets by fetching documents, investigating code, and generating fix hypotheses.
haidonglethqbAnalyze Jira stories, PRDs, and feature specs into testable requirements with acceptance criteria.
openshift-hyperfleetEstimate Jira ticket story points from ticket details and historical velocity.
MMXCGuide product managers through splitting epics into user stories using nine sequential patterns.
