Agent skill

Documentation Criteria

by shinpr in shinpr/ai-coding-project-boilerplate

Determines which PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires and where each is stored.

MITAuto-check passedDevelopment

Install Documentation Criteria

skills CLI

$ npx skills add shinpr/ai-coding-project-boilerplate --skill documentation-criteria -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install shinpr/ai-coding-project-boilerplate documentation-criteria --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/shinpr/ai-coding-project-boilerplate.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills-en/documentation-criteria .claude/skills/documentation-criteria && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "documentation-criteria" agent skill from https://github.com/shinpr/ai-coding-project-boilerplate/tree/main/.claude/skills-en/documentation-criteria into .claude/skills/documentation-criteria/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-criteria", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/shinpr/ai-coding-project-boilerplate/tree/main/.claude/skills-en/documentation-criteria

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add shinpr/ai-coding-project-boilerplate --skill documentation-criteria -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install shinpr/ai-coding-project-boilerplate documentation-criteria --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/shinpr/ai-coding-project-boilerplate.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills-en/documentation-criteria .agents/skills/documentation-criteria && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "documentation-criteria" agent skill from https://github.com/shinpr/ai-coding-project-boilerplate/tree/main/.claude/skills-en/documentation-criteria into .agents/skills/documentation-criteria/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-criteria", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add shinpr/ai-coding-project-boilerplate --skill documentation-criteria -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install shinpr/ai-coding-project-boilerplate documentation-criteria --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/shinpr/ai-coding-project-boilerplate.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills-en/documentation-criteria .cursor/skills/documentation-criteria && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "documentation-criteria" agent skill from https://github.com/shinpr/ai-coding-project-boilerplate/tree/main/.claude/skills-en/documentation-criteria into .cursor/skills/documentation-criteria/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-criteria", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/shinpr/ai-coding-project-boilerplate.git --path .claude/skills-en/documentation-criteria

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add shinpr/ai-coding-project-boilerplate --skill documentation-criteria -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install shinpr/ai-coding-project-boilerplate documentation-criteria --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/shinpr/ai-coding-project-boilerplate.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills-en/documentation-criteria .gemini/skills/documentation-criteria && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "documentation-criteria" agent skill from https://github.com/shinpr/ai-coding-project-boilerplate/tree/main/.claude/skills-en/documentation-criteria into .gemini/skills/documentation-criteria/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-criteria", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install shinpr/ai-coding-project-boilerplate documentation-criteria

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add shinpr/ai-coding-project-boilerplate --skill documentation-criteria -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/shinpr/ai-coding-project-boilerplate.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills-en/documentation-criteria .github/skills/documentation-criteria && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "documentation-criteria" agent skill from https://github.com/shinpr/ai-coding-project-boilerplate/tree/main/.claude/skills-en/documentation-criteria into .github/skills/documentation-criteria/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-criteria", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add shinpr/ai-coding-project-boilerplate --skill documentation-criteria -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install shinpr/ai-coding-project-boilerplate documentation-criteria --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/shinpr/ai-coding-project-boilerplate.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills-en/documentation-criteria .opencode/skills/documentation-criteria && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "documentation-criteria" agent skill from https://github.com/shinpr/ai-coding-project-boilerplate/tree/main/.claude/skills-en/documentation-criteria into .opencode/skills/documentation-criteria/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-criteria", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: documentation-criteria
GitHub stars: 233
Token cost: ~1.6k tokens
SKILL.md length: 714 words
Files: 7 (incl. references)
Skills in repo: 41
Repo updated: Oct 4, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Determines which PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires and where each is stored.

