dev-requirements

AI DevKit · Requirements phase guidance for starting features and reviewing requirements. Use when the user wants to capture a new requirement, clarify product scope, initialize feature docs, review requirements, or run dev-lifecycle phases 1-2.

Quality

100%

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

Quality

Content

100%Weight 40%Scale 1-3

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 efficient, action-oriented set of phased workflows with executable commands and validation checkpoints. It is concise, actionable, and well structured for a single-file instruction skill.

Dimension	Reasoning	Score
Conciseness	Lean, dense, instruction-only content with no padding or explanation of concepts Claude already knows; every token earns its place.	3 / 3
Actionability	Provides concrete, executable commands (e.g. 'npx ai-devkit@latest lint', 'npx ai-devkit@latest docs init-feature <name>') and specific doc sections to fill, copy-paste ready.	3 / 3
Workflow Clarity	Both workflows are clearly sequenced with explicit validation checkpoints and feedback loops — lint before phase work, gating ('Do not ... while material open questions remain'), and re-validation steps.	3 / 3
Progressive Disclosure	A single, well-organized SKILL.md with clear sections and no bundle files; sibling-skill mentions (dev-design, dev-planning) are routing cues, not nested references, so the simple-skill exception applies.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, concise, and pairs a clear capability statement with an explicit 'Use when...' trigger clause covering natural phrasings. It is specific, complete, and well-differentiated.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'capture a new requirement, clarify product scope, initialize feature docs, review requirements, or run dev-lifecycle phases 1-2' — matching the highest anchor.	3 / 3
Completeness	Explicitly answers both what ('Requirements phase guidance for starting features and reviewing requirements') and when (a 'Use when...' clause enumerating triggers), satisfying the top anchor.	3 / 3
Trigger Term Quality	Natural user-facing terms ('capture a new requirement', 'review requirements', 'feature docs', 'dev-lifecycle phases') give good coverage of what a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Scoped to the AI DevKit requirements-phase niche with phase-specific triggers, making overlap with unrelated skills unlikely.	3 / 3
	Total	12 / 12 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: codeaholicguy/ai-devkit
Path: skills/dev-requirements/SKILL.md
Commit: 15b09d2

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