openspec-apply
Implement an approved OpenSpec change and keep tasks in sync. Use when building, coding, or executing an approved proposal.
When & Why to Use This Skill
The openspec-apply skill streamlines the software development lifecycle by automating the implementation of approved technical proposals. It ensures that code changes remain strictly aligned with design specifications while automatically synchronizing task progress, making it an essential tool for maintaining consistency between documentation and execution in OpenSpec-compliant projects.
Use Cases
- Executing Technical Proposals: Automatically translate approved design documents and proposal specifications into functional code changes while adhering to minimal implementation principles.
- Automated Task Management: Synchronize development progress by reading and updating tasks.md files, ensuring that checklists accurately reflect the current state of implementation.
- Workflow Standardization: Maintain project integrity by following a structured, step-by-step process for applying changes, from initial scope confirmation to final status updates.
- Context-Aware Coding: Leverage existing project conventions and historical proposal data to ensure new implementations are consistent with the broader codebase architecture.
| name | openspec-apply |
|---|---|
| description | Implement an approved OpenSpec change and keep tasks in sync. Use when building, coding, or executing an approved proposal. |
Guardrails
- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
- Keep changes tightly scoped to the requested outcome.
- Refer to
openspec/AGENTS.md(located inside theopenspec/directory—runls openspecoropenspec updateif you don't see it) if you need additional OpenSpec conventions or clarifications.
Steps Track these steps as TODOs and complete them one by one.
- Read
changes/<id>/proposal.md,design.md(if present), andtasks.mdto confirm scope and acceptance criteria. - Work through tasks sequentially, keeping edits minimal and focused on the requested change.
- Confirm completion before updating statuses—make sure every item in
tasks.mdis finished. - Update the checklist after all work is done so each task is marked
- [x]and reflects reality. - Reference
openspec listoropenspec show <item>when additional context is required.
Reference
- Use
openspec show <id> --json --deltas-onlyif you need additional context from the proposal while implementing.