Inventory every claim

Collect what the product says about itself - everywhere.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule

Inventory every claim this product makes. Sources: the landing page, feature lists, README, submission/marketing copy, and UI microcopy. Extract each claim as a testable statement (e.g. 'users can export to CSV', 'data syncs across devices', 'works on mobile'). Flag vague claims ('fast', 'secure', 'seamless') for definition - each must be rewritten as something checkable or marked for removal. Produce the numbered claim list.

Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A numbered list of testable claims with vague ones flagged.

Should NOT happen

An existing feature broke
A button only logs to console
Data disappears after refresh
Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Your notes for this step

Track what changed, failed, or needs follow-up. Notes export with the flow.

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

All copy sources were scraped for claimsEach claim is phrased testablyVague claims are flagged

Do not continue if…

! Claiming 'real-time' for polling, 'secure' for nothing-in-particular
! Evidence that is just a screenshot of the UI existing
! Untested claims shipped in the landing copy
! Verification steps nobody could reproduce

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

Claims are still vague. Rewrite each flagged one as a measurable statement ('loads in under 2s on 4G', 'passwords hashed with bcrypt') or queue it for deletion.