What are the upstream dependencies for doc-req?

The skill requires upstream artifacts from Layers 1 through 6, specifically BRD, PRD, EARS, BDD, ADR, and SYS documents, to maintain a valid traceability matrix.

What does the SPEC-Ready score measure?

The SPEC-Ready score measures the completion percentage of the 12 mandatory REQ v3.0 sections; a score of at least 90% is required for a requirement to be marked as 'Approved'.

How does the skill handle 'magic numbers'?

It uses the @threshold tag to reference a centralized threshold registry, ensuring quantitative values like latencies, rate limits, and retry policies are consistent and not hardcoded.

What is Layer 7 in the SDD workflow?

Layer 7 is the Atomic Requirements (REQ) phase where system-level requirements are decomposed into self-contained, measurable, and implementation-ready units.

Atomic Requirements Architect

Name: Atomic Requirements Architect
Author: vladm3105

byvladm3105

•

Learning & Documentation

Decomposes complex system requirements into atomic, implementation-ready Layer 7 artifacts using the REQ v3.0 format.

About

The doc-req skill is a specialized tool for the SDD (Software Design Document) workflow, specifically designed to handle Layer 7: Atomic Requirements. It transforms system-level requirements into granular, testable, and implementation-ready units using a rigorous 12-section REQ v3.0 template. This skill enforces high-quality standards through dual readiness scoring (SPEC-Ready and IMPL-Ready), requiring a 90% completion threshold before moving to code. By integrating with a centralized threshold registry to eliminate magic numbers and maintaining a cumulative traceability hierarchy from BRD to SYS, it ensures that every requirement is measurable, self-contained, and perfectly aligned with business and architectural goals.

Key Features

Calculates dual readiness scores (SPEC-Ready and IMPL-Ready) to gatekeep quality.
Standardizes element IDs using the REQ.NN.TT.SS dot-notation for precise referencing.
Integrates with the @threshold registry to prevent hardcoded magic numbers in specifications.
1 GitHub stars
Generates 12-section REQ v3.0 compliant documents with mandatory control fields.
Enforces cumulative traceability tagging across Layers 1-6 (BRD, PRD, EARS, BDD, ADR, SYS).

Use Cases

Establishing automated quality gates for documentation before the implementation phase.
Mapping complex business rules to specific data schemas and interface specifications.
Decomposing high-level system requirements (SYS) into granular units for developers.

About

Key Features

Calculates dual readiness scores (SPEC-Ready and IMPL-Ready) to gatekeep quality.
Standardizes element IDs using the REQ.NN.TT.SS dot-notation for precise referencing.
Integrates with the @threshold registry to prevent hardcoded magic numbers in specifications.
1 GitHub stars
Generates 12-section REQ v3.0 compliant documents with mandatory control fields.
Enforces cumulative traceability tagging across Layers 1-6 (BRD, PRD, EARS, BDD, ADR, SYS).

Use Cases

Establishing automated quality gates for documentation before the implementation phase.
Mapping complex business rules to specific data schemas and interface specifications.
Decomposing high-level system requirements (SYS) into granular units for developers.