| name | spec-to-repo |
| description | Spec to repo: turn a product specification, PRD, or feature description into a complete working repository with code, tests, CI, and documentation |
Spec to Repo Skill
When to activate
- You have a clear spec or PRD and want Claude to build the full implementation
- Starting a greenfield project from a product brief
- Converting a design doc or technical spec into runnable code
- Building a proof-of-concept that implements a well-defined interface
When NOT to use
- Exploratory prototypes where the spec is unclear — discover first, then spec
- Large complex systems that exceed a single context window
- When you want to learn by building — this generates everything at once
Instructions
Spec ingestion
Build a repository from this specification.
Specification: [paste spec, PRD, or feature description]
Before generating any code, produce:
1. UNDERSTANDING CHECK:
- Summarise what you're building in 3 bullet points
- List any ambiguities or missing information
- Confirm the tech stack you'll use
2. FILE PLAN:
- List every file you'll create before creating any
- This gives me a chance to redirect before you start
3. IMPLEMENTATION ORDER:
- What do you build first? (usually: schema → types → core logic → API → UI → tests)
Wait for my approval before proceeding.
Full repository generation
Generate a complete repository for [project].
Spec: [paste spec]
Stack: [specify or use defaults]
Generate in this order:
1. Project scaffolding (package.json, tsconfig, .gitignore, .env.example)
2. Database schema (if applicable)
3. Core business logic (services, utilities)
4. API layer (routes, controllers, validation)
5. UI layer (if applicable)
6. Tests (unit + integration for core logic)
7. CI/CD (GitHub Actions)
8. README with setup instructions
Rules:
- Every file must be complete and runnable — no TODOs, no placeholders
- Tests must actually test the logic (not mock everything)
- README must include: install, configure, run, test commands
- .env.example must document every required variable
- All TypeScript (if Node.js) must compile without errors
