Decompose BRD, PRD, and EARS inputs into atomic REQ v3.0 documents.
npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-req
Please help me install this Agent Skill. Skill: doc-req Source: https://github.com/vladm3105/aidoc-flow-framework/tree/main/.claude/skills/doc-req Command: npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-req
This Skill enables the decomposition of complex system requirements into atomic, implementation-ready REQ documents (Layer 7) using REQ v3.0 format, ensuring traceability and SPEC-readiness.
Use doc-req to create REQ-NN entries with 12-section REQ v3.0 structure and SPEC traceability.
High-intent search queries and answers about installing and using this skill.
Decompose requirements by breaking down BRD, PRD, EARS, or BDD artifacts into individual, implementation-ready REQ v3.0 documents using the 12-section framework. Each atomic requirement captures a single, testable behavior with acceptance criteria, interfaces, and data schemas to enable downstream SPEC creation and traceability.
REQ v3.0 is a standardized 12-section requirements format that structures atomic requirements for precision, traceability, and SPEC-readiness. Use it when converting high-level requirements into Layer-7 artifacts that must enforce compliance, link to upstream sources, and prepare for implementation and validation artifacts.
Structure each REQ v3.0 document to explicitly reference its upstream artifact (BRD, PRD, EARS, ADR, or SYS section). The Skill enforces traceability links and SPEC-readiness scoring, making validation and downstream integration auditable from source through implementation.
Yes. The Skill decomposes atomic requirements from multiple upstream formats—BRD, PRD, EARS, BDD, ADR, and SYS—into consistent REQ v3.0 structure. Source format differences are normalized into a unified Layer-7 requirements layer ready for SPEC and CTR artifact generation.
A requirement is SPEC-ready when it meets the REQ v3.0 12-section framework with clear acceptance criteria, defined interfaces, data schemas, quality attributes, and verifiable traceability to upstream sources. The Skill enforces SPEC-readiness scoring to validate each atomic requirement before downstream handoff.
Atomic REQ v3.0 documents feed downstream into SPEC (specification), CTR (contract), and IMPL (implementation) artifacts. Traceability links and SPEC-readiness scores enable validation, integration testing, and audit trails from requirements through delivery.
vladm3105Generate Layer-6 System Requirements documents with traceability to upstream artifacts.
vladm3105Convert completed SDD artifacts into machine-readable SPEC YAML documents.
aquariuscookValidate software requirements by assessing SMART acceptance criteria and generating traceability matrices.
vladm3105Validate cross-document traceability and integrity across SDD framework documents.
