openspec-onboard

A structured onboarding workflow guides developers through a complete change cycle from initialization to archival. It uses preflight checks, phased tasks, artifact creation, and implementation tracing to teach end-to-end software project changes.

To guide a new developer through codebase onboarding, execute a structured workflow spanning preflight checks, task exploration, change creation, drafting artifacts like proposals and specs, and implementation tracing with built-in pauses for reflection.

To create change artifacts during onboarding, follow a phased workflow that includes drafting proposals, specs, design documents, and task lists. This ensures hands-on learning with reusable templates and proper change-archive discipline.

Yes, you can use a hands-on onboarding tutorial for team software engineering projects. It provides a reusable pattern for teaching end-to-end workflows, team onboarding, and capability demonstrations with real-world codebase interactions and guardrails.

No dependencies or external components are required to run an OpenSpec onboarding workflow. The process operates independently using built-in preflight checks, artifact templates, and change-archive discipline within your project workspace.

The best way to maintain change-archive discipline during a coding onboarding process is to execute a structured workflow that explicitly traces implementation steps and archives history from initialization through the final archival phase.