Readiness score
How the 0–100 readiness score is calculated, what each band means and how to raise it.
3 min read
What it measures
The readiness score estimates how much useful context your AI tools will receive, from 0 to 100. It is a weighted checklist: each check carries a weight based on how much it changes the output. Checks that do not apply to your selected tools are left out, so the score always reflects the pack you are about to generate.
The checks
| Check | Applies to | Weight |
|---|---|---|
| Brief has enough detail | All packs | 20 |
| Features or screens | All packs | 15 |
| Target audience | All packs | 12 |
| Goals or outcomes | All packs | 10 |
| At least one export target | All packs | 10 |
| Product name | All packs | 8 |
| Constraints & rules | All packs | 6 |
| Platform | All packs | 5 |
| Brand & visual direction | Design and creative tools | 12 |
| Tech stack | Coding agents | 12 |
| Build / test commands | Coding agents | 4 |
| Template placeholders filled in | Packs started from a template | 15 |
Score bands
| Band | Score | What to expect |
|---|---|---|
| Draft | Below 50 | Usable for exploration; expect generic results. |
| Usable | 50–74 | Good enough for a first pass. |
| Strong | 75–89 | Tools follow your intent closely. |
| Excellent | 90+ | Ready for a multi-screen or multi-task build. |
Raising your score
- Each failed check shows a hint — fix the highest-weight items first.
- Attach a Repo Kit to satisfy stack and commands in one step.
- Attach a Brand Kit for colours, typography and tone.
- Signed-in users can use Structure with AI to fill empty fields from a messy brief.
Still stuck?
Open a support ticket and a person on the PromptForge team will reply, usually within one business day.