Technical Documentation Criteria
Enforces standardized documentation workflows by providing templates and decision matrices for PRDs, ADRs, and technical design documents.
The Documentation Criteria skill provides a robust framework for managing the technical lifecycle of software projects within Claude Code. It automates the decision-making process for document creation—such as PRDs, ADRs, and Design Docs—based on the complexity and scope of code changes. By offering structured templates and clear criteria for architectural decisions, UI specifications, and work plans, this skill ensures that development remains documented, traceable, and aligned with industry best practices from initial requirement to final quality assurance.
Características Principales
01Integrated Mermaid diagram requirements for visual architecture and work plans.
02Automated document requirement detection based on file count and complexity.
03Traceability mapping between business requirements and technical implementation.
04Standardized templates for PRDs, ADRs, UI Specifications, and Design Documents.
05444 GitHub stars
06Mandatory ADR triggers for contract, data flow, or architectural changes.
Casos de Uso
01Planning a major new feature that requires architectural sign-off and stakeholder alignment.
02Generating structured work plans and task breakdowns for multi-step implementations.
03Documenting breaking changes in API contracts or complex data flow transitions.