doc-brd-validator

Validate BRD documents against Layer 1 schema standards.

16|3|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-brd-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-brd-validator
Source: https://github.com/vladm3105/aidoc-flow-framework/tree/main/.claude/skills/doc-brd-validator
Command: npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-brd-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates BRD documents against Layer 1 schema standards, ensuring metadata, structure, and traceability meet required guidelines before advancing in the SDD workflow.

Core Features & Use Cases

  • Validate Document Control, objectives, requirements, and traceability
  • Enforce BRD naming conventions and tag usage
  • Produce a validation report and recommended fixes

Quick Start

Validate a BRD document to ensure compliance with BRD schema requirements.

Frequently Asked Questions about doc-brd-validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a BRD document against schema standards?

BRD validation checks your document against Layer 1 schema standards, enforcing metadata integrity, required fields, section ordering, and content compliance. The Skill outputs a standardized validation report with errors, warnings, and remediation guidance to ensure your BRD meets traceability requirements before advancing in the workflow.

What does a BRD validation report include?

The validation report identifies schema violations across document control, objectives, requirements, and traceability sections. It includes error and warning classifications, PRD-Ready scoring, and specific remediation steps so you can systematically address compliance gaps.

Can I enforce BRD naming conventions and tag taxonomy during validation?

Yes. The Skill validates BRD naming conventions and enforces tag taxonomy compliance as part of schema validation, ensuring consistent metadata and structural standards across your document lifecycle.

When should I run BRD validation in my workflow?

Run validation on BRD artifacts created or modified before they advance in the SDD workflow. Validating early catches metadata and structure violations, reducing downstream rework and ensuring traceability continuity.

What happens if my BRD fails validation?

The validation report flags specific errors and warnings with recommended fixes. Address the violations according to Layer 1 schema standards, then re-validate to confirm compliance and achieve PRD-Ready status.

Does BRD validation check traceability across the document lifecycle?

Yes. Validation enforces traceability requirements across the BRD lifecycle, ensuring document control, objectives, and requirements maintain proper cross-references and metadata integrity throughout modification cycles.