00-onboard

star 29

Detect the current project's state and open a hub of project actions - understand the project, set up or refresh the memory bank, or continue the AIDD development journey. Silently inspects the project, the AIDD setup, and which AIDD plugins are installed, then adapts the menu to that context. Use when the user says "where do I start", "onboard me", "onboard me to this project", "what should I run next", "what should I work on next", "what's the state of this project", "guide me through aidd", "guide me through aidd-context", or invokes `aidd-context:00-onboard`. Do NOT use to enumerate every installed surface from raw user intent (the discovery skill in this plugin handles that).

ai-driven-dev By ai-driven-dev schedule Updated 6/11/2026

name: 00-onboard description: Guide the user through the AIDD framework on the current project. Explain the flow in plain language and suggest the next logical step, adapted to what is already set up and which AIDD plugins are installed. Use when the user asks where to start, what to do next, how AIDD works, or to be onboarded. Not for listing every installed surface (the explore skill does that) or running a skill the user already knows they need (invoke it directly).

Onboard

A plain-language guide to the AIDD framework for the current project. It reads the project lightly, explains where the project sits in the AIDD flow, and suggests the next logical step using only the plugins that are installed. It loops until the user stops.

Actions

# Action Role Input
01 read-project Lightly and silently read the project and the installed skills project root
02 orient Explain where the project sits and suggest the next step, in plain language the read from 01
03 act Run the suggestion, explain it, teach the flow, switch step, or stop the user's choice

Run 01 → 02 → 03, then loop back to 01 after each step until the user stops. Run each action's ## Test before the next.

Transversal rules

  • Teach, do not assume. The user may be new to AIDD. Explain a term the first time it appears (the memory bank is the project memory the AI loads each session), never assume framework literacy.
  • Suggest, never force. Show where the project seems to stand and the next logical step, and always let the user choose another.
  • Plain language only. No internal state names, no raw phase labels, no signal dump reaches the user. The user reads guidance, not a state machine.
  • Adapt to what is installed. Suggest by function and resolve it to a skill that is actually installed. If none is installed, name the missing capability by function, never invent a skill.
  • Silent read. 01-read-project prints nothing. The first visible output is the plain briefing from 02-orient.
  • Re-read after each step. The project changes, so read again before suggesting again.
  • Wait for an explicit reply between prompts. Never auto-advance.

References

  • references/journey.md: the AIDD flow stages, what each unblocks, and how a step resolves to an installed skill.
Install via CLI
npx skills add https://github.com/ai-driven-dev/aidd-framework --skill 00-onboard
Repository Details
star Stars 29
call_split Forks 2
navigation Branch main
article Path SKILL.md
More from Creator
ai-driven-dev
ai-driven-dev Explore all skills →