TraceR

Use when editing, regenerating, interpreting, or verifying any of the project's spec documents (PVD, SDD, HLRs, LLRs, Test Plan, Traceability) or their generator inputs. doc/Project.xml is the SINGLE SOURCE OF TRUTH for the project's design, requirements, and verification — and the canonical store from which traceability (SDD→HLR→LLR→Test) is measured. doc/PVD.md is the hand-authored Product Vision Document that sits above the generated stack; the AI is expected to draft and fill in PVD content under the developer's direction, asking targeted questions when sections are thin or missing. USE FOR: any change to doc/PVD.md, doc/Project.xml, doc/SDD.md, doc/HLRs.md, doc/LLRs.md, doc/STP.md, doc/Traceability.md; drafting or revising the Product Vision Document; adding/removing/renumbering HLRs or LLRs; adding new tests under test/ that need traceability annotations; updating Project.xml schema; authoring new Jinja2 templates under tools/templates/; running tools/render_doc.py; verifying those spec edits with lint/

Use when working on a project that uses TraceR for requirements traceability. TraceR manages design, requirements, and verification through a single `doc/Project.xml` source of truth and generates linked specification documents (SDD, HLRs, LLRs, STP, Traceability). USE FOR: adding or editing HLRs, LLRs, tests, or SDD modules; rendering spec documents; running the linter; understanding the traceability chain (SDD→HLR→LLR→Test); writing tests that need traceability annotations; working with `Project.xml` structure; using the TraceR VS Code extension or CLI tools. DO NOT USE FOR: code changes unrelated to requirements or design; general build/CI troubleshooting unrelated to TraceR tooling.