no-man

Challenge and stress-test claims, plans, and assumptions before they enter work product.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill no-man-gozonerd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: no-man
Source: https://github.com/gozonerd/shadow-ai-assessment/tree/main/.claude/skills/no-man
Command: npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill no-man-gozonerd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Unverified claims and reflexive agreement let weak assumptions slip into pitches, deliverables, and evidence packages where they fail under scrutiny. This Skill forces every claim through a structured challenge protocol before it ships. ## Core Features & Use Cases - Structured Claim Challenge: A four-step protocol that names the claim, demands verifiable evidence, identifies failure conditions, and anticipates a competent reviewer's objections. - Three-Verdict System: Each claim is ruled HOLDS, UNGROUNDED, or WRONG, with specific guidance on what evidence would ground an ungrounded claim. - Reflexive Agreement Audit: A self-check step that catches agreement made because something sounded right rather than because it was verified. - Use Case: Before sending a pitch claiming a framework reduces formatting failures by 30%, run the protocol to verify the number is citable, name the conditions under which it fails, and confirm it survives a rigorous reviewer's first question. ## Quick Start Ask the AI to stress test this claim or plan using the no-man protocol before it goes into the deliverable.

Frequently Asked Questions about no-man

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

FAQPage Schema
How do I stress test a claim before putting it in a pitch?

State the specific claim precisely, then demand citable evidence, name the conditions under which it fails, and anticipate a competent reviewer's first objection. The protocol ends with a verdict of HOLDS, UNGROUNDED, or WRONG for each claim.

What is the difference between challenging a claim and auditing work product?

Challenging a claim tests whether it is grounded in evidence before it enters the work. Auditing work product compares finished output against its sources to catch divergence. The two are complementary and run at different stages.

When should I use a push-back review during planning?

Use it before architectural assumptions become code, before any number or framework is treated as established, and before any claim enters a deliverable. It is designed to run before writing, not after publication.

Does contrarian pushback slow down work that is already correct?

No. If evidence supports the claim, the verdict is HOLDS and it proceeds. The protocol does not manufacture objections; it only blocks claims that lack verifiable grounding or are contradicted by evidence.

What are the limitations of an evidence-challenge protocol?

It verifies grounding, not truth. A claim can pass with strong available evidence and still be wrong if the evidence itself is flawed. It also depends on the reviewer supplying precise claims rather than vague assertions.