documentation-criteria

Standardize documentation by using comprehensive templates and decision matrices for PRD, ADR, Design Doc, and Work Plan. This Skill provides enforcement of required sections, acceptance criteria using EARS format, and storage conventions to ensure consistent creation and governance across your documentation lifecycle.

An ADR (Architecture Decision Record) documents specific architecture decisions and their rationale, while a design document details implementation specifications, data flows, and architecture diagrams. This Skill includes a creation decision matrix that automatically determines which documents are required based on project scale and complexity.

Generate a Product Requirements Document using standardized templates that structure user stories, acceptance criteria, and measurable success metrics. This Skill provides pre-built templates and phase alignment guidance to ensure PRDs include all required sections for consistent feature definition.

Yes, this Skill supports multi-file documentation projects with guidance for document sequencing, inclusion criteria, and phase alignment. It enforces structure across related documents—PRD, ADR, Design Doc, and Work Plan—enabling coordinated creation and review.

Without standardized structure, documentation becomes inconsistent, harder to review, and difficult to govern across projects. This Skill prevents those gaps by enforcing required sections, acceptance criteria, and storage conventions from the start.

Yes, this Skill is applicable to new feature additions, ADR-driven architecture decisions, and multi-file documentation projects. It provides decision matrices and templates tailored to both feature scope and architectural change contexts.