ProductBoard Release Planning Skill
Plan and manage product releases by organizing features, tracking progress, and updating statuses in ProductBoard.
Available Tools
- -
pb_feature_create - Create new features for releases - INLINECODE1 - Update feature status and details
- INLINECODE2 - List features by status or product
- INLINECODE3 - Get detailed feature information
- INLINECODE4 - List products
- INLINECODE5 - View product structure
- INLINECODE6 - Find users to assign as owners
Release Planning Workflow
1. Review Current State
CODEBLOCK0
2. Prioritize Features
Review candidates and update their status:
CODEBLOCK1
3. Assign Owners
Find users and assign feature ownership:
CODEBLOCK2
4. Set Timeframes
Add planning dates to features:
CODEBLOCK3
5. Track Progress
Monitor feature statuses:
CODEBLOCK4
Feature Status Lifecycle
| Status | Description |
|---|
| INLINECODE7 | Just created, not yet evaluated |
| INLINECODE8 |
Being considered for development |
|
in-progress | Actively being developed |
|
shipped | Released to customers |
|
postponed | Deferred to future planning |
|
archived | No longer relevant |
Planning Scenarios
Sprint Planning
- 1. List candidates:
pb_feature_list with status "candidate" - Review each feature:
pb_feature_get for details - Move selected features to in-progress: INLINECODE15
- Assign owners:
pb_feature_update with ownerEmail - Set sprint dates:
pb_feature_update with startDate/endDate
Release Retrospective
- 1. List shipped features:
pb_feature_list with status "shipped" - Review feedback on features: Use feedback skill tools
- Archive completed work:
pb_feature_update with status "archived"
Quarterly Planning
- 1. Review product hierarchy: INLINECODE20
- List all active features by product
- Reassess priorities and update statuses
- Create new features as needed: INLINECODE21
Organizing Features
By Product
CODEBLOCK5
By Component
CODEBLOCK6
As Sub-feature
CODEBLOCK7
Best Practices
- 1. Use consistent statuses: Move features through the lifecycle systematically
- Assign owners early: Clear ownership improves accountability
- Set realistic timeframes: Update dates as plans change
- Organize hierarchically: Use products, components, and sub-features
- Archive completed work: Keep the backlog clean by archiving shipped features
- Review regularly: Use listing tools to audit feature states
ProductBoard 发布规划技能
通过组织功能、跟踪进度和在 ProductBoard 中更新状态来规划和管理产品发布。
可用工具
- - pbfeaturecreate - 为发布创建新功能
- pbfeatureupdate - 更新功能状态和详情
- pbfeaturelist - 按状态或产品列出功能
- pbfeatureget - 获取详细功能信息
- pbproductlist - 列出产品
- pbproducthierarchy - 查看产品结构
- pbuserlist - 查找用户以分配为负责人
发布规划工作流程
1. 审查当前状态
- 1. pbproducthierarchy - 了解工作空间结构
- pbfeaturelist 状态为candidate - 审查候选功能
- pbfeaturelist 状态为in-progress - 检查进行中的工作
2. 确定功能优先级
审查候选功能并更新其状态：
pbfeatureupdate:
- id: 功能ID
- status: in-progress // 移至活跃开发
3. 分配负责人
查找用户并分配功能所有权：
- 1. pbuserlist - 获取可用团队成员
- pbfeatureupdate:
- id: 功能ID
- ownerEmail: developer@company.com
4. 设定时间框架
为功能添加规划日期：
pbfeatureupdate:
- id: 功能ID
- startDate: 2024-01-15
- endDate: 2024-02-15
5. 跟踪进度
监控功能状态：
pbfeaturelist 状态为in-progress - 活跃开发中
pbfeaturelist 状态为shipped - 已完成功能
功能状态生命周期
正在考虑开发 |
| in-progress | 正在积极开发中 |
| shipped | 已发布给客户 |
| postponed | 推迟到未来规划 |
| archived | 不再相关 |
规划场景
冲刺规划
- 1. 列出候选功能：pbfeaturelist 状态为candidate
- 审查每个功能：pbfeatureget 获取详情
- 将选中的功能移至进行中：pbfeatureupdate
- 分配负责人：pbfeatureupdate 附带 ownerEmail
- 设定冲刺日期：pbfeatureupdate 附带 startDate/endDate
发布回顾
- 1. 列出已发布功能：pbfeaturelist 状态为shipped
- 审查功能反馈：使用反馈技能工具
- 归档已完成工作：pbfeatureupdate 状态为archived
季度规划
- 1. 审查产品层级：pbproducthierarchy
- 按产品列出所有活跃功能
- 重新评估优先级并更新状态
- 根据需要创建新功能：pbfeaturecreate
组织功能
按产品
pbfeaturecreate:
- name: 功能名称
- productId: 产品ID
- status: candidate
按组件
pbfeaturecreate:
- name: 功能名称
- componentId: 组件ID
- status: candidate
作为子功能
pbfeaturecreate:
- name: 子功能名称
- parentFeatureId: 父功能ID
最佳实践
- 1. 使用一致的状态：系统性地推动功能通过生命周期
- 尽早分配负责人：明确的所有权提高责任感
- 设定现实的时间框架：随计划变更更新日期
- 按层级组织：使用产品、组件和子功能
- 归档已完成工作：通过归档已发布功能保持待办事项清单整洁
- 定期审查：使用列表工具审计功能状态
