# Dev Requirements

AI DevKit · Requirements phase guidance for starting features and reviewing requirements.

- Repository: https://github.com/codeaholicguy/ai-devkit (1656 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add codeaholicguy/ai-devkit --skill dev-requirements -g -a claude-code -y`
Codex: `npx skills add codeaholicguy/ai-devkit --skill dev-requirements -g -a codex -y`
Cursor: `npx skills add codeaholicguy/ai-devkit --skill dev-requirements -g -a cursor -y`
Gemini CLI: `npx skills add codeaholicguy/ai-devkit --skill dev-requirements -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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 usable task tracing, emit requirements phase, clarification/progress, blocker/open-question, and next-step events per `task`.

## New Requirement

Use for Phase 1 or `/new-requirement`.

The rest: https://github.com/codeaholicguy/ai-devkit/blob/HEAD/skills/dev-requirements/SKILL.md