/onboard

Detect pending offboard steps and route to the next session action.

8|1|Updated Jan 21, 2024
One-click install
npx skills add https://github.com/azigler/dotfiles --skill onboard-azigler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: /onboard
Source: https://github.com/azigler/dotfiles/tree/main/agents/skills/onboard
Command: npx skills add https://github.com/azigler/dotfiles --skill onboard-azigler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents lost context and missed work by restoring pending offboard steps, detecting first-session state, and guiding you to the correct next phase based on live repository signals.

Core Features & Use Cases

  • Honors pending offboard: Retroactively runs /offboard when a prior session ended without it, ensuring the system’s state remains consistent across sessions.
  • Detects first-session-on-a-new-project: Recognizes when foundational project artifacts are missing and routes you to an onboarding bootstrap decision flow.
  • Loads all skill bodies for orchestration: Forces the orchestrator to read every skill body so it can reliably route future actions without missing critical anti-patterns or prerequisites.

Quick Start

Run the /onboard skill at the start of a new orchestrator session to detect any pending /offboard, load all skill bodies, determine the current plan position, and get routed to the next action.

Frequently Asked Questions about /onboard

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

FAQPage Schema
How do I restore project context and recover work state at the start of a new session?

Session onboarding restores project context by discovering live repository signals, honoring pending offboard steps, and routing you to the correct next work phase. It reads plan tracking artifacts to ensure no open work is lost between sessions.

What happens if my previous session ended without running an offboard routine?

If a prior session ended without offboarding, the onboarding process retroactively runs those pending offboard steps to maintain consistent system state. This prevents lost context by ensuring all work artifacts and plan positions are properly reconciled.

How do I detect a first-session condition when starting work on a new project?

First-session detection identifies when foundational project artifacts are missing and routes you to an onboarding bootstrap decision flow. This ensures new projects receive proper initialization before orchestration begins tracking plan progress.

Why do I need to load all skill bodies into the main context during session startup?

Loading all skill bodies during session startup ensures the orchestrator can reliably route future actions without missing critical anti-patterns or prerequisites. It reads every skill definition to maintain context management consistency throughout the workflow.

What's the best way to orchestrate session startup for continuous plan tracking?

Orchestrating session startup requires reading project foundations, loading skill bodies, detecting pending offboards, and presenting an orientation report before routing. This bracketing approach with offboard ensures consistent state recovery and work phase continuity.

Can I use session onboarding for any orchestrator workflow or does it require specific dependencies?

Session onboarding applies to every orchestrator session where continuity depends on plan tracking and open work artifacts. It requires no external dependencies, relying solely on live project state signals and consistent bracketing with the offboard routine.