Works in 2 steps: Choice requires judgment — confirmed… → Choice is durable — selecting among them…
Deciding documentation scope
SKILL.md covers What Each Document Fixes, Creation Decision Matrix, Structural Scale and ADR Decision Filters, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Documentation Criteria is an agent skill from shinpr/ai-coding-project-boilerplate. Determines which PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires and where each is stored. Use when deciding documentation scope or creating or reviewing a technical document.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/adr-template.md`, `references/design-template.md` and `references/plan-template.md`).

It sits in Development, covering Architecture decision records and PRD writing. The repository describes itself as: Agentic coding TypeScript boilerplate for Claude Code: sub-agent workflows with built-in quality checks and context engineering. The licence is MIT.

When your agent uses it

Deciding documentation scope
Reviewing a technical document

Example prompts

“Use the documentation-criteria skill to determine which PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires and where each is stored”
“/documentation-criteria”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

Choice requires judgment — confirmed requirements, accepted decisions, and representative repository evidence leave at least two credible…
Choice is durable — selecting among them materially changes responsibility, dependency direction, a shared contract, persistence…

What it can do on your machine

Read from SKILL.md and the folder at commit 56913a2. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Documentation Criteria loads about 1.6k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 714 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~53
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~12k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from shinpr/ai-coding-project-boilerplate at commit 56913a2, republished under its MIT licence (© shinpr). 714 words, ~1,564 tokens.

Download SKILL.mdSave it as .claude/skills/documentation-criteria/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.

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

Documentation Creation Criteria

This skill owns document routing: which durable decisions the change needs to record and where each document lives. Each template linked from Storage Locations owns the document's content and structural requirements.

What Each Document Fixes

PRD — Fixes the business outcome, current requirements, exclusions, and acceptance criteria that later work traces to. Its AC IDs are stable traceability keys for design and verification. Implementation design belongs in the Design Doc, technical option selection in an ADR, and task order in the Work Plan
ADR — Records one durable technical choice and the materially distinct options it beat, allowing later work to distinguish an accepted decision from an incidental implementation. Accepted records the currently selected means, not an obligation to retain it: when later evidence supports a smaller sufficient choice, update or supersede the ADR while the confirmed outcome, desired-future requirements, and non-goals remain true. Complete implementation design belongs in the Design Doc
UI Spec — Records screen structure, transitions, component and state contracts, interactions, and visual acceptance before implementation. Create one only while those decisions remain open; reuse an approved UI Spec or proceed to the Design Doc when representative repository evidence already determines them
Design Doc — Records the complete implementation design for the confirmed scope: responsibilities, flows, contracts, change impact, and verification boundaries. Implementation treats it as the primary technical baseline, so implementation does not silently invent missing How. When repository evidence invalidates technical How while confirmed outcome, desired-future requirements, and non-goals remain true, correct the implementation and the affected technical artifact through their owning workflow without reopening product requirements
Work Plan — Fixes dependency order, task boundaries, executable verification, and the earliest useful proof point. It references design details instead of reproducing them
Task File — Carries one executable Work Plan outcome, its governing sources, investigation starting points, write responsibility, and observable verification into implementation

Creation Decision Matrix

Structural Scale	Base Documents	Creation Order
Small	None	Direct implementation
Medium	Design Doc, Work Plan	Design Doc -> Work Plan
Large	PRD, Design Doc, Work Plan	PRD -> Design Doc -> Work Plan

Add a UI Spec before the Design Doc for frontend/fullstack work when its decisions remain open. Complete any qualifying ADR batch before the Design Doc. A qualifying ADR raises the scale to Medium at minimum.

For a Large change, satisfy the PRD requirement by creating a new PRD, updating the relevant PRD, or creating a reverse PRD when no current product document exists. At any scale, update an existing PRD when the product scope changes.

Show full SKILL.md (301 more words)Show less

Structural Scale

Classify decision burden rather than repository layout. File count is supporting evidence only.

Scale	Decision burden
Small	One coherent outcome, one evident repository-supported implementation within one responsibility boundary, and no unresolved durable choice
Medium	One coherent outcome that coordinates a boundary or contains a potentially durable choice
Large	Multiple independently valuable outcomes that require separate design decisions

A cross-layer implementation can remain Medium when it serves one coherent outcome.

ADR Decision Filters

Apply the Choice filter, then the Durability filter, to each technical topic inside the confirmed implementation scope. Check accepted ADRs before creating another record.

Choice requires judgment — confirmed requirements, accepted decisions, and representative repository evidence leave at least two credible, materially distinct options.
Choice is durable — selecting among them materially changes responsibility, dependency direction, a shared contract, persistence, technology, reversibility, or lifecycle cost that future work must preserve or understand.

Create one ADR for each topic that passes both filters and review the complete batch together. Group choices that must be selected or reconsidered together; separate independently revisitable decisions. Local implementation details and other cheaply reversible choices belong in the Design Doc.

Storage Locations

Document	Path	Naming Convention	Template
PRD	`docs/prd/`	`[feature-name]-prd.md`	prd-template.md
ADR	`docs/adr/`	`ADR-[4-digits]-[title].md`	adr-template.md
UI Spec	`docs/ui-spec/`	`[feature-name]-ui-spec.md`	ui-spec-template.md
UI Spec Assets	`docs/ui-spec/assets/{feature-name}/`	Prototype code files	-
Design Doc	`docs/design/`	`[feature-name]-design.md`	design-template.md
Work Plan	`docs/plans/`	`YYYYMMDD-{type}-{description}.md`	plan-template.md
Task File	`docs/plans/tasks/`	`{plan-name}-task-{NN}.md` (backend-only plan); `{plan-name}-backend-task-{NN}.md` (backend in a mixed-layer plan); `{plan-name}-frontend-task-{NN}.md` (frontend)	task-template.md

Every placeholder substituted into a generated directory or file name must be a lowercase ASCII kebab-case slug. Convert non-ASCII source text to that form before constructing the path.

Work Plans are excluded by .gitignore.

References

Each template defines its document's content, status rules, required evidence, optional diagrams, and completion checks. Load only the template for the document being created or reviewed.

Files

SKILL.md and 6 other files (references) in .claude/skills-en/documentation-criteria of shinpr/ai-coding-project-boilerplate.

SKILL.md
references/adr-template.md
references/design-template.md
references/plan-template.md
references/prd-template.md
references/task-template.md
references/ui-spec-template.md

Open the folder on GitHubat commit 56913a2

Compare with similar skills

Documentation Criteria next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Documentation Criteria compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Documentation Criteria this skillshinpr/ai-coding-project-boilerplate	233	—	~1.6k	Automated safety check: Pass	MIT	5 days ago
Cabloy Spec Generationcabloy/cabloy	982	—	~3.2k	Automated safety check: Notes	MIT	today
Bmad Architectureaj-geddes/claude-code-bmad-skills	488	—	~1.9k	Automated safety check: Notes	Custom licence	3 mo ago
Vibe CodingOfficeDev/microsoft-365-agents-toolkit	781	—	~5.5k	Automated safety check: Pass	Custom licence	today
Documentation Criteriashinpr/claude-code-workflows	693	—	~1.9k	Automated safety check: Pass	MIT	8 days ago
Ad ReviewCorridorTech/PoseCap	224	—	~2.4k	Automated safety check: Notes	Apache-2.0	2 days ago

Similar skills

Cabloy Spec Generation
cabloy/cabloy
A skill your agent uses to create or maintain Cabloy suite specifications under repo-specs, including PRD, SRS, PDP/WBS, acceptance planning, progress, and suite ADRs.
982 GitHub stars~3.2k tokensUpdated today
DevelopmentAuto-check: notes
Bmad Architecture
aj-geddes/claude-code-bmad-skills
Solutioning skill (Winston, the Architect). An agent skill from aj-geddes/claude-code-bmad-skills.
488 GitHub stars~1.9k tokensUpdated 3 mo ago
DevelopmentAuto-check: notes
Vibe Coding
OfficeDev/microsoft-365-agents-toolkit
End-to-end workflow for agent-driven changes that add or modify behavior in the toolkit packages.
781 GitHub stars~5.5k tokensUpdated today
DevelopmentAuto-check passed
Documentation Criteria
shinpr/claude-code-workflows
Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored.
693 GitHub stars~1.9k tokensUpdated 8 days ago
DevelopmentAuto-check passed
Ad Review
CorridorTech/PoseCap
Two-axis fresh-context code review per WORKFLOW §10. An agent skill from CorridorTech/PoseCap.
224 GitHub stars~2.4k tokensUpdated 2 days ago
DevelopmentAuto-check: notes
Squid Plan
iusztinpaul/squid
Turn a raw feature spec into an approved Tasks Plan — grill the spec, have the Product Architect groom draft tasks (+ optional ADR and glossary additions), then run ONE human gate that decides…
203 GitHub stars~2.6k tokensUpdated 1 mo ago
DevelopmentAuto-check passed

Questions about Documentation Criteria

What does Documentation Criteria do?

Determines which PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires and where each is stored. Documentation Criteria is an agent skill from shinpr/ai-coding-project-boilerplate. Determines which PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires and where each is stored.

When should I use Documentation Criteria?

Documentation Criteria fits situations like: deciding documentation scope; reviewing a technical document.

How do I install Documentation Criteria in Claude Code?

Run `npx skills add shinpr/ai-coding-project-boilerplate --skill documentation-criteria -a claude-code`. Or copy the skill folder (.claude/skills-en/documentation-criteria in shinpr/ai-coding-project-boilerplate) into .claude/skills/documentation-criteria in your project. Claude Code loads it when a task matches its description.

How do I install Documentation Criteria in Codex?

Run `npx skills add shinpr/ai-coding-project-boilerplate --skill documentation-criteria -a codex`. Or copy the skill folder (.claude/skills-en/documentation-criteria in shinpr/ai-coding-project-boilerplate) into .agents/skills/documentation-criteria in your project. Codex loads it when a task matches its description.

Can I use Documentation Criteria in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add shinpr/ai-coding-project-boilerplate --skill documentation-criteria -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/documentation-criteria, .gemini/skills/documentation-criteria, .github/skills/documentation-criteria and .opencode/skills/documentation-criteria in your project.

What does Documentation Criteria need to run?

SKILL.md names no scripts, command-line tools or credentials: Documentation Criteria is instructions for the agent only.

Does Documentation Criteria access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Documentation Criteria safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Documentation Criteria use?

Documentation Criteria is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Documentation Criteria use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.

What are the alternatives to Documentation Criteria?

Skills that share tags, products or a category with Documentation Criteria: Cabloy Spec Generation (cabloy/cabloy, 982 stars), Bmad Architecture (aj-geddes/claude-code-bmad-skills, 488 stars), Vibe Coding (OfficeDev/microsoft-365-agents-toolkit, 781 stars) and Documentation Criteria (shinpr/claude-code-workflows, 693 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Documentation Criteria?

shinpr (a GitHub user) maintains it in shinpr/ai-coding-project-boilerplate, which has 233 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 4, 2026.

Source: shinpr/ai-coding-project-boilerplate on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Documentation Criteria

Install Documentation Criteria

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Documentation Creation Criteria

What Each Document Fixes

Creation Decision Matrix

Structural Scale

ADR Decision Filters

Storage Locations

References

Files

Compare with similar skills

Similar skills

Cabloy Spec Generation

Bmad Architecture

Vibe Coding