pipeline-judge

Review business plan artefacts against ground-truth data and generate JUDGE-REPORT.json.

4|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/danielgap/openclaw-planitor --skill pipeline-judge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline-judge
Source: https://github.com/danielgap/openclaw-planitor/tree/main/skills/pipeline-judge
Command: npx skills add https://github.com/danielgap/openclaw-planitor --skill pipeline-judge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables robust adversarial review of business plan artefacts to detect inconsistencies, inflated promises, and unverified assumptions early in the planning process.

Core Features & Use Cases

  • Adversarial review: systematically challenges plans, cross-checking numbers, assumptions, and buyer personas for internal consistency.
  • Cross-data validation: compares plan artefacts against ground-truth data and research inputs (e.g., research-web.json, research-benchmarks.json) to surface mismatches.
  • Structured reporting: outputs a formal JUDGE-REPORT.json with verdict, scores, issues, and recommended actions.

Quick Start

Review the provided plan-final.md and associated artefacts to produce a JUDGE-REPORT.json in the appropriate project version directory.

Frequently Asked Questions about pipeline-judge

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

FAQPage Schema
How do I cross-check a business plan for inconsistencies and inflated promises?

Adversarial review of business plan artefacts identifies inconsistencies, inflated promises, and unverified assumptions by systematically challenging numbers, buyer personas, and internal coherence against ground-truth data.

What is an adversarial review of business plan artefacts?

Adversarial review systematically challenges plan-final.md documents by cross-checking numbers, assumptions, and buyer personas for internal consistency, realism, and completeness to surface factual gaps early in the planning process.

How do I validate business plan assumptions against ground-truth data?

Cross-data validation compares plan artefacts against research-web.json, research-benchmarks.json, and ground-truth.json inputs to surface mismatches and verify coherence, realism, and completeness across cross-project version folders.

Can I generate a structured report from cross-checking business plans?

Structured reporting outputs a formal JUDGE-REPORT.json file containing the verdict, scores, identified issues, and recommended actions directly into the appropriate project version directory.

What inputs do I need to perform adversarial fact-checking on a business plan?

Adversarial fact-checking requires inputs such as plan-final.md, cross-project version folders, research-web.json, research-benchmarks.json, and ground-truth.json to verify coherence and generate a validation report.

When should I use adversarial review for my business plan?

Adversarial review is used early in the planning process to detect unverified assumptions and factual gaps, ensuring plan artefacts maintain coherence and realism before finalizing business strategies.