documentation-criteria SKILL.md skillA

documentation-criteria from shinpr/claude-code-workflows is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add shinpr/claude-code-workflows/documentation-criteria@git:20261102.9387efe

Pins git:20261102.9387efe in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

shinpr/claude-code-workflows

Path

skills/documentation-criteria/SKILL.md

Versions recorded

10

Latest version

git:20261102.9387efe, committed Nov 2, 2026

First version recorded

Aug 6, 2026

Size

8,348 bytes

Repository stars

709

License

MIT

Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored. Use when deciding documentation scope, or when creating or reviewing a technical document.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Documentation Creation Criteria

This file holds the routing decision: which documents a change requires and where they live. What to write inside one is defined by its template, linked from Storage Locations.

## What Each Document Fixes

Each document fixes one class of decision that the repository alone cannot supply. An unfilled section becomes a guess made later by the consumer named below, with no record of what was assumed.

- **PRD** — Fixes the business outcome and the acceptance criteria later work traces to. Its AC IDs are the traceability keys that the Design Doc, UI Spec, and test selection reuse; without them each consumer re-derives requirements from prose and the link between a test and the value it protects is lost. Implementation details belong to the Design Doc, selection rationale to an ADR, phases and task breakdown to the Work Plan. Later design, review, and test selection treat its content as governing, so a precondition held outside the repository change, such as release execution or organizational approval, appears in it only when the user's wording raises it.
…

Read the whole file at its exact version.

How to install

mdr add shinpr/claude-code-workflows/documentation-criteria@sha256:85c335b978c906e6

[![mdr](https://markdownregistry.com/badge/art_yd4q65tah7chyfux.svg)](https://markdownregistry.com/a/art_yd4q65tah7chyfux)

Versions

The registry has recorded 10 versions of this file, between Aug 6, 2026 and Nov 2, 2026, about one every 10 days.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_yd4q65tah7chyfux
GET https://markdownregistry.com/api/v1/resolve?ref=shinpr/claude-code-workflows/documentation-criteria
GET https://markdownregistry.com/api/v1/blob/85c335b978c906e6a136fc10b4cb5e7f0bf57a72dbc7e38c676a8fc11916f37e

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from shinpr/claude-code-workflows

Every file in shinpr/claude-code-workflows

Other files named documentation-criteria

Browse by kind, by grade A, or by owner.