Feature Decomposition Assistant

Pro v1.0.0 1 view

Break down large features into right-sized user stories (1-3 days each) following INVEST criteria with clear dependencies and acceptance criteria.

What You Get

Transform large features into implementable user stories with clear dependencies, acceptance criteria, and implementation strategy. Helps PMs avoid stories that are too large (incomplete sprints) or too small (excessive overhead).

The Problem

Product managers struggle to break down large features into right-sized stories. Stories that are too large lead to incomplete sprints and missed commitments. Stories that are too small create excessive overhead in planning and tracking. Without proper decomposition, teams face unclear dependencies, missing acceptance criteria, and no clear MVP definition.

The Solution

This skill decomposes features into 5-10 independent, right-sized stories (1-3 days each) following INVEST criteria. It identifies major capabilities, ensures stories are independent and testable, suggests implementation order with dependencies, provides starter acceptance criteria, estimates story sizes, categorizes by priority (MUST/SHOULD/NICE TO HAVE), and defines MVP vs. full feature scope.

How It Works

  1. 1 Analyze feature scope to identify major capabilities, user personas, technical components, and integration points
  2. 2 Identify decomposition boundaries: Foundation (infrastructure), Core (MVP), Enhancement (nice-to-have), and Integration stories
  3. 3 Consider investigation stories if critical information is missing (feasibility, performance, compliance)
  4. 4 Write user stories with title, user story format, estimated size (1-3 days), priority, and dependencies
  5. 5 Generate 4-6 acceptance criteria starters for each story using testable outcomes with happy path and error scenarios
  6. 6 Validate each story with INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable)
  7. 7 Create implementation strategy with phases, timeline estimates, parallelization opportunities, MVP definition, and risk mitigation

What You'll Need

  • High-level feature description with enough context to understand capabilities and scope
  • Target user personas (who benefits from this feature)
  • Known technical constraints or dependencies (if any)

Get This Skill

Requires Pro subscription ($9/month)

Have Feedback?

Help us improve this skill by sharing your ideas and suggestions.

Request Improvements

Examples

Enterprise SSO Integration

SSO integration supporting Google, Microsoft, and SAML for enterprise customers with existing basic auth. Demonstrates handling of integration-heavy features with 9 stories including investigation spike, identity linking architecture, and enterprise admin features. Shows security-focused acceptance criteria and multi-provider considerations.

View example

Cross-Platform Offline Support

Offline functionality for mobile and web platforms addressing data loss during connection drops. Demonstrates handling of ambiguous requirements through investigation stories, platform-specific decomposition (iOS vs web), and complex sync/conflict resolution. Shows how to identify technical unknowns and parallel track platform work.

View example

SaaS User Notification System

Multi-channel notification system (email, push, in-app) for a SaaS product with both end users and admin personas. Demonstrates comprehensive decomposition with 11 stories including investigation spike, foundation infrastructure, channel implementations, and enhancement layers. Shows parallelization opportunities and phased MVP approach.

View example
View all examples