spec to repo

Engineering Community

Skill notes

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.

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

Phase 2 — Architecture

Design the project before writing any files: Select template — Match to a stack template from references/stack-templates.md Define file tree — List every file that will be created Map features to files — Each feature gets at minimum one file/component Design database schema — If applicable, define tables/collections with fields and types

Phase 3 — Generate

Write every file. Rules: Real code, not stubs. Every function has a real implementation. No // TODO: implement or pass placeholders. Syntactically valid. Every file must parse without errors in its language. Imports match dependencies. Every import must correspond to a package in the manifest (package.json, requirements.txt, go.mod, etc.). Types included. TypeScript projects use types. Python projects use type hints. Go projects use typed structs.

Phase 4 — Validate

After generation, run through this checklist: [ ] Every imported package exists in the manifest [ ] Every file referenced by an import exists in the tree [ ] .env.example lists every env var used in code [ ] .gitignore covers build artifacts and secrets

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Manual integration
External API key
Required · Vendor-specific
Operating systems
Docker
Runtime requirements
Node.js · Python · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
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

02
Phase 2 — Architecture

Design the project before writing any files: Select template — Match to a stack template from `references/stack-templates.md` Define file tree — List every file that will be created Map features to files — Each feature gets at minimum one file/component Design database schema — If applicable, define tables/collections with fields and types

03
Phase 3 — Generate

Write every file. Rules: Real code, not stubs. Every function has a real implementation. No `// TODO: implement` or `pass` placeholders. Syntactically valid. Every file must parse without errors in its language. Imports match dependencies. Every import must correspond to a package in the manifest (package.json, requirements.txt, go.mod, etc.). Types included. TypeScript projects use types. Python projects use type hints. Go projects use typed structs.

04
Phase 4 — Validate

After generation, run through this checklist: [ ] Every imported package exists in the manifest [ ] Every file referenced by an import exists in the tree [ ] `.env.example` lists every env var used in code [ ] `.gitignore` covers build artifacts and secrets

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.