openspec-onboard

Run the OpenSpec CLI onboard command in your project directory to start a guided change workflow. This initializes a change container, drafts proposals, defines specs, and walks you through implementation and archiving.

The OpenSpec change cycle is a structured workflow moving from task selection to archiving. It guides developers through proposal drafting, spec definition, design, implementation, and archiving to create reproducible project records under openspec/changes.

Yes, the OpenSpec CLI must be installed to use this guided workflow. You also need access to your project's git working tree to create and save change artifacts, proposals, and specs under the openspec/changes directory.

Yes, preflight checks and scope guardrails keep your initial OpenSpec run concise and focused, but you can apply overrides to manage larger changes and tasks that exceed the default safe scope limits.

The OpenSpec onboarding process creates and saves change artifacts in a change container under the openspec/changes directory. These include drafted proposals, defined specs, design records, and implementation tasks for reproducible project tracking.