con un clic
team-brain-onboard
// Generate onboarding context for new team members from team brain knowledge. Use when user says 'onboard', 'onboarding', 'new developer', 'getting started', or '/team-brain onboard'.
// Generate onboarding context for new team members from team brain knowledge. Use when user says 'onboard', 'onboarding', 'new developer', 'getting started', or '/team-brain onboard'.
Regenerate BRAIN.md and optionally generate .cursorrules and AGENTS.md from team brain entries. Use when user says 'sync', 'regenerate', 'update brain', or '/team-brain sync'.
Shared team memory for Claude Code. Record lessons, decisions, and conventions that persist across sessions and team members. Use when user says 'team brain', 'learn', 'decide', 'convention', 'recall', 'team memory', or '/team-brain'. Subcommands: learn, decide, convention, recall, status, init.
| name | team-brain-onboard |
| description | Generate onboarding context for new team members from team brain knowledge. Use when user says 'onboard', 'onboarding', 'new developer', 'getting started', or '/team-brain onboard'. |
| allowed-tools | Bash, Read, Grep |
Generate a comprehensive onboarding document from all team brain entries.
node "${CLAUDE_SKILL_DIR}/../../scripts/store.js" list
node "${CLAUDE_SKILL_DIR}/../../scripts/store.js" list "" conventions
node "${CLAUDE_SKILL_DIR}/../../scripts/store.js" list "" decisions
node "${CLAUDE_SKILL_DIR}/../../scripts/store.js" list "" lessons
node "${CLAUDE_SKILL_DIR}/../../scripts/store.js" list "" knowledge
Read the full content of key entries using the Read tool on their file paths.
Generate a structured onboarding document with these sections:
# Onboarding Guide
> Auto-generated from Team Brain on DATE
## Project Overview
[Synthesized from knowledge entries]
## Coding Conventions
[All active conventions, clearly stated]
## Architecture Decisions
[Key decisions with brief context on WHY]
## Lessons Learned
[Important gotchas and insights the team has discovered]
## Key Things to Know
[Anything else a new developer should know on day 1]
## Contributors
[Who to ask about what, based on contributor data]