reverse-document

Generate design or architecture documents from existing implementation. Works backwards from code/prototypes to create missing planning docs.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/reverse-document/SKILL.md

Quality

Content

62%

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

The body lays out a clear, well-checkpointed workflow but is verbose with redundant restatements and references template files that do not exist in the bundle, weakening actionability and progressive disclosure.

Suggestions

Provide the referenced templates as actual files under a templates/ directory, or inline their structure so the references resolve.

Collapse the Phase 1-8, Collaborative Protocol, and Example Session sections into a single sequenced workflow to remove redundancy.

Replace bracketed-placeholder prompt scaffolds with at least one concrete filled-in example so the guidance is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept filler, but the workflow is restated three times (Phase 1-8, the Collaborative Protocol list, and the Example Session) and could be tightened significantly.	2 / 3
Actionability	Provides concrete template filenames, output paths, and prompt scaffolds, but the referenced templates do not exist as bundle files and the examples are heavy on bracketed placeholders rather than concrete content.	2 / 3
Workflow Clarity	The eight-phase sequence is clearly ordered with explicit checkpoints ('Wait for user to clarify', 'Wait for approval') and approval/decline verdicts, giving a clear feedback loop.	3 / 3
Progressive Disclosure	Sections are reasonably well-organized by headers, but the document is a monolithic ~250-line body and references templates (e.g. templates/design-doc-from-implementation.md) that are not present in any bundle directory.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 conveys concrete capabilities and occupies a distinct niche, but it lacks an explicit trigger clause and misses several natural user phrases, limiting trigger quality and completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when you built a feature without a design doc, inherited undocumented code, or need to formalize a prototype.'

Incorporate natural trigger terms users would actually say, such as 'design doc', 'GDD', 'ADR', or 'document this code'.

Tighten 'design or architecture documents' toward user-familiar phrasing like 'design docs and ADRs' to improve trigger recognizability.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Generate design or architecture documents from existing implementation" and "Works backwards from code/prototypes to create missing planning docs" — rather than vague language.	3 / 3
Completeness	Clearly states what the skill does but provides no explicit "Use when..." trigger guidance, so the "when" is only implied — capping completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Contains relevant terms ("design documents", "architecture documents", "code/prototypes") but misses common natural variations a user would actually say such as "design doc", "ADR", or "document this code".	2 / 3
Distinctiveness Conflict Risk	The reverse-documentation niche ("Works backwards from code/prototypes") is distinct and unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: Donchitos/Claude-Code-Game-Studios
Path: .claude/skills/reverse-document/SKILL.md
Commit: 984023d

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.