Draft spec

Review report

0

Run the checker to score the draft.

Missing sections

    Vague terms

      Lines to clarify

        Ready to check.

        What to do with the findings

        A vague term is not automatically wrong. It is a prompt to ask whether the spec defines the behavior well enough for implementation. Replace "fast" with a latency target, "relevant" with a selection rule, and "works" with an observable state-action-result example.

        For a deeper human pass, use the Spec Review Checklist. To rebuild the draft from structure instead of patching prose, use the Spec Builder.

        What does the Ambiguity Checker flag?

        It flags vague terms, missing spec sections, weak acceptance criteria, and requirement-like lines that lack measurable detail.

        Is the Ambiguity Checker an AI reviewer?

        No. It uses deterministic browser-side regex and section heuristics. It is meant to catch common spec smells before human review.

        Does the Ambiguity Checker upload my spec?

        No. The text is analyzed in the browser and is not submitted to a server.

        What score should I aim for?

        Use the score as a triage signal, not a final grade. A spec with no missing core sections, few vague terms, and observable verification checks is usually ready for deeper review.