We let AI build it for us.
Therefore you need a very well written spec.
Short for: Technical Specifications.
The reason you need a spec is simple. It is like the architecture of a house.
You need to make sure the foundation is made for the weight of the roof.
In order to know what kind of foundation you must build, you must know what roof will be put on top.
In short: Get the full picture of the automation only then automate.
Before I dive into a very technical boring story. I’ve made it as simple as possible.
Together with the Baseloop plugin it will build the whole ‘spec’ for you.
Click here to start with Baseloop in Claude
Give the following 10 points to your Claude or Codex and ask it to interview you.
1. Name of the automation. One sentence what you want to solve
2. Data in. Where the data come from and in which format.
3. Data out. Where the data needs to sync into a sequencing tool or your CRM
4. Volume. How many records/leads do you want at the end
5. Where it stops. The last thing the automation does
6. How it works today. Who does it, in which tool, how many hours per week and the exact steps you do manually
7. Run conditions. What needs to keep running and what needs to be excluded.
8. Trigger. What starts a run and should it run on auto-on.
9. Success metric. When is the workflow a success.
10. Important details. Special rules, not in the points above but are important context to make this automation work.
Don’t forget to use Claude Opus 5 or GPT 5.6 Sol as your model.
Fable and Astra for the real players!
