onboard

Generate briefing files and wire session-loop phases for Claude Cabinet projects.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/orenmagid/claude-cabinet --skill onboard-orenmagid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/orenmagid/claude-cabinet/tree/main/templates/skills/onboard
Command: npx skills add https://github.com/orenmagid/claude-cabinet --skill onboard-orenmagid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboard provides a guided setup to assemble Claude Cabinet for a project by generating the briefing layer and wiring the session loop so teams can start productive sessions with a consistent context.

Core Features & Use Cases

  • Skeleton skill pattern that orchestrates detect-state, interview, work-tracking, options, generate-briefing, generate-session-loop, modularity-menu, summary, and post-onboard-audit phases.
  • Adapts to first-run, early re-run, and mature re-run modes based on existing artifacts and interview results.
  • Creates actionable briefing and configuration artifacts, and wires orient and debrief with the rest of the cabinet.

Quick Start

Run onboard to generate the initial briefing and wire the session loop for your project.

Frequently Asked Questions about onboard

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

FAQPage Schema
How do I generate a project briefing layer and wire the session loop for Claude Cabinet?

To generate the briefing layer and wire the session loop, run onboard to orchestrate detect-state, interview, and generation phases, adapting to existing artifacts and interview answers to create targeted briefing files and configuration records.

What is the guided onboarding process for assembling a Claude Cabinet project?

Guided onboarding assembles the Claude Cabinet by applying phase file protocols to generate _briefing.md, system-status.md, and corrc.json, ensuring teams start productive sessions with consistent context across first-run and mature re-run modes.

Can I re-run the onboarding workflow on an existing project with mature artifacts?

Yes, onboarding adapts to detected state for early re-runs and mature re-runs, modifying existing artifacts and session-loop wiring based on current module selections and interview results without starting from scratch.

Do I need any external dependencies to set up the briefing layer and session loop?

No external dependencies are required to set up the briefing layer and session loop; onboard operates independently to record decisions into configuration files and wire orient and debrief phases within the cabinet.

What configuration and briefing files are created during the onboarding phases?

The onboarding phases create targeted briefing files, wire orient and debrief phase connections, and record decisions into _briefing.md, system-status.md, and corrc.json to establish consistent project context.

How does the session-loop wiring adapt to different project states during onboarding?

Session-loop wiring adapts by detecting existing project artifacts during the detect-state phase, then adjusting the generated briefing layer and configuration outputs based on whether it is a first-run, early re-run, or mature re-run.