productboard-release_skill

Overview

This skill helps plan and manage ProductBoard releases and roadmaps by organizing features, tracking progress, and updating statuses. It provides tools to create, list, get, and update features, inspect product structure, and find users to assign owners. Use it to move work through a clear lifecycle from candidate to shipped and archived.

How this skill works

The skill exposes API-style operations to inspect products, features, and users. Use pb_product_hierarchy to understand structure, pb_feature_list and pb_feature_get to review items, pb_feature_create to add work, and pb_feature_update to change status, owners, and dates. Workflows sequence these calls for sprint planning, quarterly planning, and retrospectives.

When to use it

• Planning a sprint: select candidates, assign owners, and set dates.
• Preparing a public release: move completed items to shipped and verify scope.
• Quarterly roadmap planning: review product hierarchy and reprioritize features.
• Release retrospective: list shipped items, capture feedback, and archive work.
• Maintaining backlog hygiene: archive obsolete features and tidy status assignments.

Best practices

• Use consistent statuses and move features through the lifecycle systematically.
• Assign owners early to improve accountability and communication.
• Set realistic start and end dates and update them when plans change.
• Organize work by product, component, and sub-feature to preserve clarity.
• Regularly list and audit feature states to keep the roadmap current.

Example use cases

• Sprint planning: list 'candidate' features, inspect details, mark selected items 'in-progress', assign owners, and set sprint dates.
• Release cut: list 'in-progress' and 'shipped' features to confirm scope, then update remaining candidates or postpone as needed.
• Quarterly roadmap reset: review pb_product_hierarchy, list active features per product, and reprioritize or create new features.
• Retrospective cleanup: list 'shipped' features, capture feedback, and archive completed work to keep the backlog focused.