openspec-onboard

To learn the OpenSpec workflow, you execute a real change cycle in your codebase from initial exploration to archived completion. This process guides you through structured proposals, specs, design, tasks, implementation, and archival for hands-on learning.

You use OpenSpec to plan and implement a bug fix by creating a change container, drafting required artifacts, applying code changes, and archiving the final decision history. It structures the entire implementation process end to end.

The OpenSpec workflow process involves exploring the codebase, creating a new change container, drafting proposals and specs, defining design and tasks, applying the implementation, and archiving the change to preserve decision history.

Yes, OpenSpec can scan your repository to find small practical tasks like missing tests, TODOs, weak error handling, and debug artifacts. It selects these starter tasks to lead you through a complete change cycle.

Yes, you need the OpenSpec CLI to guide proposal and spec generation for onboarding. The workflow requires CLI commands to support exploratory task selection, artifact generation, and the final change archival in your repository.