ospec-change

To manage an OSpec change end to end, you advance the active change through requirement intake, proposal refinement, task tracking, implementation guidance, verification, and final closeout. This ensures progress, validation, and archive readiness are tracked continuously.

Yes, you can use queue-aware planning for ordered OSpec work items. When you explicitly want ordered work, the workflow matches requirements and coordinates proposal, tasks, and state documents to advance changes sequentially.

Change verification applies plugin gate checks, such as Stitch when enabled, to enforce validation before closeout. It coordinates verification and review documents to ensure the active OSpec change meets archive readiness requirements.

Yes, you need an initialized OSpec project to advance a change. The workflow requires reading project metadata to coordinate proposal, tasks, state, verification, and review documents for requirement intake and final archive.

The best way to track implementation guidance for a single change is by advancing the active OSpec change through task tracking and state coordination. This reads project metadata and enforces plugin gates to guide the work to final closeout.

OSpec change management requires coordinating proposal, tasks, state, verification, and review documents to prevent losing track of requirements, progress, and validation. This coordination enforces plugin gates and ensures proper archive readiness for the active change.