One Scenario, Four Skills
This demo shows the full judgment loop: make the mess legible, challenge the thinking, deliberate the decision, and create evidence before commitment.
Scenario
Our team thinks onboarding is too complicated. Sales says prospects ask for simpler setup. Support says new customers are confused by permissions. Product says activation is stable. Data says the problem may only affect enterprise customers. Leadership wants to know whether we should rebuild onboarding next quarter or focus on segmentation and targeted setup help.
1. Make the Mess Legible
Use The Briefing Room to separate the raw context into facts, claims, assumptions, tensions, open questions, and next use.
Use The Briefing Room on this messy context. Separate facts, claims, assumptions, tensions, contradictions, open questions, and the best next use.
- Facts separate from claims.
- The activation-versus-confusion tension becomes visible.
- The brief identifies what kind of thinking should happen next.
2. Challenge the Thinking
Use Ground Truth to challenge the diagnosis before the team commits to a solution.
Use Ground Truth on this brief. Do not validate the current diagnosis by default. Identify the weakest assumption, strongest counterargument, missing evidence, and what should happen before we commit roadmap time.
- The jump from "users are confused" to "rebuild onboarding" gets tested.
- Alternative explanations become visible.
- The recommendation shifts toward evidence before commitment.
3. Deliberate the Decision
Use The Quorum if leadership needs a real decision with visible trade-offs.
Use The Quorum on this decision: should we rebuild onboarding next quarter, or run a targeted diagnostic path around segment-specific onboarding friction first? Preserve disagreement and give me a calibrated recommendation with a pre-mortem.
- Multiple lenses independently assess the trade-off.
- The council distinguishes urgency, reversibility, execution cost, and political pressure.
- The chairman gives a calibrated recommendation and preserves dissent.
4. Create Evidence
Use Test Drive to design the smallest credible evidence loop.
Use Test Drive to design the smallest credible test for whether onboarding complexity is the real problem. Include evidence type, smallest credible test, artifact needed, connector path, approval gate, support signals, weaken signals, and learning loop.
- The skill identifies the evidence type.
- It proposes a small test and names connector needs or manual fallbacks.
- It defines what would support, weaken, or change the plan.
What This Shows
The bundle is not a chain of prompts. It is a judgment loop: make context readable, keep reasoning honest, deliberate consequential trade-offs, and create evidence before commitment. Use the smallest part of the loop that matches the situation.