openspec-onboard

To onboard new developers to a code change workflow, you can guide them through an interactive OpenSpec cycle that teaches them to propose, specify, implement, and archive small self-contained changes in a repository.

The OpenSpec proposal process involves creating a change container, drafting a proposal, producing specs and design notes, generating tasks, and finally archiving the completed changes to maintain a clear decision history.

You can guide a team through OpenSpec by running a 15 to 20 minute interactive session that walks them through creating change artifacts, drafting specs, implementing tasks, and archiving the completed work.

Yes, you need the OpenSpec CLI installed to use this guided workflow for creating change artifacts, drafting proposals, writing specs, and generating implementation tasks.

OpenSpec onboarding is designed for small, self-contained code changes. It includes scope guard rails to keep first runs small, making it best suited for teaching the process rhythm rather than managing large features.

An OpenSpec implementation cycle steps contributors through creating a change container, drafting a proposal, writing specs and designs, generating tasks, implementing the changes, and archiving the results.