@fission-ai/openspec 1.0.1 → 1.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/dist/core/templates/skill-templates.js +2 -2
  2. package/package.json +1 -1
  3. package/schemas/spec-driven/schema.yaml +8 -3
package/dist/core/templates/skill-templates.js CHANGED
@@ -474,7 +474,7 @@ Common artifact patterns:
474
474
  **spec-driven schema** (proposal → specs → design → tasks):
475
475
  - **proposal.md**: Ask user about the change if not clear. Fill in Why, What Changes, Capabilities, Impact.
476
476
  - The Capabilities section is critical - each capability listed will need a spec file.
477
- - **specs/*.md**: Create one spec per capability listed in the proposal.
477
+ - **specs/<capability>/spec.md**: Create one spec per capability listed in the proposal's Capabilities section (use the capability name, not the change name).
478
478
  - **design.md**: Document technical decisions, architecture, and implementation approach.
479
479
  - **tasks.md**: Break down implementation into checkboxed tasks.
480
480
 
@@ -1785,7 +1785,7 @@ Common artifact patterns:
1785
1785
  **spec-driven schema** (proposal → specs → design → tasks):
1786
1786
  - **proposal.md**: Ask user about the change if not clear. Fill in Why, What Changes, Capabilities, Impact.
1787
1787
  - The Capabilities section is critical - each capability listed will need a spec file.
1788
- - **specs/*.md**: Create one spec per capability listed in the proposal.
1788
+ - **specs/<capability>/spec.md**: Create one spec per capability listed in the proposal's Capabilities section (use the capability name, not the change name).
1789
1789
  - **design.md**: Document technical decisions, architecture, and implementation approach.
1790
1790
  - **tasks.md**: Break down implementation into checkboxed tasks.
1791
1791
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@fission-ai/openspec",
3
- "version": "1.0.1",
3
+ "version": "1.0.2",
4
4
  "description": "AI-native system for spec-driven development",
5
5
  "keywords": [
6
6
  "openspec",
package/schemas/spec-driven/schema.yaml CHANGED
@@ -34,7 +34,9 @@ artifacts:
34
34
  instruction: |
35
35
  Create specification files that define WHAT the system should do.
36
36
 
37
- Create one spec file per capability/feature area in specs/<name>/spec.md.
37
+ Create one spec file per capability listed in the proposal's Capabilities section.
38
+ - New capabilities: use the exact kebab-case name from the proposal (specs/<capability>/spec.md).
39
+ - Modified capabilities: use the existing spec folder name from openspec/specs/<capability>/ when creating the delta spec at specs/<capability>/spec.md.
38
40
 
39
41
  Delta operations (use ## headers):
40
42
  - **ADDED Requirements**: New capabilities
@@ -110,14 +112,17 @@ artifacts:
110
112
 
111
113
  - id: tasks
112
114
  generates: tasks.md
113
- description: Implementation tasks derived from specs and design
115
+ description: Implementation checklist with trackable tasks
114
116
  template: tasks.md
115
117
  instruction: |
116
118
  Create the task list that breaks down the implementation work.
117
119
 
120
+ **IMPORTANT: Follow the template below exactly.** The apply phase parses
121
+ checkbox format to track progress. Tasks not using `- [ ]` won't be tracked.
122
+
118
123
  Guidelines:
119
124
  - Group related tasks under ## numbered headings
120
- - Each task is a checkbox: - [ ] X.Y Task description
125
+ - Each task MUST be a checkbox: `- [ ] X.Y Task description`
121
126
  - Tasks should be small enough to complete in one session
122
127
  - Order tasks by dependency (what must be done first?)
123
128