onboard

Plugin onboard from marketplace apurvbazari-plugins in ApurvBazari/claude-plugins. Commands read from the repo's manifest — 11 days ago.

Skills (11)

• adopt

  Bring a repo's existing hand-crafted Claude tooling under onboard management — synthesizes an onboard baseline (retrofit-mode meta + snapshots) WITHOUT modifying any hand-crafted file, so /onboard:update works afterward. Use only when the user explicitly invokes /onboard:adopt, or when start/update

• check

  Health check for Claude tooling setup. Use when user asks about the state of their `.claude/` configuration, artifact drift, whether onboard-generated files are still intact, or wants a summary of what `/onboard:start` produced. Read-only — safe to auto-invoke.

• evolve

  Apply accumulated tooling drift to Claude configuration — writes and can delete generated tooling files, and asks before installing any plugin. Use when user says their Claude tooling is out of sync, mentions drift detected by hooks, installed/removed a plugin and wants the Plugin Integration sectio

• generate

  Internal: builds Claude tooling from onboard's v3 context via the config-generator agent. Called by start, update and evolve.

• generation

  Internal: the config-generator agent's rules for writing each tooling artifact. Loaded only during onboard generation.

• maintain

  Internal, non-interactive: applies a maintain-detect report to CLAUDE.md and writes maintain-result.json. For orchestrators.

• research

  Internal: onboard's verified codebase research engine. Called by onboard's start, adopt, update and evolve skills; returns the research dossier.

• start

  Use ONLY when the user explicitly runs /onboard:start. The full interactive onboarding wizard that sets up tailored Claude Code tooling for a project. Never auto-invoke.

• update

  Update existing Claude tooling against onboard's bundled best-practice guides — re-analyzes the codebase, checks the live Claude Code docs for features newer than those guides, presents targeted upgrade options, and applies approved changes with merge/replace choice per file. Use only when user expl

• verify

  Independent feature verification for projects with feature tracking — writes results to docs/feature-list.json, docs/progress.md and docs/verification-reports/. Use when user wants to test whether features in docs/feature-list.json pass their acceptance criteria, check sprint gate status, or run ver

• wizard

  Internal: onboard's adaptive Q&A that gathers project preferences. Called by onboard's start and adopt skills.

Subagents (5)

• codebase-analyzer

  Analyzes a project without editing it: stack, file inventory, complexity and patterns. Dispatched by /onboard:start before generation.

• config-generator

  Writes the Claude tooling artifacts (CLAUDE.md, rules, skills, agents, hooks, .mcp.json) from onboard's analysis and wizard answers. Dispatched only by onboard's generate step.

• feature-evaluator

  Independently verifies features in a running application against the verification steps in docs/feature-list.json. Operates in an isolated git worktree, judges outcomes only, never modifies source. Spawned by /onboard:verify.

• research-specialist

  Researches one dimension of a codebase without editing it and returns claims with file:line evidence. Dispatched only by onboard's research engine.

• research-verifier

  Tries to refute each research claim against the real code and returns a vote per claim, without editing anything. Dispatched only by onboard's research engine.

Similar plugins