New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Dev Requirements

by codeaholicguy in codeaholicguy/ai-devkit

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

Apache-2.0Auto-check passed

Install Dev Requirements

skills CLI
$ npx skills add codeaholicguy/ai-devkit --skill dev-requirements -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install codeaholicguy/ai-devkit dev-requirements --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/dev-requirements .claude/skills/dev-requirements && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
dev-requirements
GitHub stars
1.6k
Token cost
~1.1k tokens
SKILL.md length
554 words
Files
2
Skills in repo
28
Repo updated
First seen
Licence
Apache-2.0

At a glance

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

  • Works in 9 steps: Run npx ai-devkit@latest lint before… → If working on a named feature, run npx… → If lint fails because project docs are… → …
  • The user wants to capture a new requirement
  • SKILL.md covers Phase Contract, New Requirement and Review Requirements
  • Calls npx

What it does

Dev Requirements is an agent skill from codeaholicguy/ai-devkit. 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.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

The repository describes itself as: The control plane for AI coding agents. The licence is Apache-2.0.

When your agent uses it

  • The user wants to capture a new requirement
  • Clarify product scope
  • Initialize feature docs
  • Review requirements

Example prompts

  • “/dev-requirements”

Requirements

  • Node.js

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Run npx ai-devkit@latest lint before phase work.
  2. If working on a named feature, run npx ai-devkit@latest lint --feature .
  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…
  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…

What it can do on your machine

Read from SKILL.md and the folder at commit 7ef0cd5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dev Requirements loads about 1.1k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 554 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~66
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from codeaholicguy/ai-devkit at commit 7ef0cd5, republished under its Apache-2.0 licence (© codeaholicguy). 554 words, ~1,071 tokens.

Download SKILL.mdSave it as .claude/skills/dev-requirements/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
dev-requirements
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.

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.

  1. Search AI DevKit memory for relevant past features or conventions with npx ai-devkit@latest memory search --query "<feature/topic>". If unfamiliar, check the memory skill first.
  2. Clarify feature name in kebab-case, problem, target users, key user stories, scope, non-goals, success criteria, UX, constraints, rollout, and validation.
  3. Brainstorm alternatives to confirm this is the right thing to build. Present 2-3 approaches with one-line trade-offs and a recommendation.
  4. Store reusable answers after clarification.
  5. Use dev-worktree to create or resume the active feature workspace with normalized <name>.
  6. Initialize docs with npx ai-devkit@latest docs init-feature <name> from the active worktree/repository and fill the returned paths. Treat those returned paths as authoritative because paths.docs may customize the docs directory.
  7. Fill requirements doc: problem statement, goals/non-goals, user stories, success criteria, constraints, open questions.
  8. Fill design doc: architecture with mermaid diagram, data models, APIs, components, design decisions, security/performance.
  9. Fill testing doc: derive scenarios from requirements success criteria and design components/edge cases as - [ ] checkboxes, plus mocks/fixtures and coverage target.
  10. If task tracing is available, record draft progress and next review step per task.
  11. Use dev-planning to create the initial task plan from the requirements, design, and testing docs.

Next: dev-requirements review, then dev-design.

Show full SKILL.md (146 more words)Show less

Review Requirements

Use for Phase 2.

  1. Run npx ai-devkit@latest lint --feature <name> and review the requirements doc path it validates. If manual path resolution is unavoidable, first resolve .ai-devkit.json paths.docs, falling back to docs/ai.
  2. Check it against the README.md template.
  3. Search memory for relevant conventions or past patterns.
  4. Review each section: problem statement, goals/non-goals, success criteria, user stories, constraints, open questions, template compliance.
  5. Resolve every gap, contradiction, ambiguity, open question, or implicit assumption.
  6. Brainstorm alternatives for key decisions and trade-offs before accepting the first approach.
  7. Update the requirements doc with clarified answers and chosen options.
  8. Store reusable clarifications in memory.
  9. If task tracing is available, record validation progress, next step, or blockers per task.
  10. Summarize what was validated, what was updated, and remaining open items.

Next: dev-design. If fundamental gaps remain unresolvable, return to New Requirement.

© codeaholicguy, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/dev-requirements of codeaholicguy/ai-devkit.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 7ef0cd5

Compare with similar skills

Dev Requirements next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dev Requirements compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dev Requirements this skillcodeaholicguy/ai-devkit1.6k—~1.1kAutomated safety check: PassApache-2.0
StartDonchitos/Claude-Code-Game-Studios26k—~6.4kAutomated safety check: PassMIT
Requirementsrizsotto/Bear6.5k—~2kAutomated safety check: PassGPL-3.0
Gsd Phaseopen-gsd/gsd-core10k1 repos~603Automated safety check: NotesMIT
Aria Required Attrthedaviddias/Front-End-Checklist74k—~459Automated safety check: PassMIT
Aria Required Parentthedaviddias/Front-End-Checklist74k—~498Automated safety check: PassMIT

