diff --git a/.claude/commands/opsx/apply.md b/.claude/commands/opsx/apply.md index f6b6e5b..645bbdb 100644 --- a/.claude/commands/opsx/apply.md +++ b/.claude/commands/opsx/apply.md @@ -25,7 +25,7 @@ Implement tasks from an OpenSpec change. openspec status --change "" --json ``` Parse the JSON to understand: - - `schemaName`: The workflow being used (e.g., "spec-driven", "tdd") + - `schemaName`: The workflow being used (e.g., "spec-driven") - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others) 3. **Get apply instructions** @@ -50,7 +50,6 @@ Implement tasks from an OpenSpec change. Read the files listed in `contextFiles` from the apply instructions output. The files depend on the schema being used: - **spec-driven**: proposal, specs, design, tasks - - **tdd**: spec, tests, implementation, docs - Other schemas: follow the contextFiles from CLI output 5. **Show current progress** diff --git a/.claude/commands/opsx/continue.md b/.claude/commands/opsx/continue.md index 9a61279..49daaa7 100644 --- a/.claude/commands/opsx/continue.md +++ b/.claude/commands/opsx/continue.md @@ -30,7 +30,7 @@ Continue working on a change by creating the next artifact. openspec status --change "" --json ``` Parse the JSON to understand current state. The response includes: - - `schemaName`: The workflow schema being used (e.g., "spec-driven", "tdd") + - `schemaName`: The workflow schema being used (e.g., "spec-driven") - `artifacts`: Array of artifacts with their status ("done", "ready", "blocked") - `isComplete`: Boolean indicating if all artifacts are complete @@ -96,16 +96,10 @@ Common artifact patterns: **spec-driven schema** (proposal → specs → design → tasks): - **proposal.md**: Ask user about the change if not clear. Fill in Why, What Changes, Capabilities, Impact. - The Capabilities section is critical - each capability listed will need a spec file. -- **specs/*.md**: Create one spec per capability listed in the proposal. +- **specs//spec.md**: Create one spec per capability listed in the proposal's Capabilities section (use the capability name, not the change name). - **design.md**: Document technical decisions, architecture, and implementation approach. - **tasks.md**: Break down implementation into checkboxed tasks. -**tdd schema** (spec → tests → implementation → docs): -- **spec.md**: Feature specification defining what to build. -- **tests/*.test.ts**: Write tests BEFORE implementation (TDD red phase). -- **src/*.ts**: Implement to make tests pass (TDD green phase). -- **docs/*.md**: Document the implemented feature. - For other schemas, follow the `instruction` field from the CLI output. **Guardrails** diff --git a/.claude/commands/opsx/new.md b/.claude/commands/opsx/new.md index 3b5ce01..ef26cfa 100644 --- a/.claude/commands/opsx/new.md +++ b/.claude/commands/opsx/new.md @@ -25,7 +25,6 @@ Start a new change using the experimental artifact-driven approach. Use the default schema (omit `--schema`) unless the user explicitly requests a different workflow. **Use a different schema only if the user mentions:** - - "tdd" or "test-driven" → use `--schema tdd` - A specific schema name → use `--schema ` - "show workflows" or "what workflows" → run `openspec schemas --json` and let them choose diff --git a/.claude/commands/opsx/onboard.md b/.claude/commands/opsx/onboard.md index 0c4116e..e15790e 100644 --- a/.claude/commands/opsx/onboard.md +++ b/.claude/commands/opsx/onboard.md @@ -412,7 +412,7 @@ The change is implemented! One more step—let's archive it. ``` ## Archiving -When a change is complete, we archive it. This moves it from `openspec/changes/` to `openspec/archive/YYYY-MM-DD--/`. +When a change is complete, we archive it. This moves it from `openspec/changes/` to `openspec/changes/archive/YYYY-MM-DD-/`. Archived changes become your project's decision history—you can always find them later to understand why something was built a certain way. ``` @@ -424,7 +424,7 @@ openspec archive "" **SHOW:** ``` -Archived to: `openspec/archive/YYYY-MM-DD--/` +Archived to: `openspec/changes/archive/YYYY-MM-DD-/` The change is now part of your project's history. The code is in your codebase, the decision record is preserved. ``` diff --git a/.claude/commands/opsx/verify.md b/.claude/commands/opsx/verify.md index a527a15..82ab63f 100644 --- a/.claude/commands/opsx/verify.md +++ b/.claude/commands/opsx/verify.md @@ -26,7 +26,7 @@ Verify that an implementation matches the change artifacts (specs, tasks, design openspec status --change "" --json ``` Parse the JSON to understand: - - `schemaName`: The workflow being used (e.g., "spec-driven", "tdd") + - `schemaName`: The workflow being used (e.g., "spec-driven") - Which artifacts exist for this change 3. **Get the change directory and load artifacts** diff --git a/.claude/skills/openspec-apply-change/SKILL.md b/.claude/skills/openspec-apply-change/SKILL.md index 8c79a44..bc95df4 100644 --- a/.claude/skills/openspec-apply-change/SKILL.md +++ b/.claude/skills/openspec-apply-change/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: "1.0" - generatedBy: "1.0.0" + generatedBy: "1.0.2" --- Implement tasks from an OpenSpec change. @@ -29,7 +29,7 @@ Implement tasks from an OpenSpec change. openspec status --change "" --json ``` Parse the JSON to understand: - - `schemaName`: The workflow being used (e.g., "spec-driven", "tdd") + - `schemaName`: The workflow being used (e.g., "spec-driven") - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others) 3. **Get apply instructions** @@ -54,7 +54,6 @@ Implement tasks from an OpenSpec change. Read the files listed in `contextFiles` from the apply instructions output. The files depend on the schema being used: - **spec-driven**: proposal, specs, design, tasks - - **tdd**: spec, tests, implementation, docs - Other schemas: follow the contextFiles from CLI output 5. **Show current progress** diff --git a/.claude/skills/openspec-archive-change/SKILL.md b/.claude/skills/openspec-archive-change/SKILL.md index 4a6f03b..9ea63e8 100644 --- a/.claude/skills/openspec-archive-change/SKILL.md +++ b/.claude/skills/openspec-archive-change/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: "1.0" - generatedBy: "1.0.0" + generatedBy: "1.0.2" --- Archive a completed change in the experimental workflow. diff --git a/.claude/skills/openspec-bulk-archive-change/SKILL.md b/.claude/skills/openspec-bulk-archive-change/SKILL.md index 90c0a44..5ce056a 100644 --- a/.claude/skills/openspec-bulk-archive-change/SKILL.md +++ b/.claude/skills/openspec-bulk-archive-change/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: "1.0" - generatedBy: "1.0.0" + generatedBy: "1.0.2" --- Archive multiple completed changes in a single operation. diff --git a/.claude/skills/openspec-continue-change/SKILL.md b/.claude/skills/openspec-continue-change/SKILL.md index 10a72c0..79aaac4 100644 --- a/.claude/skills/openspec-continue-change/SKILL.md +++ b/.claude/skills/openspec-continue-change/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: "1.0" - generatedBy: "1.0.0" + generatedBy: "1.0.2" --- Continue working on a change by creating the next artifact. @@ -34,7 +34,7 @@ Continue working on a change by creating the next artifact. openspec status --change "" --json ``` Parse the JSON to understand current state. The response includes: - - `schemaName`: The workflow schema being used (e.g., "spec-driven", "tdd") + - `schemaName`: The workflow schema being used (e.g., "spec-driven") - `artifacts`: Array of artifacts with their status ("done", "ready", "blocked") - `isComplete`: Boolean indicating if all artifacts are complete @@ -100,16 +100,10 @@ Common artifact patterns: **spec-driven schema** (proposal → specs → design → tasks): - **proposal.md**: Ask user about the change if not clear. Fill in Why, What Changes, Capabilities, Impact. - The Capabilities section is critical - each capability listed will need a spec file. -- **specs/*.md**: Create one spec per capability listed in the proposal. +- **specs//spec.md**: Create one spec per capability listed in the proposal's Capabilities section (use the capability name, not the change name). - **design.md**: Document technical decisions, architecture, and implementation approach. - **tasks.md**: Break down implementation into checkboxed tasks. -**tdd schema** (spec → tests → implementation → docs): -- **spec.md**: Feature specification defining what to build. -- **tests/*.test.ts**: Write tests BEFORE implementation (TDD red phase). -- **src/*.ts**: Implement to make tests pass (TDD green phase). -- **docs/*.md**: Document the implemented feature. - For other schemas, follow the `instruction` field from the CLI output. **Guardrails** diff --git a/.claude/skills/openspec-explore/SKILL.md b/.claude/skills/openspec-explore/SKILL.md index f50e7da..49d051d 100644 --- a/.claude/skills/openspec-explore/SKILL.md +++ b/.claude/skills/openspec-explore/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: "1.0" - generatedBy: "1.0.0" + generatedBy: "1.0.2" --- Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes. diff --git a/.claude/skills/openspec-ff-change/SKILL.md b/.claude/skills/openspec-ff-change/SKILL.md index 7d82708..64f058c 100644 --- a/.claude/skills/openspec-ff-change/SKILL.md +++ b/.claude/skills/openspec-ff-change/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: "1.0" - generatedBy: "1.0.0" + generatedBy: "1.0.2" --- Fast-forward through artifact creation - generate everything needed to start implementation in one go. diff --git a/.claude/skills/openspec-new-change/SKILL.md b/.claude/skills/openspec-new-change/SKILL.md index 75f28c5..53d96b9 100644 --- a/.claude/skills/openspec-new-change/SKILL.md +++ b/.claude/skills/openspec-new-change/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: "1.0" - generatedBy: "1.0.0" + generatedBy: "1.0.2" --- Start a new change using the experimental artifact-driven approach. @@ -29,7 +29,6 @@ Start a new change using the experimental artifact-driven approach. Use the default schema (omit `--schema`) unless the user explicitly requests a different workflow. **Use a different schema only if the user mentions:** - - "tdd" or "test-driven" → use `--schema tdd` - A specific schema name → use `--schema ` - "show workflows" or "what workflows" → run `openspec schemas --json` and let them choose @@ -49,7 +48,7 @@ Start a new change using the experimental artifact-driven approach. This shows which artifacts need to be created and which are ready (dependencies satisfied). 5. **Get instructions for the first artifact** - The first artifact depends on the schema (e.g., `proposal` for spec-driven, `spec` for tdd). + The first artifact depends on the schema (e.g., `proposal` for spec-driven). Check the status output to find the first artifact with status "ready". ```bash openspec instructions --change "" diff --git a/.claude/skills/openspec-onboard/SKILL.md b/.claude/skills/openspec-onboard/SKILL.md index b055905..40080aa 100644 --- a/.claude/skills/openspec-onboard/SKILL.md +++ b/.claude/skills/openspec-onboard/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: "1.0" - generatedBy: "1.0.0" + generatedBy: "1.0.2" --- Guide the user through their first complete OpenSpec workflow cycle. This is a teaching experience—you'll do real work in their codebase while explaining each step. @@ -416,7 +416,7 @@ The change is implemented! One more step—let's archive it. ``` ## Archiving -When a change is complete, we archive it. This moves it from `openspec/changes/` to `openspec/archive/YYYY-MM-DD--/`. +When a change is complete, we archive it. This moves it from `openspec/changes/` to `openspec/changes/archive/YYYY-MM-DD-/`. Archived changes become your project's decision history—you can always find them later to understand why something was built a certain way. ``` @@ -428,7 +428,7 @@ openspec archive "" **SHOW:** ``` -Archived to: `openspec/archive/YYYY-MM-DD--/` +Archived to: `openspec/changes/archive/YYYY-MM-DD-/` The change is now part of your project's history. The code is in your codebase, the decision record is preserved. ``` diff --git a/.claude/skills/openspec-sync-specs/SKILL.md b/.claude/skills/openspec-sync-specs/SKILL.md index fa874f4..632681c 100644 --- a/.claude/skills/openspec-sync-specs/SKILL.md +++ b/.claude/skills/openspec-sync-specs/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: "1.0" - generatedBy: "1.0.0" + generatedBy: "1.0.2" --- Sync delta specs from a change to main specs. diff --git a/.claude/skills/openspec-verify-change/SKILL.md b/.claude/skills/openspec-verify-change/SKILL.md index 067c845..21cbc50 100644 --- a/.claude/skills/openspec-verify-change/SKILL.md +++ b/.claude/skills/openspec-verify-change/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: "1.0" - generatedBy: "1.0.0" + generatedBy: "1.0.2" --- Verify that an implementation matches the change artifacts (specs, tasks, design). @@ -30,7 +30,7 @@ Verify that an implementation matches the change artifacts (specs, tasks, design openspec status --change "" --json ``` Parse the JSON to understand: - - `schemaName`: The workflow being used (e.g., "spec-driven", "tdd") + - `schemaName`: The workflow being used (e.g., "spec-driven") - Which artifacts exist for this change 3. **Get the change directory and load artifacts**