openspec-onboard

To onboard new developers to an OpenSpec workflow, you use a guided, phase-driven session that teaches the lifecycle from initialization to archiving. It provides hands-on prompts and artifact scaffolding for a safe, learn-by-doing experience.

The OpenSpec lifecycle includes preflight, proposal, specs, design, tasks, apply, and archive phases. This structured approach provides step-by-step prompts and clear artifacts for software project onboarding and change management.

You start a guided OpenSpec onboarding session by initiating the flow with the /opsx:onboard command. This triggers the phase-based workflow to begin your first hands-on, learn-by-doing guided session.

The best way to teach OpenSpec to a new team is using a teach-by-doing approach with graceful exit handling. It guides developers through a complete workflow from exploration to archiving, generating clear artifacts for review.

No dependencies are required to run the OpenSpec onboarding workflow. It relies entirely on a root SKILL.md file with YAML frontmatter for name and description, plus its defined multi-phase workflow configuration.

Yes, you can safely exit a phase-driven OpenSpec onboarding session midway. The workflow features graceful exit handling, ensuring your progress through the preflight, proposal, and specs phases remains safe and accessible for review.