tx-docs-specs

Docs-first spec management automates patching PRDs and design docs to keep documentation aligned with implementation. It handles creation, patching, and linting to enforce drift checks and doc coverage across your repository.

Docs-first spec tracing maps discovered invariants to tests to enable end-to-end traceability. It links artifacts like PRDs and design decisions directly to test coverage, ensuring searchable index readiness.

Docs-first spec linting validates documentation for drift, coverage, and search index readiness across a repo. It is needed when managing PRDs, design docs, and invariants to ensure artifacts stay linked to tests and decisions.

Yes, docs-first spec workflows require the tx doc and tx spec tooling to operate. These tools handle creation, patching, linting, discovery, tracing, and completion of doc-driven workflows in Claude Code.

The best way to discover invariants is running discovery and status checks after creating a PRD or design doc. This establishes end-to-end traceability by mapping discovered invariants to tests and linking artifacts to decisions.

Documentation drifts when PRDs and design docs are patched manually without linting or coverage checks. Docs-first spec workflows solve this by enforcing drift checks, linking artifacts to tests, and validating searchable index readiness.