00-onboard — Claude Code skill: what it does, how to install
00-onboard walks a project through AIDD: reads the repo, picks the next step, shows it on screen, then acts on your reply.
MIT ★ 571 updated 2026-10-29
/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-context@aidd-frameworkWhat 00-onboard does
The skill runs four actions in a loop. scan reads the project, assess works out the next move, present puts it on screen, run carries out whatever you pick. Each action's file in actions/ gets read before it fires, and the call takes a project argument.
It behaves like a guide rather than a code generator. Commands it names are the ones that actually exist in your repo, and a stale status gets re-checked instead of trusted.
Nothing happens until you reply. GUIDED steps never execute unattended, so the loop stalls by design if you were after a hands-off batch job.
What it helps with
- find a starting point in an unfamiliar repo
- get one concrete next step instead of a wall of docs
- carry a first feature through the AIDD path
- check the project's readiness before running commands
- pull the agent back on track when it drifts into generalities
Example prompts for the agent
- Onboard me on this repo — where do I start?
- Scan the project and tell me what to do next.
- Run onboarding with the
projectargument and show the next step.
How to install 00-onboard
1Plugin marketplace
/plugin marketplace add ai-driven-dev/framework/plugin install aidd-context@aidd-frameworkThis installs the whole aidd-context plugin with all its skills
2Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 00-onboard -a claude-code3Manually: put the files in place
~/.claude/skills/00-onboard/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/00-onboard/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 00-onboard -a codex2Manually: put the files in place
.agents/skills/00-onboard/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 00-onboard -a cursor2Manually: put the files in place
.cursor/skills/00-onboard/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ai-driven-dev/framework plugins/aidd-context/skills/00-onboard2Manually: put the files in place
.github/skills/00-onboard/SKILL.md1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 00-onboard -a gemini-cli2Platform CLI
gemini skills install https://github.com/ai-driven-dev/framework --path plugins/aidd-context/skills/00-onboardManually: put the files in place
.devin/skills/00-onboard/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 00-onboard -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 00-onboard
How do I install 00-onboard in Claude Code?
Use the marketplace: /plugin marketplace add ai-driven-dev/framework first, then /plugin install aidd-context@aidd-framework.
What does 00-onboard do?
It loops through four actions: reading the repository, deciding the next step, presenting it, and acting on your choice. Then it goes around again.
How is it different from listing installed skills?
It follows a project's path from first setup to a shipped feature. Taking inventory of installed surfaces is not what it is for.
Source text
SKILL.md · MIT
--- name: 00-onboard description: Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface. argument-hint: project --- # Onboard ```mermaid flowchart LR scan --> assess --> present --> run --> scan ``` ## Actions Run the actions in that order, looping. Read an action's file in `actions/` before running it. | # | Action | Does | | -- | ------- | -------------------- | | 01 | scan | read the project | | 02 | assess | decide the next step | | 03 | present | show the screen | | 04 | run | act on the reply | ## Transversal rules - Guide, do not lecture or dump. - Name real commands only, never invented ones. - Never run a GUIDED step unattended. - Never test a plugin version against a registry. - Never trust a stale status. - Wait for an explicit reply before running anything.
© AI-Driven Dev · MIT · ai-driven-dev/framework