project-onboard

Analyze repository structure and generate CLAUDE.md and agent metadata.

112|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/VKirill/claude-lane-stack --skill project-onboard-vkirill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-onboard
Source: https://github.com/VKirill/claude-lane-stack/tree/main/skills/project-onboard
Command: npx skills add https://github.com/VKirill/claude-lane-stack --skill project-onboard-vkirill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the cold-start problem for AI coding agents by creating a standardized, evidence-based project passport that ensures all agents share a consistent understanding of the codebase.

Core Features & Use Cases

  • Dual-Scenario Seeding: Automatically configures project depth based on complexity, ranging from minimal spine setup to full forensic analysis.
  • Evidence-Based Documentation: Generates deep-scan artifacts, including entrypoints, module flows, and wiki-to-code mismatch reports.
  • Use Case: When starting work on a new or legacy repository, use this to generate a reliable CLAUDE.md and agent-specific configuration files, ensuring the AI PM has a clear map of the project structure and constraints.

Quick Start

Run the project onboard skill on the current directory to perform a full forensic analysis and generate the necessary agent configuration files.

Frequently Asked Questions about project-onboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is forensic project onboarding for AI coding agents?

To automate CLAUDE.md generation for multi-agent coding, run a forensic onboarding analysis on your project root. This maps repository structure and entrypoints to produce standardized agent-specific metadata ensuring consistent AI context.

How do I set up a legacy repository for multi-agent coding environments?

Forensic project onboarding for AI coding agents is the automated process of analyzing repository structure and documentation to generate an evidence-based project passport. This ensures all agents share a consistent understanding of the codebase and identify wiki-to-code discrepancies.

Can I use automated onboarding to detect wiki-to-code discrepancies?

Set up a legacy repository for multi-agent coding environments by running automated forensic onboarding within the project root. This performs a deep scan of module flows and entrypoints to generate reliable agent-specific configuration files and resolve wiki-to-code mismatches.

Does project onboarding work with both minimal and complex repository structures?

Yes, you can use automated onboarding to detect wiki-to-code discrepancies by executing a forensic analysis within your project root. The deep scan maps code flows against existing documentation and generates a mismatch report for consistent agent context.

What are the limitations of automated forensic onboarding for project initialization?

Yes, project onboarding works with both minimal and complex repository structures through dual-scenario seeding. It automatically configures project depth based on complexity, ranging from a minimal spine setup to a full forensic analysis generating deep-scan artifacts.

What are the limitations of automated forensic onboarding for project initialization?

A key limitation of automated forensic onboarding is that it requires execution directly within the project root directory to function correctly. The evidence-based documentation and agent metadata generation depend entirely on mapping the actual repository structure and code flows present.