onboard

Configures Blueprint workflow files to match a freshly scaffolded project's detected stack.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill onboard-leroyadonis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/LeroyAdonis/kitfix-2.0/tree/main/.agents/skills/onboard
Command: npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill onboard-leroyadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After overlaying the Blueprint onto a freshly scaffolded project, the generic setup files do not match the real stack, commands, or conventions. This Skill inspects the repository and tunes the Blueprint's entry files, coding standards, ignore rules, and tool adapters so planning and the build loop work against the actual project. ## Core Features & Use Cases - Stack Detection: Surveys lockfiles, manifests, framework configs, and source layout to identify the package manager, framework, and available commands without inventing conventions. - Setup File Tuning: Updates AGENTS.md commands, replaces a copied Blueprint README with a real project stub, aligns coding-standards.md with the detected stack, and fixes CLAUDE.md placeholders. - Visibility and Adapter Management: Handles the choice between committing Blueprint workflow files or keeping them local-only via .gitignore, and reports which adapter folders (.agents/, .claude/) each AI tool needs. - Use Case: You scaffold a Next.js app, copy the Blueprint files in, and run /onboard. The Skill detects pnpm and Next.js, rewrites the Commands section with the real scripts, flags that no test command exists, and hands off to project-plan.md and build-plan.md. ## Quick Start Run /onboard after overlaying the Blueprint onto a new project to detect the stack and tune all setup files before planning.

Frequently Asked Questions about onboard

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

FAQPage Schema
How do I set up the Blueprint after copying it into a new project?▼

Run /onboard after scaffolding your app and overlaying the Blueprint files. The Skill detects your stack, updates AGENTS.md commands, tunes coding standards, checks .gitignore, and tells you which planning files to fill in next.

What is the difference between /onboard and /adopt?▼

Use /onboard for freshly scaffolded projects with empty or worksheet-like planning docs. Use /adopt for brownfield apps that already have shipped features and real behavior that must be reflected into the plans.

Should Blueprint workflow files be committed to git or kept local?▼

Committing them is the recommended default because it is portable across teams and machines. Local-only mode adds .agents/, .claude/, blueprint/, and CLAUDE.md to .gitignore while keeping AGENTS.md public, but state will not travel with the repo.

Does /onboard overwrite my project-plan.md or build-plan.md?▼

No. Planning documents are user-owned and never overwritten. The Skill only touches setup files such as AGENTS.md, coding-standards.md, .gitignore, and README stubs, and stops if the plans already contain real content.

Does /onboard install dependencies or run framework scaffolders?▼

No. The Skill never runs scaffolders or installs dependencies unless the user explicitly asks. It only reads existing files to detect the stack and edits setup files to match what already exists.