Skip to content
Adaptive Skills Docs
Esc
↑↓navigate↵open⌘Jpreview
On this page

Select Product Management modules

Choose the smallest sufficient product-management module and companion skill path.

Start with the decision, not with a framework name. Ask what must become clearer, what evidence exists, and what decision remains human-owned.

Initial modules

Module Activate when Minimum useful result
problem-framing A request names a solution but not a problem or outcome Bounded problem frame with users, context, outcome, evidence gaps, and non-goals
discovery-and-evidence Evidence is mixed, narrow, stale, or confused with interpretation Evidence ledger separating observations, inferences, assumptions, and unknowns
prioritization-and-method-selection Several initiatives compete and the method is unclear One justified primary method, rejected alternatives, assumptions, sensitivity, and human decisions
metrics-and-outcomes A team needs to connect activity to value or define guardrails Outcome hypothesis, signal definitions, measurement window, guardrails, and verification

Planned modules

These are reserved as modules, not new skills, until usage proves a separate routing and verification boundary:

  • stakeholder-alignment for conflicting interests and decision communication;
  • strategy-and-opportunity for strategic choices and opportunity structure;
  • roadmap-and-sequencing for dependencies, confidence, and sequence narratives;
  • learning-review for post-launch learning and decision renewal.

Companion skills

Use existing contracts instead of copying them into Product Management:

  • feature-value-governance for whether a feature deserves investment;
  • opportunity-tree-alignment for outcome-to-opportunity-to-lever mapping;
  • revenue-lever-mapping for the mechanism behind a business value claim;
  • feature-complexity-audit for permanent cost and complexity;
  • feature-planning after scope and product intent are bounded;
  • observability-review for instrumentation and measurement review;
  • triad-check when product, design, and engineering must review together.

If no module has sufficient inputs, return the gap and ask for the smallest missing context. Do not run every module by default.

Was this page helpful?