- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add codeaholicguy/ai-devkit --skill dev-requirements -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add codeaholicguy/ai-devkit --skill dev-requirements -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add codeaholicguy/ai-devkit --skill dev-requirements -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add codeaholicguy/ai-devkit --skill dev-requirements -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/codeaholicguy/ai-devkit/tree/HEAD/skills/dev-requirementsFrom the publisher
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.
npx ai-devkit@latest lint before phase work.npx ai-devkit@latest lint --feature <name>.npx ai-devkit@latest init -a -e claude --built-in --yes, then rerun lint.docs/ai; it is only the default docs directory.dev-lifecycle established usable task tracing, emit requirements phase, clarification/progress, blocker/open-question, and next-step events per task.Use for Phase 1 or /new-requirement.
npx ai-devkit@latest memory search --query "<feature/topic>". If unfamiliar, check the memory skill first.dev-worktree to create or resume the active feature workspace with normalized <name>.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.- [ ] checkboxes, plus mocks/fixtures and coverage target.task.dev-planning to create the initial task plan from the requirements, design, and testing docs.Next: dev-requirements review, then dev-design.
Use for Phase 2.
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.README.md template.task.Next: dev-design. If fundamental gaps remain unresolvable, return to New Requirement.
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 r
---name: dev-requirementsdescription: AI DevKit · Requirements phase guidance for starting features and reviewing requirements. Use when the user…---# skills/dev-requirements/SKILL.mdOverview
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.
FAQ
Download skills/dev-requirements/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/codeaholicguy/ai-devkit.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.