القائمة
After a completed idea-to-build (Phase 6 done), generate a ready-to-build project folder — CLAUDE.md + README + DECISIONS + PLAN — so you can open it in Claude Code and start building. Use when the user types "/scaffold" or asks to scaffold / hand the brainstorm off to a build.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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.
| name | scaffold |
| description | After a completed idea-to-build (Phase 6 done), generate a ready-to-build project folder — CLAUDE.md + README + DECISIONS + PLAN — so you can open it in Claude Code and start building. Use when the user types "/scaffold" or asks to scaffold / hand the brainstorm off to a build. |
core/CLAUDE.md and core/agents/scaffolder.md, and follow the scaffolder spec./critique, then /plan first).context/<slug>.md. Distill what's recorded; do not invent decisions. Ask the user for anything missing.<slug>/ inside the current workspace — a sibling ../ path is often blocked by the host's write scope) and the tech stack (or "let Claude Code decide"), then write the Tier 1 files — CLAUDE.md, README.md, DECISIONS.md, PLAN.md — into it. Produce the briefing, not application code. Never overwrite existing files without confirming.