Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Manage ProductBoard releases and roadmap planning
Manage ProductBoard releases and roadmap planning
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Plan and manage product releases by organizing features, tracking progress, and updating statuses in ProductBoard.
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
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
Review candidates and update their status: pb_feature_update: - id: "feature-id" - status: "in-progress" // Move to active development
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"
Add planning dates to features: pb_feature_update: - id: "feature-id" - startDate: "2024-01-15" - endDate: "2024-02-15"
Monitor feature statuses: pb_feature_list with status "in-progress" - Active development pb_feature_list with status "shipped" - Completed features
StatusDescriptionnewJust created, not yet evaluatedcandidateBeing considered for developmentin-progressActively being developedshippedReleased to customerspostponedDeferred to future planningarchivedNo longer relevant
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
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"
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
pb_feature_create: - name: "Feature name" - productId: "product-id" - status: "candidate"
pb_feature_create: - name: "Feature name" - componentId: "component-id" - status: "candidate"
pb_feature_create: - name: "Sub-feature name" - parentFeatureId: "parent-feature-id"
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
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.