openspec-onboard

OpenSpec workflow automation is learned by running a complete guided cycle from task selection through archiving. The onboarding process walks first-time users through proposal, specs, design, tasks, and implementation using real codebase work.

Start guided onboarding by confirming OpenSpec is initialized via openspec status, then trigger the flow. The process orchestrates EXPLAIN, DO, SHOW, and PAUSE transitions to take you from task discovery through archiving.

OpenSpec onboarding finds practical starter tasks by scanning your repository. It surfaces artifacts like TODO and FIXME comments, risky error handling, missing tests, TypeScript any usage, and debug statements for you to work on.

The best way to manage large tasks during OpenSpec onboarding is to use built-in scope guardrails. The workflow nudges you toward smaller, learnable slices when a selected task seems too large for an initial run.

You need to initialize OpenSpec before starting the workflow onboarding process. The skill requires checking your project initialization status via the openspec status command before orchestrating the guided cycle.

The OpenSpec onboarding workflow requires archiving after tasks are completed to finalize the change as a decision record. This ensures the entire software change management cycle ends with a properly documented and archived outcome.