Agent skill · Code Review & Quality

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.

Hoang Nguyen1,568★ · +5/wk · 1 repos on radarProfile →
claude-codecodexcursor
Install
npx skills add codeaholicguy/ai-devkit --skill dev-requirements --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/dev-requirements/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,572 · +4 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Dev Requirements Run the requirements phases for configured AI docs features. Before making docs or code changes, propose the concrete plan for this phase and wait for user approval unless the user already approved the exact phase plan. ## Phase Contract 1. Run `npx ai-devkit@latest lint` before phase work. 2. If working on a named feature, run `npx ai-devkit@latest lint --feature <name>`. 3. If lint fails because project docs are not initialized, run `npx ai-devkit@latest init -a -e claude --built-in --yes`, then rerun lint. 4. Read existing configured AI docs and keep diffs minimal. Do not assume `docs/ai`; it is only the default docs directory. 5. Ask until every material product, UX, architecture, scope, validation, rollout, contradiction, trade-off, or open question is answered, explicitly deferred, or accepted as a named assumption. 6. Ask one decision at a time, with why it matters, 2-3 viable options when useful, and a recommended answer. 7. Do not create, update, approve, or transition past requirements while material open questions remain. 8. Restate the shared understanding before updating docs or suggesting the next phase. 9. If parent `dev-lifecycle` established usab

What's inside
Steps it walks through
  1. Phase Contract
  2. New Requirement
  3. Review Requirements
Ships with 1 file
  • agents/openai.yaml
More from ai-devkit
All skills →
About this skill
What does the dev-requirements skill do?

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.

How do I install it?

Run `npx skills add codeaholicguy/ai-devkit --skill dev-requirements --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From codeaholicguy/ai-devkit, a repository with 1,572 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going