tx-docs-specs

Automate docs-first spec workflows including creation, linting, discovery, tracing, and completion via tx tooling.

6|3|Updated Jan 28, 2026

Search Tags:#workflow #documentation #traceability #docs #lint #specs #discover

Ready to run

npx skills add https://github.com/jamesaphoenix/tx --skill tx-docs-specs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tx-docs-specs
Source: https://github.com/jamesaphoenix/tx/tree/main/.claude/skills/tx-docs-specs
Command: npx skills add https://github.com/jamesaphoenix/tx --skill tx-docs-specs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Docs-first specs are essential for aligning design, PRD, and invariants, but teams often struggle to patch, lint, discover, and trace changes across docs and tests. This skill provides tooling to create, patch, lint, discover, trace, and complete docs-driven workflows in Claude Code using tx commands.

Core Features & Use Cases

Create and patch PRD/design docs to keep documentation in sync with implementation.
Discover invariants and map them to tests to enable end-to-end traceability.
Validate docs for drift, coverage, and index search readiness across the repo.

Quick Start

Create a new PRD or design doc, then run discovery and status checks to establish traceability.

Frequently Asked Questions about tx-docs-specs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I keep PRDs and design docs in sync with implementation changes?▼

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.

How do I trace invariants from design docs to tests?▼

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.

What is docs-first spec linting and when do I need it?▼

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.

Do I need the tx doc and tx spec tooling to use docs-first spec workflows?▼

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.

What's the best way to discover and map invariants in design docs?▼

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.

Why does documentation drift from implementation in spec-heavy projects?▼

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.