harness-add-living-doc

To add a new living document to a Claude Code harness, the system scans CLAUDE.md and command files to preview diffs, then updates preflight, sync, verify, and audit sections to wire the doc into the full enforcement chain.

A Claude Code harness silently misses enforcement checks when newly created living documents are not manually wired into the existing preflight, sync, verify, and audit touchpoints across CLAUDE.md and command files.

You ensure a new PRD is synced and audited by scanning existing harness patterns in CLAUDE.md, previewing a diff-style plan for approval, and updating all preflight, sync, verify, and audit sections to maintain naming and formatting consistency.

Yes, you can preview configuration changes before adding a spec, as the system presents a comprehensive diff-style plan of all CLAUDE.md and command file edits for user approval prior to applying the enforcement wiring updates.

Adding living documents to an enforcement harness does not require manual markdown editing, as the system automatically scans existing doc family patterns, matches them, and updates all relevant command and configuration files directly.

Living document enforcement wiring in a Claude Code harness is the process of integrating PRDs, specs, or constraints into preflight reading, post-implementation sync, adversarial verification, and audit scope to maintain workflow governance.