openspec-apply-change

To implement OpenSpec change tasks, use a spec-driven workflow skill that reads context files like proposals and design docs to guide development and track task progress. It systematically walks users through each task to ensure all requirements are addressed.

Spec-driven development uses context files to define requirements before coding, and task management tracks states including blocked or completed tasks. This ensures implementation aligns with the specified proposal and design constraints.

Yes, the openspec CLI is required to perform status checks and retrieve instructions for tracking change management progress. The CLI provides the necessary task status data that guides the implementation workflow.

Start implementing an OpenSpec feature by invoking the apply-change skill with the specific change name. The skill retrieves the proposal, specs, design, and tasks files to provide contextual guidance for each development step.

Yes, the implementation workflow supports handling various task states, including blocked or completed tasks. It monitors and reports on the completion status of tasks within a change to ensure development continues smoothly.

OpenSpec task implementation relies on context files such as proposals, specs, design, and tasks documents. These files inform the development process by providing the necessary requirements and design constraints for each task.