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

81%

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

75%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, actionable requirements-phase skill with concrete commands, validation gates, and a lint feedback loop. It is efficient and clearly navigable; minor gains are available by tightening the intro and making a few implicit checkpoints explicit.

Suggestions

Tighten the opening approval-policy sentence and advisory steps (e.g. 'Restate the shared understanding before updating docs') to reduce token overhead without losing meaning.

Make implicit validation checkpoints explicit validate-fix-retry loops where possible (e.g. after filling each doc, re-run `npx ai-devkit@latest lint --feature <name>` and only proceed on pass).

Consider extracting reusable doc-section templates or checklists into a references/ file so SKILL.md stays a lean overview pointing one level deep.

Dimension	Reasoning	Score
Conciseness	Largely lean and instruction-oriented with concrete commands and no padding about basic concepts, but the opening approval-policy sentence and a few advisory lines ('Restate the shared understanding...') could be tightened further.	4 / 5
Actionability	Provides copy-paste-ready commands (e.g. `npx ai-devkit@latest lint --feature <name>`, `npx ai-devkit@latest docs init-feature <name>`) and specific path-resolution guidance, with minor gaps where sibling skills (dev-worktree, dev-planning, task, memory) are referenced but not inlined.	4 / 5
Workflow Clarity	Two clearly sequenced numbered workflows with explicit validation gates (lint before work, open-question gate in Phase Contract step 7) and a feedback loop (lint fails -> init -> rerun), though some checkpoints remain implicit rather than spelled out as validate-fix-retry.	4 / 5
Progressive Disclosure	Well-organized into three clearly headed sections with no monolithic wall and no nested references; sibling-skill cross-references are clearly signaled, though some reusable detail (e.g. doc templates) could be split into reference files.	4 / 5
	Total	16 / 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 pairs a clear capability statement with an explicit, multi-trigger 'Use when' clause and a well-scoped niche. Minor tightening of the opening framing and a few extra synonyms would push specificity and trigger_term_quality to full marks.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('capture a new requirement, clarify product scope, initialize feature docs, review requirements, or run dev-lifecycle phases 1-2'), though the opening 'Requirements phase guidance' framing is slightly abstract, leaving minor gaps in capability coverage.	4 / 5
Completeness	Clearly answers both 'what' ('Requirements phase guidance for starting features and reviewing requirements') and an explicit 'when' ('Use when the user wants to capture a new requirement...') with multiple concrete trigger phrases.	5 / 5
Trigger Term Quality	Good coverage of natural trigger phrases users would say in this lifecycle context ('capture a new requirement', 'review requirements', 'clarify product scope'), with a few common synonyms (e.g. 'feature spec', 'requirements doc') missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche scoped to AI DevKit requirements phase / dev-lifecycle phases 1-2 with distinct triggers, giving it minimal overlap risk with other 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: codeaholicguy/ai-devkit
Path: skills/dev-requirements/SKILL.md
Commit: d56e554

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.