Evidence-traceable decision presentations

Turn source material into a decision people can act on

Define the decision first, then build an evidence ledger and argument around it. Deliver a structured JSON contract, a self-contained HTML deck, and validation reports in HTML and JSON. Link material claims, numbers, charts, and recommendations to evidence IDs.

Claim-level traceabilityFacts separated from judgmentOffline HTML delivery
Weighted comparison for the Shanghai team activity decision Decision ready

Before / After

From an unstructured question to an actionable decision

Known inputs become a comparable baseline. Unknowns remain visible as measures to collect instead of being presented as facts.

BeforeCurrent state

A 30-minute stand-up every day, without a shared decision framework

25
person-hours / week of fixed sync time
  • Ten people attend five stand-ups each week
  • Calculation: 10 people × 0.5 hours × 5 meetings
  • No data for preparation, follow-up, productivity change, or team acceptance
AfterActionable option

Three live syncs and two async days, governed by transparency thresholds

12.5
person-hours / week of target fixed sync time
  • Run 25-minute syncs on Monday, Wednesday, and Friday
  • Use structured async updates on Tuesday and Thursday
  • Measure one baseline week, then run a reversible four-week pilot
Comparison of fixed synchronous meeting time

Reducing fixed meeting time is not the same as producing a net productivity gain. Productivity, preparation time, and team experience still need to be measured.

3real decision scenarios
4claim statuses
7slides in each current deck
1structured content contract

Core Capabilities

Give every conclusion a clear line of support

The goal is not to accumulate information. It is to help a decision owner see the recommendation, its basis, its conditions, and the next move.

01 · FRAME

Frame the decision first

Set the audience, decision owner, options, evaluation criteria, time horizon, and hard constraints.

02 · TRACE

Trace evidence at claim level

Assign stable IDs to sources, supplied material, calculations, and assumptions, then cite what supports each claim.

03 · LABEL

Keep uncertainty visible

Separate facts, inferences, assumptions, and recommendations. Preserve conditions, timing, and limitations.

04 · ARGUE

Match the storyline to the choice

Use decision-first, options comparison, SCQA, or evidence synthesis with takeaway headlines that move the argument forward.

05 · CONTRACT

Work from one content contract

Keep slide content, evidence, visual type, limitations, and speaker notes in structured form.

06 · DELIVER

Deliver an offline-ready deck

Deliver self-contained HTML with the JSON contract and validation reports. A source manifest is an additional research deliverable when requested; the pipeline does not generate it automatically.

Source-checkable factverified
Evidence-based judgmentinference
Explicit premiseassumption
Proposed actionrecommendation

How It Works

Fix the decision boundary before content and visual production begin

STEP 01

Frame the decision

Define who decides, what must be chosen, which options are in scope, and which constraints cannot move.

STEP 02

Collect and register evidence

Read supplied material; research externally only when authorized, prioritizing primary sources for consequential claims.

STEP 03

Choose the argument structure

Match the storyline to the decision instead of forcing a fixed slide count or generic section template.

STEP 04

Write the content contract

Specify each slide's takeaway, claims, visuals, limitations, and evidence relationships.

STEP 05

Generate the presentation

Run the pipeline to write validation reports and render the offline HTML deck when validation has no errors. Review warnings and inspect the rendered slides. PDF export is optional.

STEP 06

Review the reading experience

Read every page at desktop and mobile widths, checking content, charts, sources, and navigation.

Use Cases

For work where the choice and its trade-offs must be explicit

A/B

Options comparison

Build a consistent frame across budget, timing, risk, experience, and other decision criteria.

↗

Tool and vendor selection

Bring current pricing, capability differences, implementation conditions, and upgrade triggers into one argument.

Δ

Process change

Start with the current baseline, then design a reversible move, observation period, and continuation thresholds.

Case Studies

Three real decisions, one consistent evidence discipline

The examples span a team activity, a task-management platform, and a meeting cadence—covering options comparison, product selection, and operating-process change.

Weighted comparison of half-day team activity options
Options comparison

A half-day activity for a 12-person Shanghai team

Compare indoor interaction, a city-park activity, and a craft workshop within RMB 4,000, four hours, and a low-weather-risk preference.

RecommendationPrioritize indoor interaction at a conditional budget of about RMB 2,256; retain the craft workshop as backup.

Use the park only if conditions are stable 72 hours before the event; confirm capacity and final pricing before booking.

Annual license cost comparison for Trello, Notion, and Asana
Tool selection

Task management for an eight-person content team

Compare Trello, Asana, and Notion across cost, adoption, project management, collaboration, and automation.

RecommendationChoose Trello Standard, subject to a two-week pilot using one real editorial workflow.

Move to Asana Starter if complex dependencies, Gantt views, or cross-project reporting become requirements.

Observation period and continuation thresholds for a new stand-up cadence
Process change

Stand-up cadence for a 10-person team

Assess whether to replace a daily 30-minute stand-up with three weekly syncs and asynchronous updates on the remaining workdays.

RecommendationMeasure one baseline week, then run a four-week pilot with three sync days and two async days.

Use transparency, on-time updates, and blocker response as continuation guardrails; do not assume productivity will improve.

Reliability

Sources, calculations, and limitations stay with the deliverable

Primary sources for consequential claims

Prefer official pricing and product documentation, government material, peer-reviewed papers, and recognized research institutions.

Reproducible calculations

Record input evidence, formulas, units, periods, and display precision, then use the same results in charts.

Limitations remain visible

Keep pricing conditions, unconfirmed capacity, measures still to collect, and management assumptions in view.

No live webpage dependency

The deck contains the styles, scripts, and graphics it needs for meetings, internal sharing, and archiving.

Target Users

Built for teams expected to deliver the conclusion, evidence, and conditions together

Team leads

Understand the options, trade-offs, and next move quickly.

Operations and project managers

Compare alternatives, quantify constraints, and form an executable recommendation.

Strategy and research teams

Organize multiple sources into a reviewable argument without erasing uncertainty.

Client advisory and executive reporting teams

Present the recommendation, supporting evidence, and decision conditions in one delivery.

Start a decision

Start with one real decision

Provide the audience, options, evaluation criteria, and non-negotiable constraints. If no local material exists, state whether public research is authorized.

Please use the evidence-deck-builder Skill to create a presentation for [decision audience] about [decision question]. Compare [options], evaluate [criteria], and observe [time, budget, location, or other constraints]. Label facts, inferences, assumptions, and recommendations separately, and link material claims, numbers, charts, and recommendations to specific evidence IDs.

Select the prompt above to copy it.