From aidoc-flow
Validates document IDs, 4-segment element IDs, threshold tags, and flags removed/legacy patterns in the SDD flow. Use before creating or editing any artifact.
How this skill is triggered — by the user, by Claude, or both
Slash command
/aidoc-flow:doc-namingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The naming authority for the 8-layer SDD flow. `doc-naming` validates document
The naming authority for the 8-layer SDD flow. doc-naming validates document
IDs, element IDs, threshold tags, and file names against
framework/governance/ID_NAMING_STANDARDS.md, and flags removed/legacy
patterns. It produces no artifacts — it is the declarative ID validator (the
framework ships no runtime code).
Layer: cross-cutting utility (applies to all 8 layers).
Use before creating or editing any artifact, to:
@threshold: tag, orDo NOT use for cross-document traceability (../doc-validator/SKILL.md,
../trace-check/SKILL.md) or single-document content review
(../doc-review/SKILL.md).
TYPE-NN^[A-Z]{2,8}-[0-9]{2,}$ — uppercase type, single dash, 2+ digit sequence (no
extra leading zeros beyond two: BRD-01, ADR-99, IPLAN-102). File name:
TYPE-NN_descriptive_slug.md.
TYPE.NN.SS.xxxx (4-segment)^[A-Z]+\.[0-9]{2,}\.[0-9]{2,}\.[a-f0-9]{4,8}$
| Segment | Meaning | Format |
|---|---|---|
| TYPE | Artifact prefix | BRD PRD EARS BDD ADR TDD |
| NN | Document number | 2+ digits |
| SS | Source section number | 2+ digits |
| xxxx | Content hash (SHA256, first 4 hex; extend to 8 on collision) | [a-f0-9]{4,8} |
Example: BRD.01.07.a7f3. Element IDs appear as markdown headings
(### BRD.01.07.a7f3: Title).
There are no numeric element-type codes — identity is the section + hash, not a fixed code.
| Layer | Reference form | Example |
|---|---|---|
| BRD, PRD, EARS, BDD, TDD | element (dotted) TYPE.NN.SS.xxxx | PRD.01.09.1dbc |
| ADR | both: document ADR-NN and element ADR.NN.SS.xxxx | ADR-05, ADR.05.03.e5b1 |
| SPEC, IPLAN | document (dash) TYPE-NN | SPEC-06, IPLAN-01 |
Traceability tags carry these refs: @brd: BRD.01.07.a7f3, @spec: SPEC-06,
@iplan: IPLAN-01.
@threshold: {TYPE}.{NN}.{key} where key is
category.subcategory.attribute[.qualifier]. Categories: perf timeout rate retry circuit alert cache pool queue batch. Doc reference is mandatory and
dot-separated — @threshold: PRD.035.timeout.partner.bridge (valid);
@threshold: timeout.partner.bridge (missing doc ref — invalid). Threshold
sources: BRD (business SLAs), PRD (product metrics), ADR (technical limits).
TYPE-00_* (indexes, templates, glossaries) — framework infrastructure;
skip element-ID and traceability checks.TYPE-REF-NN_{slug}.md (BRD/ADR only, via ../doc-ref/SKILL.md) —
free-format reference targets; no element IDs, no quality gates.Migrate every match to TYPE.NN.SS.xxxx (or a dash doc ref for SPEC/IPLAN):
| Removed | Applies to |
|---|---|
AC-XXX, FR-XXX, BC-XXX, BA-XXX, QA-XXX, BO-XXX, RISK-XXX, METRIC-XXX, Feature F-XXX | BRD, PRD |
Event-XXX, State-XXX | EARS |
DEC-XXX, ALT-XXX, CON-XXX | ADR |
3-segment TYPE.NN.xxxx | all element layers |
Detect with grep, e.g. grep -E "(AC|FR|BC|BA|QA|BO|NFR|RISK|METRIC)(-[A-Za-z0-9]+)*-[0-9]+" file.md
(the optional (-[A-Za-z0-9]+)* catches compound forms like FR-CICD-001).
Migration: derive TYPE/NN from the file name, SS from the source section,
xxxx from the element content hash; replace all occurrences and re-verify.
Date/time fields (frontmatter last_updated, created_date; review_date,
fix_date, approval_date, decision_date) use
YYYY-MM-DDTHH:MM:SS (optionally Z or ±HH:MM), enabling same-day drift
detection. Date-only values are deprecated.
TYPE-NN; file name is TYPE-NN_slug.md.TYPE.NN.SS.xxxx with a 4–8 hex hash, unique
within the document; SPEC/IPLAN use dash doc refs.@threshold: tags include the doc reference and an approved category.@brd: … @tdd:) are correct and targets exist.framework/governance/ID_NAMING_STANDARDS.mdframework/governance/THRESHOLD_NAMING_RULES.mdframework/registry/LAYER_REGISTRY.yamlframework/layers/NN_<X>/../doc-validator/SKILL.md · ../trace-check/SKILL.md../doc-flow/SKILL.md../charts-flow/SKILL.mdnpx claudepluginhub vladm3105/aidoc-flow-framework --plugin aidoc-flowProvides real-time quality guidance during SDD artifact creation: scores section completion, detects anti-patterns, validates cumulative tagging and naming, and generates a prioritized quality report.
Validates and registers new SoT IDs (BR-XXX, UJ-XXX, API-XXX, CFD-XXX) with format validation, uniqueness checks, cross-reference integrity, and confidence scoring.
Verifies every need ID in a sphinx-needs corpus matches its type's regex from .pharaoh/project/id-conventions.yaml, listing violations in JSON for quality gates.