brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
fact-checkingReview and validate claims using counter-hypothesis testing. Use when verifying technical content, checking references, validating API endpoints, or performing quality assurance on deliverables.
Independent GitHub snapshot · Automated classification · Original documentation governs
Codifies the challenger agent review output format and methodology so any agent performing fact-checking or review produces consistent, structured output.
For every claim or deliverable under review:
When reviewing another agent's work, use this template:
### Fact Check — {deliverable name}
**Claims verified:** {count}
**Issues found:** {count}
| # | Claim | Status | Evidence/Notes |
|---|-------|--------|---------------|
| 1 | {claim} | ✅/⚠️/❌ | {supporting or contradicting evidence} |
**Counter-hypotheses tested:**
- {alternative explanation + result}
**Verdict:** {PASS / PASS WITH NOTES / NEEDS REVISION}
Auto-trigger this skill before any architecture decision, or when an agent claim contains superlatives or percentage thresholds (e.g., "saves 75%", "always", "never"). The coordinator spawns the challenger agent with:
Challenger — fact-check {agent}'s claim: "{claim}"
Cite evidence for every verdict. Max 3 investigation cycles.