Agent skill · software engineering · alirezarezvani
spec-to-repo
Use when the user says 'build me an app', 'create a project from this spec', 'scaffold a new repo', 'generate a starter', 'turn this idea into code', 'bootstrap a project', 'I have requirements and need a codebase', or provides a natural-language project specification and expects a complete, runnable repository. Stack-agnostic: Next.js, FastAPI, Rails, Go, Rust, Flutter, and more.
Why this skill is useful
Generates complete runnable codebases from natural language specifications, providing executable templates and architecture that the AI cannot infer on its own.
What it needs
Requires flutter, go, node, python installed locally. About 6k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
Spec to Repo 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. When to Use 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. Core Workflow Phase 1 — Parse & Interpret 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 Stack inference rules (when user doesn't specify): Signal Inferred stack -------- --------------- "web app", "dashboard", "SaaS" Next.js + TypeScript "API", "backend", "microservice" FastAPI (Python) or Express (Node) "mobile app" Flutter or React Native "CLI tool" Go or Python "data pipeline" Python "high performance", "systems" Rust or Go After parsing, present a structured interpretation back to the user: Flag ambiguities. Ask at most 3 clarifying questions. If the user says "just build it", proceed with best-guess defaults. Phase 2 — Architecture Design the project before writing any files: 1. Select template — Match to a stack template from references/stack-templates.md 2. Define file tree — List every file that will be created 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/spec-to-repo--050b3b