docs-architect

An ADR should reference the governing PRD and HLD of the affected module, include title, version, status, and date, and state the structural decision explicitly. This Skill enforces that traceability chain and flags missing source artifacts instead of inventing them.

Apply explicit governance rules: mandatory metadata fields, repo naming conventions, and cross-references between PRD, HLD, ADR, plans, and reports. The Skill reviews documents against a checklist and corrects contradictions with AGENTS.md or approved ADRs.

A PRD must define scope clearly enough to drive implementation, with short functional sections, concrete references to related documents, and explicit risks and pending items. Aspirational filler text without operational utility is treated as an anti-pattern.

Escalate when a document implies approving a change to stack, boundaries, or security, when source artifacts conflict without clear document authority, or when critical missing information blocks a reliable output. The Skill marks these cases as escalation to the CTO.

Avoid long documents without operational use, duplicated reports instead of updating the living document, renaming files against repo conventions, describing unapproved architectures, and using documentation as a substitute for decisions that do not exist yet.