openspec-onboard

OpenSpec onboarding provides a guided, hands-on workflow that walks developers through a complete change cycle end-to-end, from initialization to archiving, ensuring structured learning in a real codebase.

The OpenSpec change cycle structures development through phases: preflight, task selection, exploration, change creation, proposal, specs, design, tasks, and archival. This ensures decisions are preserved and artifacts are scaffolded automatically for future reference.

Yes, the OpenSpec CLI is required to run the onboarding flow. You also need basic familiarity with the OpenSpec model, including concepts like changes, proposals, specs, design, tasks, and archive, to effectively navigate the guided workflow.

The best way to scaffold OpenSpec artifacts is by following a step-by-step, phase-driven onboarding workflow that automatically generates and documents proposals, specs, design, and tasks, teaching you how to structure changes reproducibly.

Yes, teams needing a structured OpenSpec workflow can use this hands-on onboarding flow. It provides a reproducible learning path that reduces setup friction and ensures consistent onboarding across developers working with change management artifacts.

Onboarding new developers to OpenSpec is often slow and inconsistent without a structured guide. A hands-on, phase-driven workflow reduces this friction by scaffolding artifacts and walking users through a complete change cycle for reproducible learning.