openspec-onboard

To onboard developers to an OpenSpec workflow, use a guided process that teaches tasks from preflight to archiving. It walks users through hands-on code changes, reducing setup friction and confusion by applying the workflow directly in the project environment.

OpenSpec change management creates artifacts under openspec/changes/<name>/ including proposal.md, design.md, specs/, and tasks.md. These files capture decisions and guide implementation throughout the workflow phases.

Yes, you need the OpenSpec CLI installed to guide users through the change management workflow. The onboarding process relies on the CLI to execute environment commands and generate the required workspace artifacts.

The steps to guide a team through OpenSpec include Welcome, Task Selection, Explore Demo, Create Change, Proposal, Specs, Design, Tasks, Apply, and Archive. This phased learning approach ensures comprehensive coverage of the workflow cycle.

The best way to learn OpenSpec is through a step-by-step onboarding workflow within a real codebase. This hands-on approach teaches the complete cycle from idea to implementation, allowing users to adjust artifacts as they learn.

OpenSpec requires a self-contained workspace to capture decisions and guide implementation effectively. By creating openspec/changes/<name>/ with structured artifacts, it ensures all proposal, design, and task details are documented and traceable.