Does this skill provide templates for specific documents?

Yes, it includes standardized templates for PRDs, ADRs, Technical Design Docs, Work Plans, Task files, and UX Requirements Documents (UXRD).

What documentation is recommended for a small change of 3-5 files?

For changes affecting 3-5 files, a Design Document and a Work Plan are recommended to ensure clear implementation paths and verification procedures.

Are visual diagrams required in the documentation?

Yes, the skill specifies required Mermaid diagrams for different documents, such as User Journey diagrams for PRDs and Architecture diagrams for Design Docs.

When should I create an Architecture Decision Record (ADR)?

An ADR is required for contract system changes, data flow modifications, architectural shifts, external dependency changes, or managing complex logic involving 3+ states or 5+ asynchronous processes.

How does the skill handle implementation planning?

It enforces a 4-phase work plan consisting of Foundation, Core Feature, Integration, and a mandatory Quality Assurance phase to ensure all tests and acceptance criteria are met.

Documentation Standards & Criteria

Name: Documentation Standards & Criteria
Author: tundraray

bytundraray

•

Learning & Documentation

Standardizes technical documentation workflows by providing templates and decision criteria for PRDs, ADRs, and design documents.

This skill streamlines the software development lifecycle by enforcing consistent documentation standards within Claude Code. It helps developers determine exactly when and how to create Product Requirements Documents (PRDs), Architecture Decision Records (ADRs), Technical Design Docs, and Work Plans based on the scope and complexity of a change. By providing standardized templates and a clear creation decision matrix, it ensures that technical decisions are recorded, implementation paths are mapped, and quality assurance is integrated into every production-ready workflow.

Key Features

01Automated decision matrix for document creation based on file count and complexity

02Integrated Mermaid diagram requirements for visual technical documentation

03Mandatory ADR criteria for contract changes, data flow, and architecture shifts

04Standardized templates for PRDs, ADRs, Design Docs, and Work Plans

05Structured 4-phase implementation planning with built-in Quality Assurance

061 GitHub stars

Use Cases

01Generating detailed work plans with specific E2E verification steps and task breakdowns

02Recording architectural rationale when changing core system contracts or data flow logic

03Determining if a new feature requires a full PRD and Design Doc sequence based on complexity

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add tundraray/overture documentation-criteria

For use in Claude.ai and ChatGPT

Download Skill