openspec-develop

Automating OpenSpec proposal implementation involves converting approved proposals into actionable tasks, enforcing stage gates, and updating progress checkboxes as work completes. This skill reads project artifacts to guide implementation and ensure scope alignment.

Managing development gates and checkpoints is done by enforcing stage gates and emitting checkpoint prompts during task execution. This approach preserves context across sessions, enabling safe crash recovery and reducing manual workflow drift.

Turning approved OpenSpec proposals into runnable steps requires parsing tasks.md sections into actionable items. The automation reads project.md, proposal.md, and specs to guide contextual exploration and ensure implementation matches the intended scope.

Resuming an OpenSpec development workflow after a crash is supported through checkpoint updates and context preservation. The automation emits checkpoint prompts that capture progress across sections and gates, allowing safe recovery without losing task state.

Starting OpenSpec task management requires an approved proposal as input. The automation begins processing tasks by targeting a specific change-id, reading project artifacts to guide execution, and gating progress through defined stages.

OpenSpec task automation drifts when context is lost across sessions or project artifacts are not consulted. This skill prevents drift by reading project.md, proposal.md, and specs to guide implementation, enforcing gates, and preserving checkpoint state for recovery.