scaffold

Stars9

Forks1

UpdatedMay 30, 2026 at 23:29

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.

Installation

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.

Source

winchxyz

winchxyz/idea-to-build

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

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.

/scaffold — hand the brainstorm off to a buildable folder

Read core/CLAUDE.md and core/agents/scaffolder.md, and follow the scaffolder spec.
Gate: proceed only if Phase 6 (Plan) is complete. If Critique or Plan hasn't run, decline and say what's missing (run /critique, then /plan first).
Source of truth = context/<slug>.md. Distill what's recorded; do not invent decisions. Ask the user for anything missing.
Ask for the target folder path (default: a subfolder <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.
List what was created and tell the user to open the new folder in Claude Code to start building.

More from this repository

same 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

factcheck

winchxyz/idea-to-build

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.

2026-06-019

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

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.

/scaffold — hand the brainstorm off to a buildable folder

Read core/CLAUDE.md and core/agents/scaffolder.md, and follow the scaffolder spec.
Gate: proceed only if Phase 6 (Plan) is complete. If Critique or Plan hasn't run, decline and say what's missing (run /critique, then /plan first).
Source of truth = context/<slug>.md. Distill what's recorded; do not invent decisions. Ask the user for anything missing.
Ask for the target folder path (default: a subfolder <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.
List what was created and tell the user to open the new folder in Claude Code to start building.