spec-to-repo

Topics in the source

• Spec to Repo
• When to Use
• Core Workflow
• Phase 1 — Parse & Interpret
• Phase 2 — Architecture
• Phase 3 — Generate
• Phase 4 — Validate
• Examples

Turn a natural-language project specification into a complete, runnable starter repository. Not a template filler — a spec interpreter that generates real, working code for any stack. User provides a text description of an app and wants code User has a PRD, requirements doc, or feature list and needs a codebase User says "build me an app that...", "scaffold this", "bootstrap a project" User wants a working starter repo, not just a file tree Not this skill when the user wants a SaaS app with Stripe + Auth specifically — use product-team/saas-scaffolder instead. Read the spec. Extract these fields silently: | Field | Source | Required | |-------|--------|----------| | App name | Explicit or infer from description | yes | | Description | First sentence of spec | yes | | Features | Bullet points or sentences describing behavior | yes | | Tech stack | Explicit ("use FastAPI") or infer from context | yes | | Auth | "login", "users", "accounts", "roles" | if mentioned | | Database | "store", "save", "persist", "records", "schema" | if mentioned | | API surface | "endpoint", "API", "REST", "GraphQL" | if mentioned | | Deploy target | "Vercel", "Docker", "AWS", "Railway" | if mentioned | St

This is an excerpt. Refer to the complete source and its current requirements.