openspec-onboard

You can learn the OpenSpec workflow by using a guided onboarding process that creates a change container in your repository and walks you through each phase, from preflight to archival, while generating actual artifacts like proposals, specs, design, and tasks.

The OpenSpec change management onboarding process is a step-by-step workflow that takes new contributors through preflight, task selection, proposal creation, specification, design, task generation, and archiving within a live codebase to ensure hands-on learning.

Yes, you need the OpenSpec CLI installed and an accessible code repository to perform the onboarding tasks, as the process requires scaffolding a change container and generating artifact files directly within your project.

During a guided OpenSpec workflow, the artifacts generated include proposal files, specifications, design documents, and task lists, all created within a change container to demonstrate full cycle change management in your codebase.

Yes, you can use OpenSpec onboarding to teach workflow steps in future projects because it provides a reusable, narrated onboarding experience that demonstrates exploration, artifact generation, and documentation across preflight to archival phases.

A limitation of guided OpenSpec onboarding is that it strictly requires the OpenSpec CLI and a live, accessible code repository to function, meaning it cannot be used for standalone theoretical practice without an active codebase environment.