AI Blocks › Build and ship software
Get a feature built from a plain idea, in small pieces you can check
Give it a feature idea. Get a spec, small tickets, built code, test gaps and a pull request.
Turn an idea into a spec, tickets and tested code 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
When you ask an AI to build a whole feature from one sentence, it guesses. It fills the gaps with its own ideas, builds it all at once, and hands you a pile of code that is hard to review and has few tests. The steps here take the guessing out. The first writes down what the feature must do, so nothing is left to chance. The second cuts that spec into thin tickets, each one working from end to end, with the order they depend on. The third builds the tickets one at a time and reviews the whole. The fourth lists every new behaviour that no test checks. Then you add those tests and run them, and the last step writes a pull request that shows the proof.
You give it
- A feature idea, in a few sentences, and who it is for
- Access to your project code
- Your issue tracker, if you use one (the spec and tickets are posted there)
- Your written coding standards (optional)
You get
- A spec with the problem, user stories and the decisions made
- Small tickets in build order, each saying what blocks it
- The feature built on one branch and reviewed
- A list of new behaviours with no test, and the tests to add
- A pull request with a short summary and proof
Use it when
- You have a feature in your head and no written spec yet.
- Past AI builds came back too big to review.
- You want tests and a pull request that a teammate can read in ten minutes.
Steps
- Spec writer: Talk through your idea. Get the conversation turned into a spec and posted to your issue tracker.
- Ticket planner: Give it a plan or spec. Get small tickets that each say what blocks them, posted to your tracker.
- Spec builder: Give it a spec and tickets. Get the work built in code, tested and reviewed.
- Code change test coverage review: Give it a code change and your tests. Get each new behaviour marked covered or not, plus test cases for the gaps.
- Pull request writer: Give it your changes. Get a clear pull request description a reviewer can follow.
How to use it
- Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
- Open your project in Claude Code, give it the folder and say "Follow HANDOFF.md".
- Describe the feature, then answer its questions about the tests and the ticket sizes.
- After the missing-test step, add the tests it proposes and run your suite before you go on.
- Read the pull request text and fix anything that does not match what you wanted.