openspec-onboard

The OpenSpec workflow is learned through a guided cycle from task selection to archiving a change. This onboarding process facilitates learning by performing real codebase actions with step-by-step narration.

Onboarding a new developer to an agile codebase workflow is best done by completing a small, real task in the project's repository. This guided process actively scans code and analyzes git history to identify tasks.

To generate proposal and design specs, you initiate a workflow cycle that creates artifacts including proposals, specs, designs, and tasks. This process tracks implementation from start to archiving.

Yes, you can use this guided workflow to identify tasks via git history analysis and code scanning. It actively interacts with your codebase to find real tasks and demonstrate implementation.

The OpenSpec onboarding process does not require prior knowledge of agile methodologies. It guides users step-by-step through creating, proposing, specifying, designing, implementing, and archiving a change.

A limitation of this guided workflow for codebase management is that it focuses specifically on the OpenSpec cycle. It facilitates learning by performing real codebase actions rather than acting as a general-purpose development tool.