factcheck

Sterne9

Forks1

Aktualisiert1. Juni 2026 um 01:15

Apply the idea-to-build verification protocol (Tier 1/2/3, Skeptical-by-Default) to a specific claim. Use when the user types "/factcheck" followed by a claim, or asks to verify, fact-check, or pressure-test a specific statement.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Quelle

winchxyz

winchxyz/idea-to-build

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Marktforschungsanalysten und MarketingspezialistenWirtschafts- und Finanzberufe·SOC 13-1161

SKILL.md

readonly

name	factcheck
description	Apply the idea-to-build verification protocol (Tier 1/2/3, Skeptical-by-Default) to a specific claim. Use when the user types "/factcheck" followed by a claim, or asks to verify, fact-check, or pressure-test a specific statement.

/factcheck — verify a claim (Skeptical-by-Default)

Read core/CLAUDE.md (the Factual Rigor / Tier 1/2/3 protocol and the Skeptical-by-Default stance).
The claim to verify is whatever the user provided after /factcheck (as a slash command, that's $ARGUMENTS). If it's empty, ask which claim to check. Then classify it:
- Tier 1 — logic, math on given numbers, fundamental concepts → assert directly.
- Tier 2 — tool details, "best practices", memory-based claims below ~90% confidence → mark ⚠️ and verify when possible.
- Tier 3 — market sizes, prices, competitor data, current platform policies, recent news, anything that could have changed in the last 6–18 months → search before stating.
For Tier 3, search first, then cite the source (title + year, URL if available).
Label the verdict: ✅ verified / ⚠️ hypothesis / 🔍 needs verification. If no reliable source exists, say so plainly — never fabricate.
If the claim is false or shaky, say so directly and name exactly what would confirm or refute it.

Mehr aus diesem Repository

gleiches Repository

recheck

winchxyz/idea-to-build

Re-critique a project after the build, with real execution results — does the data disconfirm the THESIS or just the tuning? Use when the user types "/recheck" (often with results/data pasted) or asks to re-examine a project in light of how it's actually going.

2026-06-099

profile

winchxyz/idea-to-build

Switch the idea-to-build coordinator to a domain profile — general, startup, tech-architecture, content-strategy, product-roadmap, or personal-decisions. Use when the user types "/profile startup" (or any profile name) or asks to switch, activate, or change the brainstorming profile.

2026-06-029

start

winchxyz/idea-to-build

Activate the idea-to-build coordinator and begin (or resume) a structured 6-phase brainstorm. Use when the user types "/start" / "/idea-to-build:start" or asks to begin an idea-to-build session.

2026-06-029

phase

winchxyz/idea-to-build

Jump the idea-to-build session to a specific phase (1–6). Use sparingly — when the user types "/phase 4" (any phase 1-6) or explicitly asks to skip to a phase.

2026-06-019

critique

winchxyz/idea-to-build

Run the idea-to-build Critic (Phase 5, in-context) on the currently chosen idea. Use when the user types "/critique" or asks to run the critique, stress-test, or premortem the chosen idea now.

2026-06-019

memory

winchxyz/idea-to-build

Show what idea-to-build has recorded in the current project's context file. Use when the user types "/memory" or asks what's saved / remembered about the project.

2026-05-309

name	factcheck
description	Apply the idea-to-build verification protocol (Tier 1/2/3, Skeptical-by-Default) to a specific claim. Use when the user types "/factcheck" followed by a claim, or asks to verify, fact-check, or pressure-test a specific statement.

/factcheck — verify a claim (Skeptical-by-Default)

Read core/CLAUDE.md (the Factual Rigor / Tier 1/2/3 protocol and the Skeptical-by-Default stance).
The claim to verify is whatever the user provided after /factcheck (as a slash command, that's $ARGUMENTS). If it's empty, ask which claim to check. Then classify it:
- Tier 1 — logic, math on given numbers, fundamental concepts → assert directly.
- Tier 2 — tool details, "best practices", memory-based claims below ~90% confidence → mark ⚠️ and verify when possible.
- Tier 3 — market sizes, prices, competitor data, current platform policies, recent news, anything that could have changed in the last 6–18 months → search before stating.
For Tier 3, search first, then cite the source (title + year, URL if available).
Label the verdict: ✅ verified / ⚠️ hypothesis / 🔍 needs verification. If no reliable source exists, say so plainly — never fabricate.
If the claim is false or shaky, say so directly and name exactly what would confirm or refute it.