Introduce the product-roadmapping-and-portfolio skill for outcome-based sequencing and strategic-bet management. Covers Now/Next/Later views, continue/pause/kill/revisit criteria, capacity allocation, dependency and confidence mapping, scenario planning, stakeholder narratives, and roadmap review cadences. Routes tactical prioritization (RICE, MoSCoW, Kano, OST) to their canonical owners in product-methodology and product-strategy. Includes: - SKILL.md with core methodology, loading guide, and routing table - README.md with human-facing overview and trigger guidance - 5 reference files (outcome roadmapping, strategic bets, dependency and confidence view, scenario comparison, roadmap review cadence) - 1 discovery brief reconciling duplicated framework references - 3 fillable templates (outcome roadmap, bet record, review record) - evals/evals.json with 5 schema-valid cases covering competing bets, dependency invalidation, low-confidence opportunity, capacity shortfall, and stop-bet-with-evidence Closes #189 Co-authored-by: username <username> Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
1.6 KiB
Discovery Brief — product-roadmapping-and-portfolio
Reconciles duplicated prioritization-framework references. Phase-2 discovery of issue #189, Milestone 4.
Where RICE, Kano, OST, and MoSCoW Live
- RICE: Canonical owner
product-methodology/references/rice-framework.md. Strategic summary inproduct-strategy/references/product-strategy.md. - Kano:
product-strategy/references/product-strategy.md— single canonical location. - OST: Strategic in
product-strategy, tactical inproduct-methodology. - MoSCoW:
product-methodology/references/moscow-prioritization.md— single canonical owner.
Ownership Boundary
This skill owns: outcome roadmaps, portfolio-level choices, bet management, scenario planning, review cadence, evidence-to-roadmap connection.
Routes to (does not own): RICE/MoSCoW/OST to product-methodology; Kano/OST-strategic to product-strategy; capital allocation to strategy-frameworks; delivery flow to kanban-guru; evidence to product-analytics-and-measurement (prose); implementation to implementation-planning (prose); experimentation/adoption/lifecycle to their respective skills (prose).
Non-goals
Does NOT turn roadmaps into project schedules. Does NOT re-explain RICE/Kano/OST/MoSCoW. Does NOT replace capital-allocation or delivery-flow management.
Design Decisions
- Now/Next/Later over timeline as default
- Evidence/assumptions/commitments/options distinction in every artifact
- Portfolio + individual product with same artifacts
- Continue/pause/kill/revisit criteria mandatory
- No framework duplication — routing only