idea-to-mvp-buildlisted

Use this whenever the user mentions wanting to build, make, or create an app, product, feature, or tool -- even casually, even without using words like "PRD," "technical prompt," or "scaffold." Trigger on phrases like "I want to build...", "I've been thinking about an app for...", "I have an idea for...", "what if there was a product/tool that...". Also trigger when the user already has a finished PRD (pasted, uploaded, or referenced) and wants it turned into a project scaffold. Walks the user from a raw idea through a refined AI Technical Prompt, a PRD (both fixed templates), a full project scaffold (AGENTS.md, agent rules, skill files, design tokens), a hallucination audit of everything generated, and a handoff with copy-pasteable prompts to actually start building the MVP. Always start at the Technical Prompt stage for a new idea -- never jump straight to a PRD or scaffold unless the user already supplies a finished PRD.
ask-ayomide/idea-to-mvp-build · ★ 0 · AI & Automation · score 70

Install: claude install-skill ask-ayomide/idea-to-mvp-build

# Idea → Technical Prompt → PRD → Project Scaffold → Handoff Five stages, always in this order for a brand-new idea. If the user arrives with an already-finished PRD, skip straight to Stage 3. 1. **AI Technical Prompt** — drafted, refined, explicitly confirmed 2. **PRD** — generated FROM the confirmed Technical Prompt, delivered as a file 3. **Project Scaffold** — AGENTS.md, agent rules, skill files, design tokens — each piece confirmed before the next starts 4. **Audit** — check everything Stage 3 produced against the PRD for invented/unsupported claims 5. **Handoff** — close the loop: deliver/confirm the scaffold and hand off the prompts to actually start building Every stage pauses for explicit confirmation before the next begins ("looks good," "let's move on," etc.) — not silence, not a tangential reply. ## Stage 1: AI Technical Prompt **Step 1 — Capture the idea.** If the user only mentioned it in passing, ask 2-3 quick questions to get the raw shape: what it does, who it's for, what's already decided vs. still open. Don't over-ask — fill gaps with reasonable, flagged assumptions. **Step 2 — Draft using this exact structure** (fixed — don't add, remove, or reorder sections; if one doesn't clearly apply, keep it brief rather than dropping it): - Role/Persona - Mission/Core objective - Context/Target users - Formatting/Input & output specification (the result produced for the user) - Constraints/Guardrails - Examples - Tone/Style - Fall back behaviour/Error handling