Use when input contains epics, themes, compound user stories, or large feature requests that need to be broken down into atomic, testable capabilities before writing a capability.md.
Decomposes epics and large user stories into atomic capabilities using proven story-splitting patterns. Prevents "mega-capabilities" that are too vague to implement and ensures each output capability is independently testable and valuable.
Story contains conjunctions implying multiple features: "and", "also", "additionally"
Story describes multiple actions, actors, or workflows
A Trello card or intent describes a broad feature area
What This Skill Does
Analyzes incoming feature requests, epics, or compound stories and applies one or more splitting patterns to produce multiple atomic capability entries. Each decomposed capability maps to a single capability.md section or a separate spec.
Story Splitting Patterns
Pattern 1: Workflow Steps
相关技能
When: Story describes a multi-step process
Split by: Each step becomes a capability
Example — "As a user, I want to purchase a product":
Add product to cart
Review cart contents
Enter shipping information
Select payment method
Confirm and place order
View order confirmation
Pattern 2: CRUD Operations
When: Story implies Create, Read, Update, Delete
Split by: Each operation becomes a capability
Example — "As an admin, I want to manage products":
Create new product
View product list
View product details
Update product information
Delete product
Search products
Pattern 3: Business Rules / Variations
When: Story has multiple business rules or conditions
Split by: Each rule variation becomes a capability
Example — "As a customer, I want to apply discounts":
Apply percentage discount code
Apply fixed-amount discount code
Apply BOGO discount
Apply free shipping discount
Apply tiered discount
Stack multiple discounts
Pattern 4: Actor / Role Variations
When: Different actors need different capabilities
Split by: One capability per actor type
Example — "Users want to view reports":
Sales Rep views own sales report
Sales Manager views team report
Admin views company-wide report
Finance exports data for accounting
Pattern 5: Data Variations / Input Types
When: Story involves different data types or sources
Split by: One capability per data variation
Example — "As a user, I want to import contacts":
Import from CSV
Import from Excel
Import from Google Contacts
Import from Outlook
Import from vCard
Pattern 6: Platform / Channel Variations
When: Story mentions multiple platforms (web, mobile, Slack, Teams)
Split by: One capability per platform where behavior differs
Example — "Users want to access the dashboard on mobile and web":
Web desktop layout
Mobile responsive layout
Offline access on mobile
Cross-platform data sync
Pattern 7: Performance / Scale Variations
When: Story has different performance requirements at different scales
Split by: One capability per performance tier
Example — "System should handle reports for small and large datasets":
< 1,000 records (synchronous)
1,000–100K records (async with progress)
100K records (background job with notification)
Pattern 8: Happy Path vs. Error Handling
When: Story implies error or exception scenarios
Split by: Happy path + each error handling capability
Example — "As a user, I want to pay for my order":
Process successful payment
Handle payment decline
Handle payment timeout
Handle fraud detection trigger
Retry failed payment
Refund payment
Decision Tree
Apply patterns in this order. Multiple patterns can apply to the same epic:
Does it describe a multi-step process? → Pattern 1: Workflow Steps
Does it mention CRUD operations? → Pattern 2: CRUD Operations
Does it have multiple business rules/conditions? → Pattern 3: Business Rules
Does it mention multiple user roles/actors? → Pattern 4: Actor Variations
Does it involve different data types/sources? → Pattern 5: Data Variations
Does it mention multiple platforms? → Pattern 6: Platform Variations
Does it have different performance/scale requirements? → Pattern 7: Performance Variations
Does it imply error/exception scenarios? → Pattern 8: Error Handling
None of the above → Story may already be atomic; output as-is