openspec-onboard

The OpenSpec workflow is a structured change management process guiding developers from repository initialization to artifact creation and deployment. It enforces a rhythm of exploration, proposal, specs, design, tasks, and archiving.

You can onboard new developers using a guided workflow that walks them through a complete process from initialization to deploying a tiny change. It teaches the OpenSpec lifecycle by having contributors do real work in the repository, creating a reusable playbook.

To implement a change in an existing codebase, you verify initialization, select a task, create a change container, draft a proposal, define specs and design, generate tasks, and finally archive the change. This structured process ensures complete lifecycle coverage.

Before starting OpenSpec onboarding, you must verify that OpenSpec is initialized in your workspace. The workflow requires an existing codebase where you can select tasks and perform real repository analysis to complete the guided change deployment.

Yes, you can use this workflow to train contributors across different projects. It serves as a reusable playbook that provides a repeatable pattern for introducing new contributors to the OpenSpec workflow through hands-on codebase tasks.

The best way to structure repository analysis and proposal drafting is following the OpenSpec rhythm: create a change container first, then draft proposals, define specs, and design tasks. This enforces a structured process for artifact creation and archiving.