From intent to testable behavior
Know what to test. And why.
Start with a feature specification. Resolve ambiguous rules, see the risks, and leave with a test plan your team can use.
Saved drafts
Your saved projects in this browser. Opening a draft does not start another analysis.
Project links & access
The draft link requires this browser’s access cookie. To let someone else read your specification, answers and results, create a separate read-only link. Anyone with that link can read the latest saved report until it expires or you disable sharing.
Local preview links work only on this computer. External sharing will work once this feature is deployed to the website.
Technical details
Add a specification or try the example to begin.
Checking service availability…
Private by default. Not used by Proof for AI training. Deleted after 30 days, or sooner when you delete the project.
Your specification, answers and generated review are sent to the configured AI provider. Leave out secrets. No repository access or application test execution is needed.
How your data is handled
Current model configuration: not yet available. Recorded request identities are included in the report.
Your specification, answers, generated requirements, test plan and project files expire after 30 days and are automatically cleaned up. Use “Delete project” to remove your project earlier. Draft and shared links stop working when the project is deleted. Existing projects keep the expiry shown beside their draft link. Download anything you want to keep.
We use your content to generate and review your plan. OpenRouter requests are restricted to model providers whose policies disallow training on inputs and outputs. This is separate from provider logging and retention; provider data policies apply.
A signed browser-access cookie expires 30 days after it is issued or renewed. It can renew while you use Spec Lab; renewal does not extend the project’s expiry. The draft URL restores your review. Clearing browser storage can prevent you from reopening the project.
Deleting removes the temporary Proof project, not downloaded copies or records already held by the AI providers. Non-content usage records, such as token counts and cost totals, are retained separately for billing, limits and abuse prevention. Provider retention is separate from Proof’s project expiry. Website privacy · Ask about data handling
This is the original specification saved with this project. Suggest a correction to create a new revision; the original text and prior analysis remain available. Use Saved drafts to return to another project.
Your working document
Test plan
Decisions that need you
Proof is looking for missing decisions and turning the behavior into requirements. This can take a few minutes.
Activity log
Planned checks, not test results. Run these against your implementation and collect the evidence.
Requirements-based tests
Acceptance outcomes
Check that these outcomes match what the feature must do. Expand an outcome to see which generated cases already exercise it. Reuse those tests; add separate checks only when an outcome needs a different setup, journey or integration.
Hazards & failure checks
Start from the worst-case failures recorded for each requirement. Define how the system must respond, then collect evidence a reviewer can inspect. A test may reuse inputs from the decision table; here it must also demonstrate the required failure handling.
Decisions still needed
Requirements
Original specification
Your submitted text. Compare it with the requirements below.
Read full specification Collapse original specification
Data rules
Which values and combinations matter?
Decision matrices, limits and data constraints recorded from your specification. Missing combinations remain open decisions.
Open decisions & missing checks
Specification supporting records
Data limits and combinations
These recorded limits and combinations shape the test cases. No separate approval is needed here. If something does not match your specification, suggest a correction. Recording your review of the whole revision is optional.
Original specification & your answers
Record that you reviewed this revision Optional
This records your review of this specification snapshot. No application tests have run, and the implementation is not verified. It does not approve a release or certify completeness. You can view and download the plan without recording a review.
Requirement logic & truth tables
Inspect the formal conditions, independent condition changes and remaining coverage limits.
Decision coverage
These tables explore the formal requirement, including combinations an implementation must prevent. They explain coverage; they do not claim the application passed these checks.
Technical record & analysis checks
What Proof checked
Inspect the analysis behind this plan.