writing-requirements-documents

Block anchors and wiki links enable traceable requirements in Obsidian. Structure your document with RFC 2119 keywords (SHALL, SHOULD, MAY), assign ID formats like FR1 or NFR1 to requirements, add block anchors (^FR1) after each requirement, then link internally using [[#^FR1|FR1]] syntax for cross-document references and validation.

Link integrity across documents requires citation-manager validation as a final quality gate. After creating cross-document markdown links and internal wiki references, run citation-manager to detect broken anchors, missing block references, and malformed links before publishing your requirements.

Yes. Obsidian wiki links work for all requirement types—PRDs, functional and non-functional requirements, epics, user stories, and acceptance criteria. Use block anchors to tag each item, apply consistent ID formats (FR/NFR/AC), and cross-link them with [[#^ID|ID]] references to build traceability matrices within a single vault.

Structure your PRD by assigning unique block anchors to each requirement and acceptance criterion, then link them using wiki link syntax. Each FR gets ^FR1, each AC gets ^AC1. Link acceptance criteria back to their requirements with [[#^FR1|depends on FR1]], then validate all links with citation-manager before finalizing.

Citation-manager validation detects broken anchors, missing block references, and malformed markdown links. Run validation before publishing to catch dead references; the tool flags unlinked IDs and orphaned blocks, ensuring your traceability chain stays intact across all documents in your vault.

RFC 2119 keywords (SHALL, SHOULD, MAY, MUST NOT) enforce clarity on requirement enforcement. Using them is recommended to distinguish mandatory (SHALL) from optional (SHOULD) behavior, making acceptance criteria precise and traceable across cross-document links.