openspec-onboard

OpenSpec onboarding guides teams hands-on through a complete change cycle directly in the codebase. It covers creating proposals, specs, design artifacts, and task checklists for real changes to teach the workflow.

Creating OpenSpec proposals and specs is best practiced through a guided onboarding flow that scaffolds artifacts like proposal.md and design.md. This provides safe, repeatable learning with clear checkpoints for small changes.

Yes, preflight checks are required to verify OpenSpec prerequisites are met. The onboarding process runs these checks to help you initialize your environment before guiding you through the change cycle.

Guided onboarding scaffolds design artifacts and task checklists for small, real changes. It provides templates for design.md and tasks.md to demonstrate the workflow and preserve decisions during the cycle.

The OpenSpec workflow includes a built-in archival process that finalizes completed changes. Onboarding guides you through this archival step as the last phase of the change cycle to ensure safe, repeatable learning.

OpenSpec onboarding runs inside your codebase to turn learning into real practice. This hands-on approach lets development teams apply the workflow to actual small changes rather than simulated examples.