Source Code

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
pb_feature_update - Update feature status and details
pb_feature_list - List features by status or product
pb_feature_get - Get detailed feature information
pb_product_list - List products
pb_product_hierarchy - View product structure
pb_user_list - Find users to assign as owners

Release Planning Workflow

1. Review Current State

1. pb_product_hierarchy - Understand workspace structure
2. pb_feature_list with status "candidate" - Review feature candidates
3. pb_feature_list with status "in-progress" - Check ongoing work

2. Prioritize Features

Review candidates and update their status:

pb_feature_update:
  - id: "feature-id"
  - status: "in-progress"  // Move to active development

3. Assign Owners

Find users and assign feature ownership:

1. pb_user_list - Get available team members
2. pb_feature_update:
   - id: "feature-id"
   - ownerEmail: "developer@company.com"

4. Set Timeframes

Add planning dates to features:

pb_feature_update:
  - id: "feature-id"
  - startDate: "2024-01-15"
  - endDate: "2024-02-15"

5. Track Progress

Monitor feature statuses:

pb_feature_list with status "in-progress" - Active development
pb_feature_list with status "shipped" - Completed features

Feature Status Lifecycle

Status	Description
`new`	Just created, not yet evaluated
`candidate`	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

List candidates: pb_feature_list with status "candidate"
Review each feature: pb_feature_get for details
Move selected features to in-progress: pb_feature_update
Assign owners: pb_feature_update with ownerEmail
Set sprint dates: pb_feature_update with startDate/endDate

Release Retrospective

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

Review product hierarchy: pb_product_hierarchy
List all active features by product
Reassess priorities and update statuses
Create new features as needed: pb_feature_create

Organizing Features

By Product

pb_feature_create:
  - name: "Feature name"
  - productId: "product-id"
  - status: "candidate"

By Component

pb_feature_create:
  - name: "Feature name"
  - componentId: "component-id"
  - status: "candidate"

As Sub-feature

pb_feature_create:
  - name: "Sub-feature name"
  - parentFeatureId: "parent-feature-id"

Best Practices

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-release