Onboard

by parcadeid07ff4b06b62No license3.9K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 8 months ago

Analyze brownfield codebase and create initial continuity ledger

Instructions onlyAI & Agents
AI-generated overview

Analyzes an existing codebase and produces an initial YAML continuity handoff summarizing stack, key files and goals.

What it does
This skill guides an onboarding pass over an existing (brownfield) project. It instructs the agent to create handoff and .claude directories, explore the codebase with tools such as tldr or find, detect the tech stack from manifest files, and ask the user about their goals. It then writes a dated YAML handoff containing the goal, tech stack, key files, architecture notes and suggested next actions.
When to use it
Use it the first time you work in an existing project, or when the user asks to onboard, analyze the project, or get familiar with the codebase. It is intended for brownfield projects with existing code, not new projects.
Requirements
No scripts are shipped; it is instructions only. It relies on the agent's Task tool with a subagent_type of onboard, codebase exploration tools (tldr preferred, with find as fallback), and the ability to create directories and write a YAML file. It also uses an AskUserQuestion step to collect the user's goals.

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/<project>/, .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

Source and attribution

Source:parcadei/continuous-claude-v3in.claude/skills/onboardat commitd07ff4b

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal