AI Blocks › Build and ship software
Get a first working service from your spec, with every route tested and documented
Give it a spec. Get a project, a working service, route tests and an API spec.
Turn a spec into a tested service with API docs is a free AI workflow for the job "Build and ship software". It guides your AI through several skills in order, passing each step's output to the next.
Free · No account · Made by AI Blocks · Thinking: high
What it does
A written spec is not a service yet. The gap between them is the project setup, the routes, the database and the tests. If an AI fills it in one pass, you get code with no tests and documentation that does not match the routes. The steps close the gap in order. The first reads your spec, says back what it understood so you can correct it, and generates the project with setup steps. The second builds the routes, the database and the sign-in checks, and load tests the busiest route. The third finds every route in the code and writes tests for sign-in, bad input and error codes. The last reads the finished routes and writes the API spec, so the documents match what was built.
You give it
- A written spec that says what the service does, who uses it and what data it keeps
- Your preferred language and database, or let it choose
- How sign-in should work (optional)
- Where it will run (optional)
You get
- A project folder with the structure and setup steps
- Routes, database design and sign-in checks
- Tests for every route, with sample data
- A complete API spec file you can share
Use it when
- You have a spec or a feature list for a service and no code yet.
- You want tests and API docs that match the code, not written from memory.
- A new project needs a sound first version before the team builds on it.
Steps
- Spec to starter repo builder: Give it a written spec. Get a new project folder with the structure, setup and first working code.
- Backend builder: Say what the service must do. Get API routes, database design and secure login written for you.
- API test suite builder: Point it at your endpoints. Get integration and contract tests for each route, with fixtures.
- API spec writer: Describe your API or paste its code. Get a complete OpenAPI or Swagger spec ready for docs and SDKs.
How to use it
- Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
- Open an empty folder in Claude Code, give it the pack and say "Follow HANDOFF.md".
- Paste your spec. Check the plain-words summary it gives back and fix anything it got wrong.
- After the build, run the service and the tests yourself.
- Open the API spec in a viewer and compare it with a few real requests.