documentation-criteria

Create documentation templates and criteria for PRD, ADR, Design Doc, UI Spec, and Work Plan.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/darsoohoo/intake-bot --skill documentation-criteria-darsoohoo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-criteria
Source: https://github.com/darsoohoo/intake-bot/tree/main/.agents/skills/documentation-criteria
Command: npx skills add https://github.com/darsoohoo/intake-bot --skill documentation-criteria-darsoohoo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Documentation creation for PRD, ADR, Design Doc, UI Spec, and Work Plan is often inconsistent and hard to audit; this skill provides standard templates and decision criteria to streamline work and ensure compliance across artifacts.

Core Features & Use Cases

  • Standard templates for PRD, ADR, UI Spec, Design Doc, Plan, and Task files.
  • Creation decisions and mandatory ADR prerequisites help teams decide which docs to produce and in what order.
  • Use case: When kicking off a feature, generate a complete documentation pack following templates and review criteria.

Quick Start

Review the templates in references/ and apply the documented criteria to create and review project documentation.

Frequently Asked Questions about documentation-criteria

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

FAQPage Schema
What templates do I need for a complete feature documentation pack?

A complete feature documentation pack requires standard templates for PRD, ADR, Design Doc, UI Spec, and Work Plan. These templates ensure artifact consistency, simplify auditing, and enforce compliance across project documentation.

How do I decide the correct ordering for PRD, ADR, and Design Doc creation?

Decide document ordering by applying the mandatory ADR prerequisite map, which dictates creation decisions. This framework ensures traceability and quality by requiring specific architecture decision records before subsequent design artifacts.

When should I write an ADR instead of a Design Doc?

Write an ADR when you need to document mandatory architectural decisions and governance prerequisites before implementation. A Design Doc follows to outline the technical approach, relying on the ADR to provide validated context and traceability.

What's the best way to structure a UI Spec and Work Plan for traceability?

Structure your UI Spec and Work Plan using standard templates that map directly to PRD and ADR decisions. This ensures traceability across artifacts, linking implementation tasks and interface criteria back to approved product requirements.

How do I review project documentation for compliance and quality?

Review project documentation for compliance by applying documented creation criteria against standard templates. Check that mandatory ADR prerequisites are met and that artifact ordering enforces traceability from feature ideation through implementation.