openspec-onboard

An OpenSpec workflow is a structured change management process that moves from idea to implementation through discovery, proposal, specs, design, tasks, and archival steps. It creates a validated change container with proposal, specs, design, tasks, and an archive record.

You can onboard new contributors by following a guided, step-by-step workflow that teaches how to create a change container, draft a proposal, define specs, design, and tasks, then apply and archive the change. This provides hands-on learning in a safe, repeatable pattern.

Yes, this structured workflow is designed to run small-to-medium codebase changes end-to-end. It applies a stepwise guidance pattern from welcome to archive, enabling a full OpenSpec cycle for manageable development tasks.

The best way to create traceable artifacts is using a guided workflow that generates interactive artifacts, including a change container with proposal, specs, design, tasks, and an archive-ready record. This ensures full traceability for new contributors learning the process.

No specific developer tools or dependencies are required to start the OpenSpec onboarding workflow. You simply follow the guided prompts and acknowledgments to create and validate the structured change container.

You should avoid using this full stepwise workflow for task management if your changes do not require structured traceability or the overhead of proposal, specs, design, and archival steps. It is best suited for educational onboarding and structured small-to-medium changes.