# 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 in `product-strategy/references/product-strategy.md`.
- **Kano:** `product-strategy/references/product-strategy.md` — single canonical location.
- **OST:** Strategic in `product-strategy`, tactical in `product-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
1. Now/Next/Later over timeline as default
2. Evidence/assumptions/commitments/options distinction in every artifact
3. Portfolio + individual product with same artifacts
4. Continue/pause/kill/revisit criteria mandatory
5. No framework duplication — routing only