OpenSpec workflow: specs for AI coding assistants

OpenSpec is presented as an open source command-line framework for spec-driven development inside a local repository. The tutorial explains how a coding assistant can use written requirements and task lists to retain project intent beyond a chat's context window. The speaker argues that this reduces architectural drift; the video does not establish that outcome through comparative testing.

For existing codebases, the workflow uses delta specs that describe the components under modification rather than requiring documentation of the entire repository. Active work lives in change directories, while the specs directory holds accumulated specifications. The tutorial distinguishes terminal commands for configuration and inspection from /opsx actions entered in the assistant's chat.

The core workflow covers exploration, proposal, implementation, and archiving. Planning produces proposal.md, spec.md, design.md, and tasks.md for human review before code generation. Developers can revise these artifacts during implementation. Archiving merges specification changes and preserves the change folder as history.

Expanded workflows use schema dependencies to pace artifact generation. The speaker describes config.yaml for shared project context, per-artifact rules, and verification checks for completeness, correctness, and agreement with the design. Separate change directories also support pausing one feature to handle a fix and then resuming its checklist.