030-architecture-adr-general

Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of Plinth Toolkit

Quality

75%

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 ./skills/030-architecture-adr-general/SKILL.md

Quality

Content

63%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.

A well-structured, lean overview with good progressive disclosure and a clear workflow including a confirmation checkpoint. It would improve by trimming the duplicated trigger list and adding more concrete inline guidance (or a brief ADR skeleton) for the elicitation and generation steps.

Suggestions

Trim the 17-item "When to use this skill" list to the few most natural triggers, since the description already carries them — this tightens conciseness.

Add a short inline outline of the MADR-style ADR structure (sections to fill) so the generate step is actionable without needing to open the reference.

Add an explicit verification step to the workflow (e.g. confirm all required ADR sections are populated and consistent) to strengthen workflow_clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with well-organized sections, but the 17-item "When to use this skill" list duplicates much of the description's trigger phrases and could be trimmed.	3 / 5
Actionability	Names concrete deliverables and instructs loading the reference and eliciting specific inputs, but the elicitation and synthesis steps stay high-level and delegate nearly all specifics to the reference file, leaving key details inline-incomplete.	3 / 5
Workflow Clarity	A clear three-step sequence (load + elicit, synthesize and confirm, generate) with an explicit user-confirmation checkpoint and an edge-case section, though it lacks an explicit validation step on the generated ADR.	4 / 5
Progressive Disclosure	The body is a lean overview pointing to a single one-level-deep reference (references/030-architecture-adr-general.md, which exists as a real file), clearly signaled in both the workflow and a dedicated Reference section.	5 / 5
	Total	15 / 20 Passed

Description

87%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.

A strong description that clearly states its Java-ADR niche, names concrete elicitation inputs and deliverables, and provides explicit natural-language triggers. Minor room to add a few more synonyms and template/storage specifics.

Dimension	Reasoning	Score
Specificity	Names the ADR/Java domain plus several concrete inputs it gathers ("context, stakeholders, options, and outcomes") and the concrete deliverable ("well-structured ADR documents"), with only minor gaps such as template/storage specifics.	4 / 5
Completeness	Explicitly answers both what it does (generate ADRs via an interactive elicitation process) and when to use it ("This should trigger for requests such as..."), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Lists natural trigger phrases users would say ("Generate ADR", "Create Architecture Decision Record", "Document architecture decision"), with good coverage but a few common synonyms (e.g. "design decision record", file extensions) missing.	4 / 5
Distinctiveness Conflict Risk	Scoped to "Java project" ADR generation with ADR-specific triggers, giving it a clear niche and minimal overlap with general documentation skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/030-architecture-adr-general/SKILL.md
Commit: 05bf9d1

Reviewed: 12 minutes 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.