What is the recommended document creation order?

For new features, the standard order is PRD, followed by an ADR (if required), then the Design Doc, and finally the Work Plan.

Does this skill include visual documentation tools?

Yes, it defines specific Mermaid diagram requirements for each document type, such as user journey diagrams for PRDs and architecture diagrams for Design Docs.

When is an ADR required by this skill?

An ADR is mandatory for changes involving 6+ files, contract system changes (like 3+ levels of nesting), data flow modifications, or when introducing new external dependencies.

How does this skill handle implementation planning?

It provides a Work Plan template divided into four mandatory phases: Foundation, Core Feature, Integration, and a required Quality Assurance phase.

Technical Documentation Criteria

Name: Technical Documentation Criteria
Author: Tahir-yamin

byTahir-yamin

•

学習とドキュメンテーション

Enforces standardized requirements and templates for PRDs, ADRs, Design Docs, and Work Plans to ensure architectural consistency.

This skill provides a structured framework for technical documentation within the Claude Code environment, ensuring that every engineering decision is well-documented and architecturally sound. It implements a rigorous decision matrix that automatically determines when specific documents—such as Architecture Decision Records (ADRs) or Product Requirements Documents (PRDs)—are necessary based on code complexity, file count, and data flow changes. By leveraging standardized templates and clear separation of concerns, this skill helps development teams maintain high-quality technical records, reduce tribal knowledge, and streamline the transition from high-level planning to granular implementation tasks.

主な機能

01Automated document requirement matrix based on change scope and file count

02Standardized templates for PRD, ADR, Design Doc, and phased Work Plans

03Mandatory ADR triggers for contract changes and data flow modifications

04Integrated Mermaid diagram requirements for visual architectural clarity

05Phased implementation planning with mandatory Quality Assurance milestones

063 GitHub stars

ユースケース

01Drafting detailed Architecture Decision Records when introducing new libraries

02Determining necessary documentation for new features based on technical complexity

03Creating structured technical design documents with change impact mapping

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add tahir-yamin/dev-engineering-playbook documentation-criteria

For use in Claude.ai and ChatGPT

Download Skill