SkillVaultskills Browse all 500 skills

Product Management · Version 1.0.0 · Reviewed 2026-08-02

Roadmap Trade-off Memo Builder

Make a product decision about option framing and evidence-weighted prioritization with evidence, explicit trade-offs, and a verification plan.

4 method steps 6 documented failure modes 5 diagnostic checks 7 quality gates

Turns competing roadmap options into a decision memo using customer impact, strategy, urgency, evidence, dependency, effort, risk, reversibility, and opportunity cost.

₹149 one-time

Get this skill archive

What this skill helps you do

  • Option framing
  • Evidence-weighted prioritization
  • Opportunity-cost communication

How Roadmap Trade-off Memo Builder works

You provide

Build definition, timings, and cache statistics

It inspects

Layer ordering and secret exposure for option framing

It decides

A evidence-weighted prioritization change that keeps every gate intact

You verify

Per-stage duration and cache hit rate re-measured

What it checks first

Roadmap Trade-off Memo Builder turns competing roadmap options into a decision memo using customer impact, strategy, urgency, evidence, dependency, effort, risk, reversibility, and opportunity cost. Use it when the work involves Option framing, Evidence-weighted prioritization, Opportunity-cost communication.

  1. Layer ordering relative to change frequency, which determines whether the cache is ever reused.
  2. Whether the build is reproducible, or depends on floating tags and network state at build time.
  3. Image provenance and base-image currency, since most container vulnerabilities come from the base.
  4. Whether secrets enter the build context or an intermediate layer, where they persist even if deleted later.
  5. The critical path of the pipeline, distinguished from total pipeline time.

Failure modes it recognizes

  • Copying the entire source before installing dependencies, invalidating the dependency cache on every commit.
  • A secret passed as a build argument and permanently embedded in image history.
  • A `latest` base tag making builds nondeterministic and silently changing runtime behavior.
  • Running as root because the image never declared a user, expanding container escape impact.
  • A cache key that includes a timestamp, so the cache never hits.
  • Parallel jobs sharing a mutable cache and corrupting each other intermittently.

Answers it will reject

  • Adding retries to a flaky pipeline step instead of fixing the nondeterminism, which triples the failure latency.
  • Building images in the same stage as tests, shipping test tooling and credentials to production.
  • Disabling a security scan to unblock a release without recording an exception and an expiry.
  • Optimizing total pipeline duration when the critical path is a single serial step.

Decision rules it applies

  • Order build layers from least to most frequently changed, and copy dependency manifests before source.
  • Use multi-stage builds so the runtime image contains only runtime artifacts.
  • Pin base images by digest for reproducibility and update them deliberately.
  • Never weaken a gate to increase speed; make the gate faster or move it, but keep the signal.

Evidence it asks for

  • Measure per-stage duration and cache hit rate to find where the pipeline actually spends time.
  • Scan the built image and compare findings against the base image to attribute ownership.
  • Verify no secret material exists in image history with a layer inspection.

The method inside

  1. Separate the customer problem from requested solutions
  2. Inventory assumptions and strength of evidence
  3. Compare options using impact, confidence, risk, effort, and reversibility
  4. Define success, guardrails, and the decision after new evidence

Deliverables

  • Option framing evidence map
  • Evidence-weighted prioritization option and risk analysis
  • Opportunity-cost communication decision memo

Evidence requirements

  • Customer research, usage, support, and commercial evidence
  • Strategy, constraints, dependencies, and opportunity cost
  • Experiment design, roadmap options, or requirements artifact

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Build a roadmap trade-off memo comparing compliance work, onboarding improvements, and an analytics feature.

Expected output

Compliance is deadline-driven and non-discretionary. Onboarding has the strongest retention evidence; analytics has strategic value but weak current demand. The memo recommends sequencing, not a single score...

Boundaries and compatibility

Ideal for

  • Option framing: produce a decision or artifact grounded in supplied evidence.
  • Evidence-weighted prioritization: produce a decision or artifact grounded in supplied evidence.
  • Opportunity-cost communication: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Using request volume as a substitute for impact
  • Presenting a prioritization score as objective truth

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.