The site explains the workflow and shows its own traceability, but the two things a new user operates — the tracer-spec CLI and the seven workflow skills — are documented only in README.md and the SKILL.md files, not in the site. The existing pages also violate the repo’s own Diátaxis rule (one page = one mode): getting-started.adoc links out to Reference, workflow/overview.adoc mixes explanation with instructions, and workflow/authoring.adoc duplicates the guidance/ templates. A seventh skill, tspec-track, was added without touching the README, which still says six.

A complete Diátaxis site: how-to/ (scaffold a project, drive the seven-skill workflow), reference/ (CLI, skills catalog, roles, config), and explanation/ (workflow rationale, traceability). The mixed-mode pages are re-homed — workflow/overview.adoc becomes explanation/workflow.adoc, workflow/authoring.adoc is folded into reference/roles.adoc — and the tutorial’s out-links are removed. guidance/change.adoc and guidance/decision.adoc stay in place because traceability.yml roleGuidance points at them. The README is corrected to name all seven skills. use-cases/ and design/ remain, empty, for growth-role documentation.

Populating use-cases/ and design/ with growth-role content. Splitting the workflow how-to into per-skill pages. Documenting the full antora-tracer CLI beyond validate (linked out to its own reference). Rewriting item content under changes/, requirements/, or decisions/.