requirements-graph

You create traceable requirements by structuring acceptance criteria as individual markdown files, using frontmatter tags like TRACES_TO to map relationships. This builds a traceable graph linking user stories, areas, and decisions.

Requirements traceability tracks links between artifacts like user stories and acceptance criteria. A graph approach models these as atomic nodes with frontmatter-driven edges, providing end-to-end visibility across complex documentation.

Organize user stories and acceptance criteria by creating a requirements root with area folders, then add acceptance criterion markdown files. Frontmatter tags enforce a standard schema connecting each node for traceability.

Yes, frontmatter links non-functional requirements (NFRs) to user stories. The schema enforces standard node types including nfr and user-story, allowing you to tag each file with relationship metadata.

The best way to structure complex requirements as atomic units is using a graph-based approach with markdown files. Each acceptance criterion becomes a file with frontmatter traces to other artifacts.

No external dependencies are required to manage requirements traceability with this approach. It relies on standard markdown files and frontmatter metadata to build the graph of requirements, areas, and decisions.