feature-planning
Break down the approved PRD, User Stories, IA, and User Flows into implementable product features with priorities, dependencies, and release planning.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- feature-planning
- author
- AI Business OS
- license
- MIT
- version
- 1.0.0
- category
- workflow
- priority
- required
- description
- Break down the approved PRD, User Stories, IA, and User Flows into implementable product features with priorities, dependencies, and release planning.
03 SKILL.md 正文
Feature Planning
Purpose
This skill transforms product requirements into a structured feature roadmap.
The objective is to define what features will be built, their priorities, dependencies, and release strategy before implementation begins.
A feature should represent a complete unit of business value.
When to Use
Execute after:
- planning/prd
- planning/user-story
- planning/ia
- planning/user-flow
Execute before:
- planning/task-planning
- design
- development
Objectives
Create a complete feature plan that:
- groups related functionality
- defines feature boundaries
- establishes priorities
- identifies dependencies
- supports implementation planning
Inputs
Expected inputs:
- Product Requirements Document
- User Stories
- Information Architecture
- User Flow
- Business Goals
Feature Definition
Each feature should include:
- Feature ID
- Feature Name
- Description
- Business Value
- Owner
- Priority
- Status
Example:
Feature: User Authentication
Description:
Allow users to register, log in, and manage sessions securely.
Feature Categories
Organize features such as:
- Authentication
- User Management
- Dashboard
- Product Catalog
- Search
- Shopping Cart
- Checkout
- Payment
- Notifications
- Administration
Priority
Assign one priority:
- Must Have
- Should Have
- Could Have
- Won't Have
Provide a reason for each priority.
Dependencies
Document:
- Required APIs
- Database tables
- External services
- Shared components
- Related features
MVP Planning
Separate features into:
MVP
Required for initial release.
Phase 2
Future improvements.
Backlog
Ideas for future consideration.
Release Planning
Assign each feature to a release.
Example:
Release 1.0
- Login
- Registration
- Dashboard
Release 1.1
- Notifications
- Analytics
Feature Workflow
Review PRD
↓
Review User Stories
↓
Review IA
↓
Review User Flow
↓
Identify Features
↓
Group Features
↓
Assign Priorities
↓
Identify Dependencies
↓
Create MVP
↓
Plan Releases
↓
Approve
Outputs
Generate:
- Feature List
- Feature Roadmap
- MVP Definition
- Priority Matrix
- Dependency Map
- Release Plan
Rules
- One feature should deliver a complete business capability.
- Avoid duplicate features.
- Keep feature boundaries clear.
- Prioritize business value over technical complexity.
- Features should be independently testable whenever possible.
Success Criteria
This skill succeeds when:
- all requirements are mapped to features
- MVP is clearly defined
- priorities are assigned
- dependencies are documented
- release planning is complete
Next Skills
Invoke:
task-planning
↓
milestone
Related Skills
- prd
- user-story
- ia
- user-flow
- task-planning
- ai-business-os-core
Version History
| Version | Date | Description |
|---|---|---|
| 1.0.0 | 2026-07-10 | Initial release |
04 同仓库更多 Skills
rollback
Plan, validate, and execute safe rollback procedures to restore a stable system state when deployments introduce critical issues.
release-note
Create clear, concise, and stakeholder-friendly release notes that communicate new features, improvements, fixes, breaking changes, and operational guidance for each release.
monitoring
Continuously observe application health, performance, reliability, and business metrics after deployment to detect issues early and support operational excellence.
maintenance
Maintain, improve, and support production systems after release through continuous monitoring, issue resolution, updates, and operational excellence.
deployment
Plan, validate, and execute application deployments safely and consistently across environments while minimizing downtime and deployment risk.
changelog
Maintain a structured, accurate, and versioned changelog that records all notable changes made to the project across releases.