Menu
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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
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.
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.
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.
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.
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.
| name | recheck |
| description | 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. |
The user built (or started building) a project from an earlier idea-to-build brainstorm and now has real results. They want the critic to re-examine it in light of that data — not to tune parameters, but to question whether the core thesis still holds. This is the loop that catches calibration-myopia while it's happening, which a one-time pre-build critique cannot.
core/CLAUDE.md (coordinator role) and core/agents/critic.md — especially its "Re-critique mode (invoked with results)" section.context/<slug>.md for the chosen idea, its core thesis, the original critique, and the rejected alternatives. If it's unclear which project this is, ask. If the built project has a FRAME-LOG.md (written by /scaffold's frame-check guardrail), read it too — it's the run-record of in-build tuning-vs-thesis calls and their predictions. Use it as evidence: a long trail of altitude:in-build tuning entries with no thesis-test is itself a calibration-myopia signal./recheck (as a slash command, $ARGUMENTS) — pasted data, metrics, or a description of how it's going. If none is given, ask what actually happened.context/<slug>.md (dated, in English), so the project's log carries it.