Skip to content

Guides

How complete is this feature against the spec?

Use Driver to turn a specification review into a requirement-by-requirement comparison with code and tests. Paste the numbered requirements, identify a file in the connected codebase, or provide a page accessible through a documentation connection configured by support.

  1. Name the intended release and select its codebase branch or supply the relevant source changes. Include the specification’s date or revision so Driver compares against the agreed requirements.
  2. Ask: “Compare this SSO specification with the selected branch. For each requirement, give its ID, implemented/partial/not found status, supporting code, relevant tests, feature gates, and the acceptance check still needed. Mark ambiguous requirements separately.”
  3. Open the cited code and tests. For a partial requirement, ask which specific behavior is present and which is missing. An implementation with no acceptance test is a different gap from an absent implementation.
  4. Ask the engineering owner to confirm deployment and organization-specific settings. Add that evidence to the review before marking a requirement available to customers.
  5. Copy missing behavior, ambiguous requirements, and unrun acceptance checks into the release issue with an owner for each. Repeat the comparison when the candidate or specification changes.

The resulting table is a release-review checklist: it shows what the code supports, what has been tested, and what still needs confirmation before release.