CtrlK
BlogDocsLog inGet started
Tessl Logo

recipe-update-doc

Update existing design documents (Design Doc / PRD / ADR) with review

64

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

100%

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

The body is an exemplary orchestration guide: lean, highly actionable with executable commands and copy-paste subagent prompts, a clearly sequenced workflow with explicit validation checkpoints and feedback loops, and well-signaled one-level-deep cross-references. No bundle files exist, so structure rests entirely on the well-organized body.

DimensionReasoningScore

Conciseness

The body is dense and operational (tables, decision flows, structured subagent prompts) with no padding of concepts Claude already knows; minimal framing and every section earns its place, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

Provides executable bash commands (e.g., 'ls docs/design/*.md ...') and copy-paste-ready subagent invocation prompts with structured fields and clear decision tables, matching the 'fully executable; copy-paste ready' anchor.

3 / 3

Workflow Clarity

Defines a clear 6-step sequence with explicit [Stop] validation checkpoints, feedback loops (review -> revise -> retry, max 2 iterations), an error-handling table, and a completion checklist, matching the 'clear sequence with explicit validation steps; feedback loops; checklists' anchor.

3 / 3

Progressive Disclosure

Well-organized into clearly labeled sections with one-level-deep, clearly signaled cross-references to other skills (e.g., 'see subagents-orchestration-guide skill'); no nested/deep reference chains and no monolithic wall of text, matching the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

12

/

12

Passed

Description

50%

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

The description clearly states what the skill does and names the concrete document types it handles, but it omits any explicit trigger/when guidance and does not enumerate multiple distinct actions. It is competent but not exemplary.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when updating an existing Design Doc, PRD, or ADR after review feedback, spec changes, or bug-fix findings.'

Enumerate concrete actions beyond 'update' (e.g., 'revise, clarify, supersede, and re-review') to lift specificity to the top anchor.

Include common trigger variations (e.g., 'design doc', 'product requirements document', 'architecture decision record') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ("design documents") and concrete subtypes ("Design Doc / PRD / ADR") plus the action ("update ... with review"), but does not enumerate multiple distinct actions, matching the 'names domain and some actions, but not comprehensive' anchor.

2 / 3

Completeness

Clearly answers 'what' (update existing design docs with review) but provides no 'when'/trigger guidance; per guidelines a missing 'Use when...' clause caps completeness at 2.

2 / 3

Trigger Term Quality

Includes natural terms users would say ("Design Doc", "PRD", "ADR") but lacks a 'Use when...' clause and common variations, matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The niche (updating existing design docs with review) is fairly specific but could still overlap with document-creation or review skills and lacks explicit distinct triggers, matching the 'somewhat specific but could still overlap' anchor.

2 / 3

Total

8

/

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.