CtrlK
BlogDocsLog inGet started
Tessl Logo

031-architecture-adr-functional-requirements

Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project

75

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

85%

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

The content is well-structured with a clear sequenced workflow, explicit validation checkpoints, and a clean single-level reference split. Its only weakness is mild redundancy where the 'When to use' section and parts of the Workflow section repeat material already conveyed elsewhere.

Suggestions

Remove or condense the 'When to use this skill' section, since its trigger phrasings duplicate the frontmatter description already loaded into context.

Avoid restating the Constraints (one/two questions at a time, validate before proposing ADR) inside the Workflow steps; reference the Constraints section instead to eliminate overlap.

Consider collapsing the bullet list under 'What is covered in this Skill?' into the overview paragraph to reduce token usage without losing information.

DimensionReasoningScore

Conciseness

The body is mostly lean and avoids explaining concepts Claude already knows, but the 'When to use this skill' section duplicates the trigger phrasings already present in the description, and the Workflow section restates constraints from the Constraints section, so it could be tightened.

2 / 3

Actionability

Gives concrete, executable guidance: a specific shell command ('date'), an explicit reference path, and precise behavioral rules ('Pose one or two discovery questions at a time; never all at once'), which is appropriately actionable for an interactive discovery skill.

3 / 3

Workflow Clarity

A clear numbered sequence (steps 0–3) with explicit validation checkpoints — 'Validate summary with user', 'Wait for user to confirm proceed', and 'Only after user confirms proceed' — providing the feedback loop the rubric rewards.

3 / 3

Progressive Disclosure

The body is an overview that points to a single, clearly signaled, one-level-deep bundled reference (references/031-architecture-adr-functional-requirements.md, verified present) in a dedicated Reference section, with content appropriately split.

3 / 3

Total

11

/

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.

The description is strong across all dimensions: it states concrete capabilities, includes explicit 'Use when' triggers and natural user phrasings, and occupies a distinct, well-scoped niche. It fully answers both what the skill does and when Claude should invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions such as 'create Architectural Decision Records (ADRs)', 'document command-line or HTTP service architecture', 'capture functional requirements', and 'design interfaces with documented decisions', matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('Facilitates conversational discovery to create ADRs for functional requirements') and when with an explicit 'Use when...' clause plus 'This should trigger for requests such as...'.

3 / 3

Trigger Term Quality

Includes natural user phrasings — 'Create ADR for functional requirements', 'Document functional requirements', 'Capture functional requirements', 'Generate functional requirements in an ADR' — giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (ADRs for functional requirements scoped to CLI and/or REST/HTTP), with distinct triggers and an explicit project scope ('Part of cursor-rules-java project'), making conflict with other skills 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
jabrena/cursor-rules-java
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.