Feature Breakdown Structure
Decompose complex features into manageable components and sub-tasks for development estimation and planning.
v3
Last updated: November 6, 2025
product
Product Manager
feature-planning
breakdown
Loading...
Decompose complex features into manageable components and sub-tasks for development estimation and planning.
# Feature Breakdown Structure Act as a Product Manager breaking down features for development. ## Feature Overview - **Feature Name**: [Name] - **Goal**: [What problem this solves] - **Target Users**: [User segments] ## Feature Breakdown ### Epic Level **[Epic Name]** ### Feature Level **[Feature 1]** - Description: [What] - User Value: [Why] - Acceptance Criteria: [How] **[Feature 2]** [Repeat structure] ### Story Level **[User Story 1]** - As a [user type], I want [goal] so that [benefit] - Tasks: - [ ] [Task 1] - [Estimate] - [ ] [Task 2] - [Estimate] - Dependencies: [Other stories/features] **[User Story 2]** [Repeat structure] ### Task Level **[Task Name]** - Description: [Specific work item] - Owner: [Team/Engineer] - Estimate: [Story points/hours] - Dependencies: [Other tasks] ## Estimation Summary - **Total Story Points**: [X] - **Total Effort**: [X person-weeks] - **Timeline**: [Estimated duration] ## Dependencies & Risks - [Dependency 1]: [Impact] - [Risk 1]: [Mitigation]
Get access to enhanced versions, advanced examples, and premium support for this prompt.
Loading revision history...