CtrlK
BlogDocsLog inGet started
Tessl Logo

documentation-criteria

Documentation creation criteria including PRD, ADR, Design Doc, and Work Plan requirements with templates. Use when creating or reviewing technical documents, or determining which documents are required.

70

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable reference that cleanly separates overview criteria from template files and gives concrete, measurable guidance for each document type. Its main weaknesses are repeated Scope phrasing that inflates tokens and an implicit rather than explicit validation loop in the creation workflow.

Suggestions

Consolidate the per-document 'Scope' statements (the repeated 'X belongs in A, Y in B' phrasing) into a single ownership matrix so each doc type's boundaries are stated once, reducing token cost.

Add explicit validation/feedback checkpoints to the Creation Process — e.g., after Creation, 'verify against the template checklist → fix gaps → re-validate before requesting Approval' — to give the workflow a clear retry loop.

DimensionReasoningScore

Conciseness

The body is information-dense and does not explain concepts Claude already knows, but the per-document 'Scope: ... belongs in X, ... in Y' statements are restated for every doc type and could be consolidated, so it is mostly efficient with room to tighten.

2 / 3

Actionability

Provides concrete, specific guidance throughout — measurable conditions (numeric targets, AC-001 IDs, minimum 3 options), naming conventions, storage paths, a creation decision matrix, and linked templates — so Claude knows exactly what each document must contain.

3 / 3

Workflow Clarity

The Creation Process lists a clear 1–4 sequence with an Approval gate, but validation checkpoints are implicit rather than explicit validate→fix→retry loops, matching the 'sequence present but checkpoints missing' anchor.

2 / 3

Progressive Disclosure

SKILL.md serves as an overview while detailed templates are split into references/ (all six referenced files verified to exist), one level deep and clearly signaled via markdown links in the Templates list and Storage Locations table.

3 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-formed description that names a clear niche, lists concrete capabilities, and provides an explicit 'Use when' trigger in third-person voice. It answers both what the skill does and when to invoke it without padding.

DimensionReasoningScore

Specificity

Lists concrete actions ('creating or reviewing technical documents', 'determining which documents are required') alongside specific artifact types (PRD, ADR, Design Doc, Work Plan) and templates, matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly states what the skill provides ('Documentation creation criteria ... with templates') and an explicit 'Use when creating or reviewing technical documents, or determining which documents are required' trigger, answering both what and when.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — 'technical documents', 'PRD', 'ADR', 'Design Doc', 'Work Plan' — giving good keyword coverage rather than generic jargon.

3 / 3

Distinctiveness Conflict Risk

The documentation-creation niche anchored by specific doc-type triggers (PRD/ADR/Design Doc/Work Plan) is clearly distinguishable from other skills and uses third-person voice, making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
shinpr/claude-code-workflows
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.