skills.rest
jcchikikomori
jcchikikomoriCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

documentation-criteria

Standardize documentation practices across PRD, ADR, UI Spec, and Work Plan workflows.

Updated Apr 19, 2026
Search Tags:#templates#documentation#PRD#governance#ADR#design-doc#work-plan
One-click install
npx skills add https://github.com/jcchikikomori/opencode-workflow --skill documentation-criteria-jcchikikomori
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: documentation-criteria
Source: https://github.com/jcchikikomori/opencode-workflow/tree/main/skills/documentation-criteria
Command: npx skills add https://github.com/jcchikikomori/opencode-workflow --skill documentation-criteria-jcchikikomori

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Establishes standardized criteria and templates to ensure consistent, high-quality documentation across PRD, ADR, Design Doc, UI Spec, and Work Plan workflows.

Core Features & Use Cases

  • Templates for PRD, ADR, UI Spec, Design Doc, and Work Plan to streamline documentation.
  • Clear decision criteria, diagram requirements, and QA checks to ensure traceability and compliance.
  • Use Case: When starting a new feature, generate a complete documentation package by applying the templates and templates map, ensuring alignment with stakeholders.

Quick Start

Create a PRD, ADR, and Design Doc using the provided templates to begin documenting the feature.

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 standardizing project documentation across PRD and ADR workflows?▼

Standardizing project documentation requires templates for PRD, ADR, Design Doc, UI Spec, and Work Plan workflows. These templates establish clear decision criteria, diagram requirements, and QA checks to ensure traceability and compliance across backend and frontend documentation.

How do I create a complete documentation package when starting a new feature?▼

To create a complete documentation package for a new feature, generate a PRD, ADR, and Design Doc using the provided templates. Applying the templates and templates map ensures alignment with stakeholders and satisfies verification criteria.

When do I need an ADR versus a Design Doc for my project?▼

An ADR is needed to document architectural decisions and governance criteria, while a Design Doc details the technical design. Both use standardized templates to maintain consistent, high-quality documentation across different project workflows.

Can I use these documentation templates for both frontend and backend specifications?▼

Yes, the documentation templates apply to creating, reviewing, and maintaining both backend and frontend documentation. They include specific UI Spec templates for frontend work and PRD or Design Doc templates for broader backend and frontend specifications.

What's the best way to ensure my PRD meets diagram requirements and verification criteria?▼

The best way to ensure a PRD meets diagram requirements is to apply the standardized templates, which define specific diagram rules, template usage guidelines, and verification criteria needed to pass QA checks and maintain compliance.

Related Skills

Explore More Content & Communication Skills→
clovernguyen1010-ship-itclovernguyen1010-ship-it

bmad-agent-pm

Guide user interviews and requirements discovery to draft PRDs.

Community
Intermediate
darsoohoodarsoohoo

documentation-criteria

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

Community
Advanced
nseluganseluga

domain-modeling

Collaboratively define and standardize project domain terminology and record architectural decisions.

Community
Advanced
VincentChong123VincentChong123

learn

Distill ad-hoc workflows and documentation into structured Markdown skill units.

Community
Intermediate