documentation-criteria

Defines criteria and templates for technical documents like PRDs and ADRs.

Updated Feb 16, 2026

Search Tags:#templates #documentation #adr #design document #prd #work plan

Ready to run

npx skills add https://github.com/skiluo/vibe-springboot-scaffold --skill documentation-criteria-skiluo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: documentation-criteria
Source: https://github.com/skiluo/vibe-springboot-scaffold/tree/main/.qoder/skills/documentation-criteria
Command: npx skills add https://github.com/skiluo/vibe-springboot-scaffold --skill documentation-criteria-skiluo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides clear guidelines and templates for creating essential technical documentation, ensuring consistency, quality, and adherence to project standards. It helps determine which documents are required based on project changes and offers standardized templates for PRDs, ADRs, Design Docs, and Work Plans.

Core Features & Use Cases

Documentation Requirement Guidance: Understand when to create PRDs, ADRs, Design Docs, and Work Plans based on project scope and complexity.
Template Provision: Access standardized templates for various technical documents, ensuring all necessary sections are covered.
Use Case: When starting a new feature that involves significant architectural changes, this Skill can guide you to create an ADR, followed by a Design Doc and Work Plan, providing the specific templates for each.

Quick Start

Use the documentation-criteria skill to understand the requirements for creating an Architecture Decision Record.

Frequently Asked Questions about documentation-criteria

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

When do I need to create an Architecture Decision Record for my project?▼

An Architecture Decision Record is required when project changes involve contract system modifications, data flow changes, or architectural shifts. Triggers for ADR creation ensure significant structural modifications are formally documented and reviewed.

How do I standardize technical documentation like PRDs and design docs?▼

Standardize technical documentation by applying predefined criteria and templates for Product Requirements Documents, Architecture Decision Records, Design Documents, and Work Plans. This ensures all necessary sections are covered and project standards are consistently met.

What is the best way to decide which technical documents are required for a new feature?▼

Use a decision matrix based on project scope and complexity to determine required technical documents. This matrix evaluates project conditions to specify whether a PRD, ADR, Design Doc, or Work Plan is needed for the new feature.

What sections should be included in a Product Requirements Document?▼

A Product Requirements Document requires a standardized structure and content as specified by documentation criteria. Using provided templates ensures all necessary sections for defining product requirements and project standards are consistently covered.

Do I need a Work Plan if I already have a Design Document?▼

A Work Plan is often required alongside a Design Document for features involving significant architectural changes. The documentation criteria outline specific project conditions that trigger the need for both documents to ensure proper execution planning.