onboard skill
Analyze brownfield codebase and create initial continuity ledger
A100/100content scan
Is the onboard skill safe?
Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.
No findings.
Install the onboard skill
A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.
git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3.git /tmp/Continuous-Claude-v3 mkdir -p ~/.claude/skills cp -r /tmp/Continuous-Claude-v3/.claude/skills/onboard ~/.claude/skills/onboard
available in every project
In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub
The instructions your agent would load
SKILL.md as published, without the frontmatter. Read it on GitHub
Onboard - Project Discovery & Ledger Creation
Analyze a brownfield codebase and create an initial continuity ledger.
When to Use
- First time working in an existing project
- User says "onboard", "analyze this project", "get familiar with codebase"
How to Use
Spawn the onboard agent:
Use the Task tool with subagent_type: "onboard" and this prompt:
Onboard me to this project at $CLAUDE_PROJECT_DIR.
1. Create required directories if they don't exist:
mkdir -p thoughts/shared/handoffs/<project-name> .claude
2. Explore the codebase using available tools:
- Try: tldr tree . && tldr structure .
- Fallback: find . -type f -name "*.py" -o -name "*.ts" -o -name "*.js" | head -50
3. Detect tech stack (look for package.json, requirements.txt, Cargo.toml, go.mod, etc.)
4. Ask the user about their goals using AskUserQuestion
5. Create a YAML handoff at thoughts/shared/handoffs/<project-name>/onboard-<date>.yaml:
---
date: <ISO date>
type: onboard
status: active
---
goal: <user's stated goal>
now: Start working on <first priority>
tech_stack: [list of detected technologies]
key_files:
- path: <important file>
purpose: <what it does>
architecture: <brief description>
next:
- <suggested first action>Why an Agent?
The onboard process:
- Requires multiple exploration steps
- Should not pollute main context with codebase dumps
- Returns a clean summary + creates the handoff
Output
- Directories created: thoughts/shared/handoffs//, .claude/
- YAML handoff created (loaded automatically on session start)
- User has clear starting context
- Ready to begin work with full project awareness
Notes
- This skill is for BROWNFIELD projects (existing code)
- For greenfield, use /create_plan instead
- Handoff can be updated anytime with /create_handoff
More skills from parcadei/Continuous-Claude-v3
- Aagent-context-isolationAgent Context Isolation
- Aagent-orchestrationAgent Orchestration Rules
- Aagentic-workflowAgentic Workflow Pattern
- Aagentica-claude-proxyGuide for integrating Agentica SDK with Claude Code CLI proxy
- Aagentica-infrastructureReference guide for Agentica multi-agent infrastructure APIs
- Aagentica-promptsWrite reliable prompts for Agentica/REPL agents that avoid LLM instruction ambiguity
- Aagentica-sdkBuild Python agents with Agentica SDK - @agentic decorator, spawn(), persistence, MCP integration
- Aagentica-serverAgentica server + Claude proxy setup - architecture, startup sequence, debugging
- Aagentica-spawnSpawn Agentica multi-agent patterns
- Aanalytic-functionsProblem-solving strategies for analytic functions in complex analysis
- Aast-grep-findAST-based code search and refactoring via ast-grep MCP
- Aasync-repl-protocolAsync REPL Protocol