CtrlK
BlogDocsLog inGet started
Tessl Logo

architecture-decision

Document an architectural decision — record the decision and rationale, retain into Hindsight, and update CLAUDE.md if needed.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/architecture-decision/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

The body is a well-structured, actionable ADR workflow with concrete templates and explicit user-approval checkpoints; its main gaps are minor padding and the absence of an explicit error-recovery feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly lean templates and concrete steps, but the opener 'This command ensures decisions are properly recorded and available for future recall' and the top-of-file diagram-complexity blockquote are minor over-explanation that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready ADR template, exact markdown embed syntax, concrete `/devflow:render-diagram` invocation, and specific Hindsight retain fields (Title, Category, Content, Context) covering the common cases.

5 / 5

Workflow Clarity

Steps 1–6 are clearly sequenced with explicit approval checkpoints (step 3 review/approval, step 5 'Only update CLAUDE.md if the user approves', step 6 confirmation), but no explicit validate→fix→retry error-recovery loop exists.

4 / 5

Progressive Disclosure

Well-organized into Steps and Important sections with the ADR template inline and the render-diagram skill clearly signaled at one level deep, though the pre-Steps diagram-complexity blockquote is slightly awkward organizationally and no bundle files exist.

4 / 5

Total

17

/

20

Passed

Description

58%Weight 40%Scale 1-5

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 is third-person and names several concrete actions tied to a recognizable niche, but it lacks an explicit 'when to use' trigger clause and omits common synonyms like 'ADR' and 'tradeoffs' that a user would naturally invoke.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when the user records an architectural decision, writes an ADR, or commits to a design tradeoff.'

Include common synonyms such as 'ADR', 'design decision', and 'tradeoffs' so the description matches natural user phrasing.

Mention alternatives/tradeoffs as part of the documented rationale to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Quotes 'record the decision and rationale, retain into Hindsight, and update CLAUDE.md' — several specific concrete actions named, though not fully comprehensive (no mention of structuring alternatives or diagramming).

4 / 5

Completeness

The 'what' is clear (document/record/retain/update), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Contains 'architectural decision', 'decision', and 'rationale' but omits common synonyms users would say such as 'ADR', 'design decision', or 'tradeoffs'.

3 / 5

Distinctiveness Conflict Risk

'Document an architectural decision' with system-specific anchors (Hindsight, CLAUDE.md) is mostly distinct, with only minor overlap risk against general documentation skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
AndreJorgeLopes/devflow
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.