Similar skills

  • Start

    Donchitos/Claude-Code-Game-Studios

    First-time onboarding — asks where you are, then guides you to the right workflow.

    26k GitHub stars~6.4k tokensUpdated 8 days ago
    Game DevelopmentAuto-check passed

  • Requirements

    rizsotto/Bear

    Write, modify, or review a requirement file under docs/requirements -- pick the single owning file, keep the text contract-only, name IDs so they need no explanation, and verify cross-references and…

    6.5k GitHub stars~2k tokensUpdated today
    Testing & QAAuto-check passed

  • Gsd Phase

    open-gsd/gsd-core

    Multi-phase management — add, insert, remove, or edit phases in ROADMAP.md (roadmap phase CRUD)

    10k GitHub starsUsed in 1 repo~603 tokens
    Product & Project ManagementAuto-check: notes

  • Aria Required Attr

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Include required ARIA attributes for roles.

    74k GitHub stars~459 tokensUpdated yesterday
    Frontend & DesignAuto-check passed

  • Aria Required Parent

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure ARIA roles are contained by required parent roles.

    74k GitHub stars~498 tokensUpdated yesterday
    Frontend & DesignAuto-check passed

  • GSD Phase Discussion

    open-gsd/gsd-core

    Asks adaptive questions about a project phase and records the decisions in a CONTEXT.md that later research and planning agents can act on without asking again.

    10k GitHub starsUsed in 1 repo~1.5k tokens
    Agent WorkflowsAuto-check: warnings

More from codeaholicguy/ai-devkit

All 28 skills in this repo

  • Agent Management

    codeaholicguy/ai-devkit

    AI DevKit · Manage running AI agents with ai-devkit agent commands.

    1.6k GitHub stars~558 tokensUpdated yesterday
    Auto-check passed

  • Dev Lifecycle

    codeaholicguy/ai-devkit

    AI DevKit · Orchestrator for structured SDLC phase skills. An agent skill from codeaholicguy/ai-devkit.

    1.6k GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

  • Task

    codeaholicguy/ai-devkit

    AI DevKit · Track dev-lifecycle / structured-debug progress on a durable task with the ai-devkit task CLI.

    1.6k GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

  • Simplify Implementation

    codeaholicguy/ai-devkit

    AI DevKit · Analyze and simplify existing implementations to reduce complexity, improve maintainability, and enhance scalability.

    1.6k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Agent Communication

    codeaholicguy/ai-devkit

    AI DevKit · Exchange information with active Codex, Claude Code, and other AI agents using ai-devkit agent list, detail, and send.

    1.6k GitHub stars~321 tokensUpdated yesterday
    Auto-check passed

  • Technical Writer

    codeaholicguy/ai-devkit

    AI DevKit · Review and improve documentation for novice users.

    1.6k GitHub stars~431 tokensUpdated yesterday
    Auto-check passed

Questions about Dev Requirements

What does Dev Requirements do?

AI DevKit · Requirements phase guidance for starting features and reviewing requirements. Dev Requirements is an agent skill from codeaholicguy/ai-devkit. AI DevKit · Requirements phase guidance for starting features and reviewing requirements.

When should I use Dev Requirements?

Dev Requirements fits situations like: the user wants to capture a new requirement; clarify product scope; initialize feature docs; review requirements.

How do I install Dev Requirements in Claude Code?

Run `npx skills add codeaholicguy/ai-devkit --skill dev-requirements -a claude-code`. Or copy the skill folder (skills/dev-requirements in codeaholicguy/ai-devkit) into .claude/skills/dev-requirements in your project. Claude Code loads it when a task matches its description.

How do I install Dev Requirements in Codex?

Run `npx skills add codeaholicguy/ai-devkit --skill dev-requirements -a codex`. Or copy the skill folder (skills/dev-requirements in codeaholicguy/ai-devkit) into .agents/skills/dev-requirements in your project. Codex loads it when a task matches its description.

Can I use Dev Requirements in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add codeaholicguy/ai-devkit --skill dev-requirements -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dev-requirements, .gemini/skills/dev-requirements, .github/skills/dev-requirements and .opencode/skills/dev-requirements in your project.

What does Dev Requirements need to run?

Going by SKILL.md and its folder, Dev Requirements needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Dev Requirements access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Dev Requirements safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dev Requirements use?

Dev Requirements is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dev Requirements use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dev Requirements?

Skills that share tags, products or a category with Dev Requirements: Start (Donchitos/Claude-Code-Game-Studios, 26k stars), Requirements (rizsotto/Bear, 6.5k stars), Gsd Phase (open-gsd/gsd-core, 10k stars) and Aria Required Attr (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dev Requirements?

codeaholicguy (a GitHub user) maintains it in codeaholicguy/ai-devkit, which has 1,641 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 6, 2026.

Source: codeaholicguy/ai-devkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.