Load manual verification results (review, inspection, analysis, demonstration) recorded as markdown with a user-supplied schema.

What’s in this folder#

06-review-documentation/
  schema.yaml                    # schema for manual results
  design-review-results.md       # VR-001: design review for TEST-002 (pass)

Manual results format#

Manual results are markdown files with attr blocks, just like requirements — but the schema declares result-specific attributes:

# schema.yaml
x-reqmd:
  level: verify-results
required: [outcome, verifier, verified-at]
properties:
  outcome:
    type: string
    enum: [pass, fail, skipped, inconclusive]
  verifier:
    type: string
  evidence:
    type: string
  verified-at:
    type: string

Each result is a heading with an attr block:

## VR-001: Boot Sequence Design Review Result
```attr
status: approved
outcome: pass
verifier: "A. Reviewer"
evidence: minutes/2026-07-15-boot-review.md
verified-at: "2026-07-15"
trace: [TEST-002]

The `trace` attribute links the result to the measure it verifies.

## Scaffold a results directory

Use the built-in `results` preset:

```sh
reqmd init my-reviews/ --preset results --id-prefix VR

This creates schema.yaml + results.md with one example result.

Run checks with manual results#

reqmd check 02-trace-your-spec/ --results 06-review-documentation/

Combine automated + manual results#

reqmd check 02-trace-your-spec/ \
  --results 05-verification-results-ctrf/ \
  --results 06-review-documentation/

Both result sources are merged — if a measure has results from both CTRF and manual sources, the latest verified-at wins.

Export with manual verdicts#

reqmd export html 02-trace-your-spec/ \
  --results 06-review-documentation/ -o html-out/

That’s it#

You’ve worked through the full reqmd workflow:

  1. Scaffold a project
  2. Build a traced spec tree
  3. Export to CSV/HTML/graph
  4. Define custom templates
  5. Load automated test results (CTRF)
  6. Load manual review results

For the full spec, see the README and AGENTS.md.