OpenSpec v1.0.2: Spec Naming & Task Format Fixes
OpenSpec v1.0.2 clarifies spec naming conventions and fixes task checkbox format guidance for better apply phase tracking.
TL;DR
- Clarified spec naming convention — use capability names, not change descriptions
- Fixed task checkbox format guidance for apply phase tracking
Fixed
- Spec naming convention — Specs should be named after capabilities (
specs/<capability>/spec.md), not changes. Prevents confusion in spec organization. - Task checkbox format guidance — Tasks now clearly require
- [ ]checkbox format for proper apply phase tracking.
Update with: npm install openspec@1.0.2
Source: OpenSpec
