In the next 10 minutes you can go from a fresh reqmd install to a fully traced V-model spec tree, validated and exported. Work through the steps in order — lettered steps are optional detours.

The seven steps#

StepFolderWhat you’ll learn
0Installationgo install, build from source, or prebuilt binary
1Get startedScaffold a new project and run your first validation
1aCI integrationJSON reports, exit codes, GitHub Actions
2Trace your specBuild a four-level V-model with trace links
2aStatus & dispositionThe draft/approved lifecycle and deferred/rejected workflow
2bVersion pinsPin traces to a specific upstream version; detect when stale
2cRepinBulk-update ~N version pins with reqmd repin --yes
3ExportCSV, HTML, and graph export formats
3aLive previewreqmd serve with live-reloading HTML
3bBaseline diffCompare requirements between two git tags
4Custom templatesDefine your own schema with a custom reqmd init preset
5Verification results (CTRF)Load automated test results and run outcome-gated checks
6Review documentationLoad manual review, inspection, and analysis results

Suggested paths#

New users: 00010203040506

CI/automation focus: 000101a0203b05

Status & lifecycle focus: 00010202a02b0506

Prerequisites#

Build the reqmd binary:

go build -o reqmd ./cmd/reqmd

Each step’s page shows the exact commands to run. Paths are relative to the project root. The full source for every step lives in the quickstart/ directory of the repo.

Beyond the spec itself: the companion reqmd-import tool extracts requirement IDs from Go and Python source via tree-sitter. After you’ve written the spec for a feature, run reqmd-import extract and the implementation gets IDs in the same namespace — closing the loop from spec to code.