The foundations a senior engineer would insist on.
From your answers, the foundations to build first, each with its reason and source. The plan from rules is free.
14 days free. No card needed.
Plain questions in. A plan with its reasons out.
Foundations cost the most to add later. The plan sorts them into v1, Later and Not now.
Answer the questions (free)
Mind ticks what it thinks fits your product, with the words it came from, and you untick what is wrong.
See the plan (free)
It is drafted at once by rule, with no AI call, so the same answers always give the same plan.
Tailor and check (AI credits)
Mind reads your features for what each needs to work safely, how your flows could be abused, and a senior engineer's check.
Accept into the Map
Each group becomes an Idea feature in its lane, with a draft story per item.
This week first, then v1, Later and Not now.
What to do this week is at most five lines, in order. It holds the one-way decisions you weren't asked, what only you can decide, and questions for your developer.
- Every item says why. Its source, its lane, who decides, and Done when.
- Sized to your numbers. A load test goes in v1 when you need one.
- What you have is marked. A live capability shows Already on your map.
The questions to send your developer.
You know the market and the customer. The plan turns what only a developer can settle into questions you can send as they are.
Send these N questions
The items your answers can't settle, worded for a developer, with Copy all. You don't have to know the answer to ask the right question.
How someone could abuse it
After Tailor and check: each case with who, the impact, and what covers it, or the question to ask when nothing does.
The critic's notes
A second pass leaves notes such as Move to v1 or Add the fix story. Applying a note is a decision, and what the checks removed can be restored.
Every Build Pack then carries FOUNDATIONS.
Accept into the Map shows what would be created before anything is. Undo lasts 24 hours.
Each feature's Build Pack then holds the plan's decisions, one-way calls first, the rules every feature follows and the size to build for. On a bug's page, editors can say which foundation was missing, and the next plan raises it.
What the plan will not do
Before each release, the publish check lists what changed from your commit titles. Neither it nor the plan reads your code.
Does the free plan use AI?
No. The plan from rules is free: no AI call. The same answers always give the same plan. Tailoring it to your own features uses AI credits, included on Growth and Scale, and the credits come back if tailoring fails or keeps nothing.
Do I need to be technical to use it?
No. The questions are plain: what kind of product it is, who buys and uses it, and how it is delivered. One asks about high-stakes areas such as health, finance or hiring. Mind ticks what it thinks fits, and you correct it.
What are the questions for my developer?
The items your answers can't settle, worded so a developer can answer them, with Copy all. They sit in What to do this week, beside the one-way decisions you weren't asked and the first things only you can write.
Is the plan legal advice?
No. It is a framework. Risk lines end "Check with counsel where you operate", and the plan never says a product is legal.
What happens when I accept the plan?
Each group becomes an Idea feature in Build › Features, in its lane, with a draft story per item and its Done when as acceptance checks. Undo lasts 24 hours. From then on every Build Pack carries a FOUNDATIONS section for your coding agent.
Know what to ask before you build.
Answer about ten plain questions. The plan from rules is free, and the questions for your developer come with it.
- 14 days free
- No card needed
- Viewers are free
