protocol-9-runner

Audit numbers, financial claims, and planning proposals for factual grounding.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/oliverjone01-dev/t1 --skill protocol-9-runner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: protocol-9-runner
Source: https://github.com/oliverjone01-dev/t1/tree/main/.claude/skills/protocol-9-runner
Command: npx skills add https://github.com/oliverjone01-dev/t1 --skill protocol-9-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns numbers-heavy proposals into auditable decisions by forcing every figure, assumption, and upside claim to be checked before it can move forward.

Core Features & Use Cases

  • Tags every number as verified data or a hypothesis so unsupported claims are visible immediately.
  • Runs a five-question reality audit covering audience behavior, assumptions, available data, downside risk, and the first checkpoint.
  • Applies hard rules for budgets, ranges, external presentation claims, and missing links in the client-to-product chain.
  • Use it for finance reviews, roadmap prioritization, external pitch decks, benchmark comparisons, and any plan that promises growth or ROI.

Quick Start

Use protocol-9-runner to audit this proposal, tag every number, and return the final go, pilot, block, or kill verdict.

Frequently Asked Questions about protocol-9-runner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit financial claims and validate budget proposals for unsupported assumptions?

Auditing financial claims requires tagging every figure as verified data or a hypothesis to expose unsupported assumptions. Applying a five-question reality check on audience behavior, downside risk, and available data separates factual numbers from speculative growth promises.

What is the best way to reality-check ROI estimates and growth promises in a pitch deck?

Reality-checking ROI estimates involves running assumption checks and downside analysis on every growth claim. Applying hard rules for external presentation claims and missing links in the client-to-product chain ensures pitch deck numbers are factually grounded before approval.

How do I tag financial estimates in a roadmap to separate verified data from hypotheses?

Tagging financial estimates in a roadmap requires labeling every number as either verified data or a hypothesis. This figure tagging process makes unsupported wide ranges and budget requests immediately visible for prioritization reviews.

Can I use a reality audit to triage budget requests and roadmap items before approval?

A reality audit can triage budget requests by applying five reality questions covering assumptions, downside risk, and the first checkpoint. This process returns go, pilot, block, or kill verdicts that separate grounded data from hypotheses before moving forward.

When do I need a budget validation process for benchmark comparisons and wide ranges?

Budget validation is needed when planning proposals contain estimates, wide ranges, or external benchmark comparisons. Applying hard rules for missing links in the client-to-product chain ensures these financial claims have factual grounding before review.