Help us improve
Share bugs, ideas, or general feedback.
From onboarding
Gathers project context from instructions, git status/history, open issues via bd, and build files to deliver concise status briefing and next steps.
npx claudepluginhub florianbuetow/claude-code --plugin onboardingHow this skill is triggered — by the user, by Claude, or both
Slash command
/onboarding:onboardingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Orient in the current project by gathering context from multiple sources: project instructions, version control state, issue tracker, and build system. Produce a concise status briefing and suggest what to tackle next.
Discovers git state, project structure, language/framework, and dev tooling in unfamiliar codebases. Provides structured summary with risk flags and recommendations for onboarding.
Displays project status, roadmap progress, blockers, and next-action suggestions based on workflow state. Use for progress checks and orientation.
Detects project type, tech stack, AIWG phase status, team config, git activity, blockers, and risks from .aiwg files and repo. Summarizes context and recommends next actions.
Share bugs, ideas, or general feedback.
Orient in the current project by gathering context from multiple sources: project instructions, version control state, issue tracker, and build system. Produce a concise status briefing and suggest what to tackle next.
Execute all steps below. Run independent steps in parallel where possible.
You MUST read AGENTS.md, CLAUDE.md, GEMINI.md, and COPILOT.md in the project root. Skip any that don't exist, but read all that do. If a file explicitly instructs you to read another file, read that file too. If both files contain the same content (e.g., one simply redirects to the other), only read it once. When both files exist and their rules conflict, AGENTS.md takes precedence.
Extract from these files:
Follow the instructions and rules found in these files during this session.
Execute these four checks concurrently:
2a. Git Status
Run git status to identify:
2b. Recent Git History
Run git log --oneline --date=short --format="%h %ad %s" -15 to see:
2c. Open Issues
Run bd ready to list issues with no blockers that are ready to work on.
Also run bd list --status=in_progress to check for any claimed but unfinished work.
If beads is not initialized (command fails), skip this step and note that no issue tracker is configured.
2d. Build System
Read the project's justfile (or Makefile if no justfile exists) to identify:
just test, just ci, etc.)just run)Present a concise status briefing covering: