doc-naming

Validate SDD document and element IDs against unified naming standards.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces unified ID naming standards and threshold naming rules across all SDD documentation artifacts to ensure consistency and discoverability.

Core Features & Use Cases

  • Validate document IDs and filenames against universal patterns
  • Detect legacy or placeholder identifiers and suggest corrections
  • Support cross-artifact discovery through standardized IDs

Quick Start

Validate a BRD/PRD/SYS document against the universal TYPE-NN naming convention.

Frequently Asked Questions about doc-naming

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

FAQPage Schema
How do I validate document ID naming conventions across SDD artifacts?

Document ID validation enforces unified naming standards across SDD artifacts like BRD, PRD, and SPEC files. The Skill applies regex-based rules to check TYPE-NN document IDs and TYPE.NN.TT.SS element IDs, ensuring uppercase codes, dash separators, and 2+ digit sequencing before artifact creation or editing.

What ID format does SDD documentation require?

SDD documentation uses two ID formats: TYPE-NN for document IDs and TYPE.NN.TT.SS for element IDs. Both enforce uppercase type codes, numeric sequencing with 2+ digits, and specific separators (dashes for documents, dots for elements) to maintain consistency across BRD, PRD, EARS, BDD, ADR, SYS, REQ, IMPL, CTR, SPEC, TASKS, and IPLAN artifacts.

Can this Skill detect legacy or placeholder ID patterns in my documentation?

Yes, the Skill detects removed and legacy ID patterns across all SDD artifacts and suggests corrections. It validates threshold tag syntax and identifies non-compliant element IDs, helping you standardize documentation and improve cross-artifact discoverability.

When should I enforce naming standards for SDD documentation?

Enforce naming standards before creating or editing any SDD documentation artifact to prevent inconsistency from the start. The Skill validates IDs during document creation and editing workflows, catching naming violations early across all SDD artifact types and maintaining unified standards throughout your documentation lifecycle.

Does this work with all SDD document types?

Yes, the Skill applies unified ID naming standards and threshold validation rules to all SDD artifact types: BRD, PRD, EARS, BDD, ADR, SYS, REQ, IMPL, CTR, SPEC, TASKS, and IPLAN. It enforces consistent TYPE-NN and TYPE.NN.TT.SS patterns regardless of document type.