Create a specification completeness checker with Claude

A specification completeness checker is useful when you need to identify missing required specification fields using explicit criteria. The result should make the underlying records easier to inspect and the next decision easier to explain. This guide develops a specific specification completeness checker with a source schema, operating rules, a fictional example, and observable review checks. It is intended for someone who already has the underlying material and needs a dependable way to organize it.

Product references checked: 7 October 2026. The examples and implementation specifications below are original editorial guidance. They illustrate expected behavior and have not been presented as a benchmark or as a completed tool tested inside another product.

Define the deliverable and its scope

This is a completeness review against a supplied template, separate from requirement conflict analysis or verification of technical correctness.

Write the acceptance standard before asking Claude for a draft. A reviewer should be able to identify the requirement id, inspect the expected evidence, and understand the coverage summary without guessing what a blank field means. Decide which records belong in the deliverable, which are out of scope, and who can confirm the final interpretation. Keep those choices visible in the working specification rather than leaving the assistant to supply convenient defaults.

Prepare the source package

Gather an approved specification template, field requirements and a versioned draft. Assign source IDs and preserve original wording wherever a small difference could change the outcome. Record the collection date and the version of each source. If two files disagree, keep both references and mark the conflict. Do not replace a disputed value with whichever one produces the cleanest display.

Use a small representative subset for the first draft. Include one ordinary record, one incomplete record, and one record that challenges an important rule. For this task, use the following as the incomplete-record check: An empty required heading fails the presence check. Preserve the original package separately from the assistant's transformed output. A polished result is easier to audit when its IDs still lead back to the original supplied material.

Define the record schema

Treat requirement id as a deliberate part of the data model. Approved template criterion identifier. Keep its representation consistent when you sort, filter, or revise the output. The expected evidence field has a different job: Specific field, section, or condition required by the template. Combining these fields into one sentence can hide the distinction the reviewer needs to inspect.

Pay particular attention to located evidence and check outcome. The former means: Draft location and exact supporting content. The latter means: Present, missing, ambiguous, or not applicable with reason. Store them separately and label both in the detail view or report. This makes disagreements visible at the exact point where they affect the result instead of burying them in a general note at the bottom.

Apply the task rules

Rule 1. Only supplied template criteria are mandatory.

Rule 2. A heading without substantive content is missing evidence.

Rule 3. A not-applicable result requires an explicit reviewed reason.

Rule 4. Do not label a complete specification correct or safe solely because fields exist.

Make these rules inspectable alongside the specification completeness checker. Ask Claude to describe how each rule affects a record and what should happen when the supplied data does not establish an answer. A rule written in prose still needs a defined output state. Use an explicit missing, disputed, or not-applicable label where appropriate, and reserve a valid zero or an empty result for cases where it has a defined meaning.

Work through a fictional example

A fictional interface specification requires a retry limit, a failure message and an owner. The draft contains a retry heading but no value. It describes a failure message in paragraph P8 and names an owner in P2. The checker records the retry criterion as missing and links the other two criteria to their paragraphs. A later draft supplies a retry limit of three. That closes the presence check but still requires a separate review of whether three is appropriate. A criterion for offline behavior remains ambiguous because the draft describes only intermittent connectivity, not a fully disconnected state.

Use the example as a review fixture rather than as real operational data. Before generating the output, write down which fields should be populated and which should remain unresolved. Then compare the generated result with that expectation. If Claude supplies an unsupported value, correct the underlying instruction or calculation rule instead of merely editing the one visible record. Otherwise, the same error may return when the next record is processed.

Build the first version

Ask for the simplest interactive artifact that displays the schema and supports the specific review task. Start with the fictional example and an obvious detail panel. Keep the source data separate from display labels and interaction state. A selected row, a filter, or an open panel should change what the reviewer sees, not silently rewrite the underlying evidence. Add editing only to fields that the specification explicitly identifies as user inputs.

For the first interaction pass, prioritize reviewer action: The narrow question or evidence needed to close the gap. Then add the coverage summary behavior: Counts by outcome without treating presence as correctness. Use visible text labels for both. Test the core logic before spending time on animation or visual polish. Provide a keyboard path through the controls and preserve a readable empty state when the selected view has no records.

A reusable prompt

Create a specification completeness checker from the supplied source package. Goal: identify missing required specification fields using explicit criteria. Use these fields: Requirement ID: Approved template criterion identifier.; Expected evidence: Specific field, section, or condition required by the template.; Located evidence: Draft location and exact supporting content.; Check outcome: Present, missing, ambiguous, or not applicable with reason.; Reviewer action: The narrow question or evidence needed to close the gap.; Coverage summary: Counts by outcome without treating presence as correctness.. Preserve source IDs. Rules: Only supplied template criteria are mandatory. A heading without substantive content is missing evidence. A not-applicable result requires an explicit reviewed reason. Do not label a complete specification correct or safe solely because fields exist.. First explain the proposed data model and unresolved inputs. Then build the smallest usable version. Use only supplied facts; label the demonstration fictional. Do not invent approvals, thresholds, owners, or external integrations. Include an empty state and explain the expected result for these checks: An empty required heading fails the presence check. A new draft invalidates location links that no longer resolve. Not applicable without a reason remains unresolved.

Review behavior and edge cases

Check 1. An empty required heading fails the presence check. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.

Check 2. A new draft invalidates location links that no longer resolve. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.

Check 3. Not applicable without a reason remains unresolved. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.

Repeat the checks after adding another source record or changing the presentation. A working first example does not prove every record is handled correctly. Pay attention to retained selections, stale derived values, and unexplained changes in the number of displayed records. For specification completeness checker work, the reviewer must be able to tell whether a difference comes from new evidence, an edited rule, or merely a changed view.

Maintain the reviewed version

Keep a version label, source cutoff, and short change record with the finished specification completeness checker. Record who approved the rules and which demonstration cases were reviewed. When the source package changes, preserve record IDs and revisit the checks affected by the change. Do not treat yesterday's verified result as evidence that today's replacement input is complete.

Before handing the output to another person, review its audience and the material it contains. Use a sanitized demonstration for general feedback when the real source package is confidential. Explain whether changes are saved, whether the output is a preview, and which source remains authoritative. If persistence or sharing is required, verify that behavior in the actual account and intended environment instead of assuming it from a successful preview.

Frequently asked questions

Sources and related reading

Consult the current primary references for account-specific availability and controls: Current Claude artifact documentation, Claude sharing documentation. The schema, examples, prompts, and review checks here are editorial recommendations rather than documented built-in features.

For broader context, read the related Claude workflow guide.