SkillVaultskills Browse all 500 skills

Customer Success · Version 1.0.0 · Reviewed 2026-08-02

QBR Outcome Narrative Builder

Improve outcome evidence selection and executive narrative design with evidence, explicit trade-offs, and a verification plan.

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

Builds a customer-specific quarterly business review from adoption, outcomes, unresolved risks, executive priorities, and mutually agreed next-quarter actions.

₹149 one-time

Get this skill archive

What this skill helps you do

  • Outcome evidence selection
  • Executive narrative design
  • Next-quarter action planning

How QBR Outcome Narrative Builder works

You provide

Build definition, timings, and cache statistics

It inspects

Layer ordering and secret exposure for outcome evidence selection

It decides

A executive narrative design change that keeps every gate intact

You verify

Per-stage duration and cache hit rate re-measured

What it checks first

QBR Outcome Narrative Builder builds a customer-specific quarterly business review from adoption, outcomes, unresolved risks, executive priorities, and mutually agreed next-quarter actions. Use it when the work involves Outcome evidence selection, Executive narrative design, Next-quarter action planning.

  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. Reconstruct the customer journey and promised outcomes
  2. Separate activity volume from outcome and risk signals
  3. Identify the blocked dependency and accountable owner
  4. Create a jointly verifiable recovery or expansion plan

Deliverables

  • Outcome evidence selection account brief
  • Executive narrative design risk and dependency map
  • Next-quarter action planning action plan

Evidence requirements

  • Success plan, adoption data, support history, and meeting notes
  • Renewal date, stakeholders, expected outcomes, and risks
  • Verified customer commitments and unresolved dependencies

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 QBR narrative from this usage report, success plan, and support history for our executive sponsor.

Expected output

Adoption grew 18%, but the outcome story is concentrated in one team. The QBR leads with cycle-time reduction, addresses stalled expansion honestly, and proposes three jointly owned next-quarter actions...

Boundaries and compatibility

Ideal for

  • Outcome evidence selection: produce a decision or artifact grounded in supplied evidence.
  • Executive narrative design: produce a decision or artifact grounded in supplied evidence.
  • Next-quarter action planning: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Inferring customer sentiment without evidence
  • Hiding unresolved product or service failures

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.