Athena can build an app in an hour and interview you first to write a one-page plan with the problem, who uses it, what goes in and out, which building blocks to use, and the test cases that prove it works. Spend twenty minutes on that plan so you build the right thing and can turn its test cases directly into checks for the build.
Why plan if the build takes an hour?
Athena builds what you ask for in an hour, so a clear plan makes sure you ask for the right thing. Writing the plan first solves three common problems:- You solve the actual problem, instead of building a dashboard when the team needed a list of items to review.
- Everyone agrees on what “working” means, because the test cases define it up front.
- Engineers can take the build over, because teams that want a written requirement already have one.
What goes in the plan?
Your Trigger and Judgment answers point to the right building blocks. Fixed steps on a schedule point to an Automation, reading and deciding points to an AOP (Agent Operating Procedure), and people entering records all day points to an Application.

How does Athena interview me?
Athena interviews you one question at a time, bases each question on your last answer, and often suggests an answer you can accept with a click. Save the text below as a Skill in your workspace and add it to your Agent. Then start a conversation and say “interview me for a spec”.How does the plan become an app?
Turn each test case into a check:- Have the business owner read the plan and sign off on the test cases.
- Pick the building blocks using the plan’s suggestion, or see When to use what.
- Give Athena the plan to start building, and include the build standard if you are building an app.
- Turn the test cases into checks, as shown in the next section.
- Keep the plan current, since the next owner will read it first.
How do I prove it works?
What to plan for
Keep the interview Skill in your workspace and make planning a team habit, since Athena lets you start building without a plan. Talk to whoever does the work today with a real example open when you run the interview. When the business process changes later, update the test cases first and run them again.Questions teams ask
Is this a product requirements document?
Is this a product requirements document?
It is a one-page version of one. An engineer can take over from it, and a reviewer can check the work against it. You can expand it for business-critical or public apps.
Can the interview run as an AOP?
Can the interview run as an AOP?
Yes. Put the same instructions in an AOP so anyone on the team can start it from a form, and send the finished plan into a set folder.
We already built the prototype. Is it too late?
We already built the prototype. Is it too late?
No. Run the interview and write the test cases, then test the prototype against them to see whether to keep it.
Who owns the plan?
Who owns the plan?
The business owner owns the problem, the user, and the test cases. The builder owns the choice of blocks and the build.
See it work
Thirty minutes, your workflow, and you leave with the work product.

