openspec-onboard

To onboard a new developer with the OpenSpec workflow, use a guided step-by-step process that walks them through exploring, creating, proposing, specifying, and implementing a change in a real codebase.

The OpenSpec workflow lifecycle for codebase management is a complete cycle spanning exploration, change creation, proposal drafting, specification writing, design documentation, task breakdown, implementation, and archiving artifacts.

You create and draft change proposals for your codebase by analyzing tasks, generating interactive prompts, and executing OpenSpec CLI commands to manage change artifacts like specifications and design documentation.

Yes, you need the OpenSpec CLI installed and available as a dependency, because the workflow directly executes OpenSpec commands to create directories, scan code, and manage change artifacts in your project.

Yes, you can use guided developer tools for onboarding to a new git workflow, allowing new team members to learn lifecycle stages by completing a small, real task within an existing project.

A limitation of automating OpenSpec task breakdown is that the interactive prompts and code analysis rely on actual project operations, requiring a real codebase environment to scan and create directories correctly.