← ClaudeAtlas

requirements-docslisted

Generate and iterate standard, versioned requirements documents per feature or module. Covers the BRD, FRD, SRD (System Requirements), a traceability matrix with implementation status (RTM) and an executive gap report. Each document has fixed sections and semantic versions (bump, revision row, history snapshot), with stable IDs traced BR → FR → SR → code/test evidence. Evidence is a hyperlink to source lines, never copied code, and Mermaid/UML diagrams are included. Works from code (via legacy-code-analysis), notes or upstream docs, in any language. Use it whenever someone asks to write, update, version, review or derive a BRD, FRD, SRD/SRS, functional or technical spec, traceability matrix, implementation status or gap analysis, or a new feature's requirements, even if they just say "requirements doc", "spec" or "how much of this is built".
YarlisAISolutions/yarlis-modernization · ★ 0 · Web & Frontend · score 75
Install: claude install-skill YarlisAISolutions/yarlis-modernization
# Requirements package: BRD → FRD → SRD → RTM → Gap report | Doc | File | Answers | Defines | |---|---|---|---| | Project context | `PROJECT-CONTEXT.md` | Facts every document starts from: owner, users, repo + commit, constraints | — | | BRD | `BRD.md` (21 sections) | Why, and what business outcome | BO, BR, RUL, ASM/CON/DEP, RSK | | FRD | `FRD.md` (17 sections) | What the solution does | UC, FR, SCR, BAT, RPT, INT, MSG | | SRD | `SRD.md` (23 sections) | How the system is built and constrained (System Requirements Document) | SR, NFR, IFR, DR, ADR | | RTM | `RTM.md` | Each requirement's trace, code/verification/deployment status and gap | rows for BR, RUL, FR, SR, NFR, IFR, DR | | Gap report | `GAP-REPORT.md` | Executive progress, gaps, blockers, next milestone | — | Templates in `assets/templates/` are the standard. Section numbers and titles are fixed, and `docver.py validate` checks them in order. A section that doesn't apply says `N/A: <reason>`. Never delete or renumber a section: that's what keeps every version and every project comparable. Tooling: `D=<skill-dir>/scripts/docver.py` (`<skill-dir>` = this skill's folder; `l2m docs …` runs the same script when the `@l2m/cli` package is installed). Default folder: `docs/requirements/`, with `history/` for snapshots. ## Layout: one document set per feature ``` docs/requirements/ PROJECT-CONTEXT.md once per repository (owner, users, repo URL + commit, constraints) INDEX.md generated by `docver