@fission-ai/openspec 0.1.0 → 0.3.0

package/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2024 OpenSpec Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+

package/README.md

@@ -1,119 +1,327 @@
+<p align="center">
+  <a href="https://github.com/Fission-AI/OpenSpec">
+    <picture>
+      <source srcset="assets/openspec_pixel_dark.svg" media="(prefers-color-scheme: dark)">
+      <source srcset="assets/openspec_pixel_light.svg" media="(prefers-color-scheme: light)">
+      <img src="assets/openspec_pixel_light.svg" alt="OpenSpec logo" height="64">
+    </picture>
+  </a>
+  
+</p>
+<p align="center">Spec-driven development for AI coding assistants.</p>
+<p align="center">
+  <a href="https://github.com/Fission-AI/OpenSpec/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/Fission-AI/OpenSpec/actions/workflows/ci.yml/badge.svg" /></a>
+  <a href="https://www.npmjs.com/package/@fission-ai/openspec"><img alt="npm version" src="https://img.shields.io/npm/v/@fission-ai/openspec?style=flat-square" /></a>
+  <a href="https://nodejs.org/"><img alt="node version" src="https://img.shields.io/node/v/@fission-ai/openspec?style=flat-square" /></a>
+  <a href="./LICENSE"><img alt="License: MIT" src="https://img.shields.io/badge/License-MIT-blue.svg?style=flat-square" /></a>
+  <a href="https://conventionalcommits.org"><img alt="Conventional Commits" src="https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg?style=flat-square" /></a>
+</p>
+
+<p align="center">
+  <img src="assets/openspec_dashboard.png" alt="OpenSpec dashboard preview" width="90%">
+</p>
+
+<p align="center">
+  Follow <a href="https://x.com/0xTab">@0xTab on X</a> for updates.
+</p>
+
 # OpenSpec
 
-A specification-driven development system for maintaining living documentation alongside your code.
+OpenSpec aligns humans and AI coding assistants with spec-driven development so you agree on what to build before any code is written. **No API keys required.**
+
+## Why OpenSpec?
+
+AI coding assistants are powerful but unpredictable when requirements live in chat history. OpenSpec adds a lightweight specification workflow that locks intent before implementation, giving you deterministic, reviewable outputs.
+
+Key outcomes:
+- Human and AI stakeholders agree on specs before work begins.
+- Structured change folders (proposals, tasks, and spec updates) keep scope explicit and auditable.
+- Shared visibility into what's proposed, active, or archived.
+- Works with the AI tools you already use: custom slash commands where supported, context rules everywhere else.
+
+## How It Works
+
+```
+┌────────────────────┐
+│ Draft Change       │
+│ Proposal           │
+└────────┬───────────┘
+         │ share intent with your AI
+         ▼
+┌────────────────────┐
+│ Review & Align     │
+│ (edit specs/tasks) │◀──── feedback loop ──────┐
+└────────┬───────────┘                          │
+         │ approved plan                        │
+         ▼                                      │
+┌────────────────────┐                          │
+│ Implement Tasks    │──────────────────────────┘
+│ (AI writes code)   │
+└────────┬───────────┘
+         │ ship the change
+         ▼
+┌────────────────────┐
+│ Archive & Update   │
+│ Specs (source)     │
+└────────────────────┘
+
+1. Draft a change proposal that captures the spec updates you want.
+2. Review the proposal with your AI assistant until everyone agrees.
+3. Implement tasks that reference the agreed specs.
+4. Archive the change to merge the approved updates back into the source-of-truth specs.
+```
+
+## Getting Started
 
-## Installation
+### Supported AI Tools
+
+#### Native Slash Commands
+These tools have built-in OpenSpec commands. Select the OpenSpec integration when prompted.
+
+| Tool | Commands |
+|------|----------|
+| **Claude Code** | `/openspec:proposal`, `/openspec:apply`, `/openspec:archive` |
+| **Cursor** | `/openspec-proposal`, `/openspec-apply`, `/openspec-archive` |
+
+#### AGENTS.md Compatible
+These tools automatically read workflow instructions from `openspec/AGENTS.md`. Ask them to follow the OpenSpec workflow if they need a reminder. Learn more about the [AGENTS.md convention](https://agents.md/).
+
+| Tools |
+|-------|
+| Codex • Amp • Jules • OpenCode • Gemini CLI • GitHub Copilot • Others |
+
+### Install & Initialize
+
+#### Prerequisites
+- **Node.js >= 20.19.0** - Check your version with `node --version`
+
+#### Step 1: Install the CLI globally
 
 ```bash
-npm install -g openspec
+npm install -g @fission-ai/openspec@latest
 ```
 
-## Quick Start
+Verify installation:
+```bash
+openspec --version
+```
+
+#### Step 2: Initialize OpenSpec in your project
+
+Navigate to your project directory:
+```bash
+cd my-project
+```
 
+Run the initialization:
 ```bash
-# Initialize OpenSpec in your project
 openspec init
+```
+
+**What happens during initialization:**
+- You'll be prompted to select your AI tool (Claude Code, Cursor, etc.)
+- OpenSpec automatically configures slash commands or `AGENTS.md` based on your selection
+- A new `openspec/` directory structure is created in your project
+
+**After setup:**
+- Primary AI tools can trigger `/openspec` workflows without additional configuration
+- Run `openspec list` to verify the setup and view any active changes
+
+### Create Your First Change
+
+Here's a real example showing the complete OpenSpec workflow. This works with any AI tool. Those with native slash commands will recognize the shortcuts automatically.
+
+#### 1. Draft the Proposal
+Start by asking your AI to create a change proposal:
+
+```text
+You: Create an OpenSpec change proposal for adding profile search filters by role and team
+     (Shortcut for tools with slash commands: /openspec:proposal Add profile search filters)
+
+AI:  I'll create an OpenSpec change proposal for profile filters.
+     *Scaffolds openspec/changes/add-profile-filters/ with proposal.md, tasks.md, spec deltas.*
+```
+
+#### 2. Verify & Review
+Check that the change was created correctly and review the proposal:
+
+```bash
+$ openspec list                             # Confirm the change folder exists
+$ openspec validate add-profile-filters     # Validate spec formatting
+$ openspec show add-profile-filters         # Review proposal, tasks, and spec delta
+```
+
+#### 3. Refine the Specs
+Iterate on the specifications until they match your needs:
 
-# Update existing OpenSpec instructions (team-friendly)
-openspec update
+```text
+You: Can you add acceptance criteria for the role and team filters?
+
+AI:  I'll update the spec delta with scenarios for role and team filters.
+     *Edits openspec/changes/add-profile-filters/specs/profile/spec.md and tasks.md.*
+```
 
-# List specs or changes
-openspec spec list        # specs (IDs by default; use --long for details)
-openspec change list      # changes (IDs by default; use --long for details)
+#### 4. Implement the Change
+Once specs look good, start implementation:
 
-# Show differences between specs and proposed changes
-openspec diff [change-name]
+```text
+You: The specs look good. Let's implement this change.
+     (Shortcut for tools with slash commands: /openspec:apply add-profile-filters)
 
-# Archive completed changes
-openspec archive [change-name]
+AI:  I'll work through the tasks in the add-profile-filters change.
+     *Implements tasks from openspec/changes/add-profile-filters/tasks.md*
+     *Marks tasks complete: Task 1.1 ✓, Task 1.2 ✓, Task 2.1 ✓...*
 ```
 
-## Commands
+#### 5. Archive the Completed Change
+After implementation is complete, archive the change:
 
-### `openspec init`
+```text
+AI:  All tasks are complete. The implementation is ready.
 
-Initializes OpenSpec in your project by creating:
-- `openspec/` directory structure
-- `openspec/README.md` with OpenSpec instructions
-- AI tool configuration files (based on your selection)
+You: Please archive the change
+     (Shortcut for tools with slash commands: /openspec:archive add-profile-filters)
 
-### `openspec update`
+AI:  I'll archive the add-profile-filters change.
+     *Runs: openspec archive add-profile-filters*
+     ✓ Change archived successfully. Specs updated. Ready for the next feature!
+```
 
-Updates OpenSpec instructions to the latest version. This command is **team-friendly** and only updates files that already exist:
+Or run the command yourself in terminal:
+```bash
+$ openspec archive add-profile-filters  # Archive the completed change
+```
 
-- Always updates `openspec/README.md` with the latest OpenSpec instructions
-- **Only updates existing AI tool configuration files** (e.g., CLAUDE.md, CURSOR.md)
-- **Never creates new AI tool configuration files**
-- Preserves content outside of OpenSpec markers in AI tool files
+**Note:** Tools with native slash commands (Claude Code, Cursor) can use the shortcuts shown. All other tools work with natural language requests to "create an OpenSpec proposal", "apply the OpenSpec change", or "archive the change".
 
-This allows team members to use different AI tools without conflicts. Each developer can maintain their preferred AI tool configuration file, and `openspec update` will respect their choice.
+## Command Reference
 
-### `openspec spec`
+```bash
+openspec list               # View active change folders
+openspec view               # Interactive dashboard of specs and changes
+openspec show <change>      # Display change details (proposal, tasks, spec updates)
+openspec validate <change>  # Check spec formatting and structure
+openspec archive <change>   # Move a completed change into archive/
+```
+
+## Example: How AI Creates OpenSpec Files
 
-Manage and view specifications.
+When you ask your AI assistant to "add two-factor authentication", it creates:
 
-Examples:
-- `openspec spec show <spec-id>`
-  - Text mode: prints raw `spec.md` content
-  - JSON mode (`--json`): returns minimal, stable shape
-    - Filters are JSON-only: `--requirements`, `--no-scenarios`, `-r/--requirement <1-based>`
-- `openspec spec list`
-  - Prints IDs only by default
-  - Use `--long` to include `title` and `[requirements N]`
-- `openspec spec validate <spec-id>`
-  - Text: human-readable summary to stdout/stderr
-  - `--json` for structured report
+```
+openspec/
+├── specs/
+│   └── auth/
+│       └── spec.md           # Current auth spec (if exists)
+└── changes/
+    └── add-2fa/              # AI creates this entire structure
+        ├── proposal.md       # Why and what changes
+        ├── tasks.md          # Implementation checklist
+        ├── design.md         # Technical decisions (optional)
+        └── specs/
+            └── auth/
+                └── spec.md   # Delta showing additions
+```
 
-### `openspec change`
+### AI-Generated Spec (created in `openspec/specs/auth/spec.md`):
 
-Manage and view change proposals.
+```markdown
+# Auth Specification
 
-Examples:
-- `openspec change show <change-id>`
-  - Text mode: prints raw `proposal.md` content
-  - JSON mode (`--json`): `{ id, title, deltaCount, deltas }`
-  - Filtering is JSON-only: `--deltas-only` (alias: `--requirements-only`, deprecated)
-- `openspec change list`
-  - Prints IDs only by default
-  - Use `--long` to include `title` and counts `[deltas N] [tasks x/y]`
-- `openspec change validate <change-id>`
-  - Text: human-readable result
-  - `--json` for structured report
+## Purpose
+Authentication and session management.
 
-### `openspec diff [change-name]`
+## Requirements
+### Requirement: User Authentication
+The system SHALL issue a JWT on successful login.
 
-Shows the differences between current specs and proposed changes:
-- Displays a unified diff format
-- Helps review what will change before implementation
-- Useful for pull request reviews
+#### Scenario: Valid credentials
+- WHEN a user submits valid credentials
+- THEN a JWT is returned
+```
 
-### `openspec archive [change-name]`
+### AI-Generated Change Delta (created in `openspec/changes/add-2fa/specs/auth/spec.md`):
 
-Archives a completed change:
-- Moves change from `openspec/changes/` to `openspec/changes/archive/`
-- Adds a date prefix to the archived change
-- Updates specs to reflect the new state
-- Use `--skip-specs` to archive without updating specs (for abandoned changes)
+```markdown
+# Delta for Auth
 
-## Team Collaboration
+## ADDED Requirements
+### Requirement: Two-Factor Authentication
+The system MUST require a second factor during login.
 
-OpenSpec is designed for team collaboration:
+#### Scenario: OTP required
+- WHEN a user submits valid credentials
+- THEN an OTP challenge is required
+```
 
-1. **AI Tool Flexibility**: Each team member can use their preferred AI assistant (Claude, Cursor, etc.)
-2. **Non-Invasive Updates**: The `update` command only modifies existing files, never forcing tools on team members
-3. **Specification Sharing**: The `openspec/` directory contains shared specifications that all team members work from
-4. **Change Tracking**: Proposed changes are visible to all team members for review before implementation
+### AI-Generated Tasks (created in `openspec/changes/add-2fa/tasks.md`):
 
-## Contributing
+```markdown
+## 1. Database Setup
+- [ ] 1.1 Add OTP secret column to users table
+- [ ] 1.2 Create OTP verification logs table
 
-See `openspec/specs/` for the current system specifications and `openspec/changes/` for pending improvements.
+## 2. Backend Implementation  
+- [ ] 2.1 Add OTP generation endpoint
+- [ ] 2.2 Modify login flow to require OTP
+- [ ] 2.3 Add OTP verification endpoint
 
-## Notes
+## 3. Frontend Updates
+- [ ] 3.1 Create OTP input component
+- [ ] 3.2 Update login flow UI
+```
+
+**Important:** You don't create these files manually. Your AI assistant generates them based on your requirements and the existing codebase.
+
+## Understanding OpenSpec Files
+
+### Delta Format
+
+Deltas are "patches" that show how specs change:
+
+- **`## ADDED Requirements`** - New capabilities
+- **`## MODIFIED Requirements`** - Changed behavior (include complete updated text)
+- **`## REMOVED Requirements`** - Deprecated features
+
+**Format requirements:**
+- Use `### Requirement: <name>` for headers
+- Every requirement needs at least one `#### Scenario:` block
+- Use SHALL/MUST in requirement text
+
+## How OpenSpec Compares
+
+### vs. Kiro.dev
+OpenSpec groups every change for a feature in one folder (`openspec/changes/feature-name/`), making it easy to track related specs, tasks, and designs together. Kiro spreads updates across multiple spec folders, which can make feature tracking harder.
+
+### vs. No Specs
+Without specs, AI coding assistants generate code from vague prompts, often missing requirements or adding unwanted features. OpenSpec brings predictability by agreeing on the desired behavior before any code is written.
+
+## Team Adoption
+
+1. **Initialize OpenSpec** – Run `openspec init` in your repo.
+2. **Start with new features** – Ask your AI to capture upcoming work as change proposals.
+3. **Grow incrementally** – Each change archives into living specs that document your system.
+4. **Stay flexible** – Different teammates can use Claude Code, Cursor, or any AGENTS.md-compatible tool while sharing the same specs.
+
+Run `openspec update` whenever someone switches tools so your agents pick up the latest instructions and slash-command bindings.
+
+## Updating OpenSpec
+
+1. **Upgrade the package**
+   ```bash
+   npm install -g @fission-ai/openspec@latest
+   ```
+2. **Refresh agent instructions**
+   - Run `openspec update` inside each project to regenerate AI guidance and ensure the latest slash commands are active.
+
+## Contributing
 
-- The legacy `openspec list` command is deprecated. Use `openspec spec list` and `openspec change list`.
-- Text output is raw-first (no formatting or filtering). Prefer `--json` for tooling-friendly output.
-- Global `--no-color` disables ANSI colors and respects `NO_COLOR`.
+- Install dependencies: `pnpm install`
+- Build: `pnpm run build`
+- Test: `pnpm test`
+- Develop CLI locally: `pnpm run dev` or `pnpm run dev:cli`
+- Conventional commits (one-line): `type(scope): subject`
 
 ## License
 
-MIT
+MIT

package/dist/cli/index.js

@@ -5,9 +5,9 @@ import path from 'path';
 import { promises as fs } from 'fs';
 import { InitCommand } from '../core/init.js';
 import { UpdateCommand } from '../core/update.js';
-import { DiffCommand } from '../core/diff.js';
 import { ListCommand } from '../core/list.js';
 import { ArchiveCommand } from '../core/archive.js';
+import { ViewCommand } from '../core/view.js';
 import { registerSpecCommand } from '../commands/spec.js';
 import { ChangeCommand } from '../commands/change.js';
 import { ValidateCommand } from '../commands/validate.js';
@@ -78,12 +78,15 @@ program
     }
 });
 program
-    .command('diff [change-name]')
-    .description('Show differences between proposed spec changes and current specs (includes validation warnings)')
-    .action(async (changeName) => {
+    .command('list')
+    .description('List items (changes by default). Use --specs to list specs.')
+    .option('--specs', 'List specs instead of changes')
+    .option('--changes', 'List changes explicitly (default)')
+    .action(async (options) => {
     try {
-        const diffCommand = new DiffCommand();
-        await diffCommand.execute(changeName);
+        const listCommand = new ListCommand();
+        const mode = options?.specs ? 'specs' : 'changes';
+        await listCommand.execute('.', mode);
     }
     catch (error) {
         console.log(); // Empty line for spacing
@@ -92,15 +95,12 @@ program
     }
 });
 program
-    .command('list')
-    .description('List items (changes by default). Use --specs to list specs.')
-    .option('--specs', 'List specs instead of changes')
-    .option('--changes', 'List changes explicitly (default)')
-    .action(async (options) => {
+    .command('view')
+    .description('Display an interactive dashboard of specs and changes')
+    .action(async () => {
     try {
-        const listCommand = new ListCommand();
-        const mode = options?.specs ? 'specs' : 'changes';
-        await listCommand.execute('.', mode);
+        const viewCommand = new ViewCommand();
+        await viewCommand.execute('.');
     }
     catch (error) {
         console.log(); // Empty line for spacing

package/dist/core/config.d.ts

@@ -1,14 +1,16 @@
 export declare const OPENSPEC_DIR_NAME = "openspec";
-export interface OpenSpecConfig {
-    aiTools: string[];
-}
 export declare const OPENSPEC_MARKERS: {
     start: string;
     end: string;
 };
-export declare const AI_TOOLS: {
+export interface OpenSpecConfig {
+    aiTools: string[];
+}
+export interface AIToolOption {
     name: string;
     value: string;
     available: boolean;
-}[];
+    successLabel?: string;
+}
+export declare const AI_TOOLS: AIToolOption[];
 //# sourceMappingURL=config.d.ts.map

package/dist/core/config.js

@@ -4,9 +4,8 @@ export const OPENSPEC_MARKERS = {
     end: '<!-- OPENSPEC:END -->'
 };
 export const AI_TOOLS = [
-    { name: 'Claude Code', value: 'claude', available: true },
-    { name: 'Cursor', value: 'cursor', available: false },
-    { name: 'Aider', value: 'aider', available: false },
-    { name: 'Continue', value: 'continue', available: false }
+    { name: 'Claude Code (✅ OpenSpec custom slash commands available)', value: 'claude', available: true, successLabel: 'Claude Code' },
+    { name: 'Cursor (✅ OpenSpec custom slash commands available)', value: 'cursor', available: true, successLabel: 'Cursor' },
+    { name: 'AGENTS.md (works with Codex, Amp, Copilot, …)', value: 'agents', available: true, successLabel: 'your AGENTS.md-compatible assistant' }
 ];
 //# sourceMappingURL=config.js.map

package/dist/core/configurators/agents.d.ts

@@ -0,0 +1,8 @@
+import { ToolConfigurator } from './base.js';
+export declare class AgentsStandardConfigurator implements ToolConfigurator {
+    name: string;
+    configFileName: string;
+    isAvailable: boolean;
+    configure(projectPath: string, _openspecDir: string): Promise<void>;
+}
+//# sourceMappingURL=agents.d.ts.map

package/dist/core/configurators/agents.js

@@ -0,0 +1,15 @@
+import path from 'path';
+import { FileSystemUtils } from '../../utils/file-system.js';
+import { TemplateManager } from '../templates/index.js';
+import { OPENSPEC_MARKERS } from '../config.js';
+export class AgentsStandardConfigurator {
+    name = 'AGENTS.md standard';
+    configFileName = 'AGENTS.md';
+    isAvailable = true;
+    async configure(projectPath, _openspecDir) {
+        const filePath = path.join(projectPath, this.configFileName);
+        const content = TemplateManager.getAgentsStandardTemplate();
+        await FileSystemUtils.updateFileWithMarkers(filePath, content, OPENSPEC_MARKERS.start, OPENSPEC_MARKERS.end);
+    }
+}
+//# sourceMappingURL=agents.js.map

package/dist/core/configurators/registry.js

@@ -1,10 +1,13 @@
 import { ClaudeConfigurator } from './claude.js';
+import { AgentsStandardConfigurator } from './agents.js';
 export class ToolRegistry {
     static tools = new Map();
     static {
         const claudeConfigurator = new ClaudeConfigurator();
+        const agentsConfigurator = new AgentsStandardConfigurator();
         // Register with the ID that matches the checkbox value
         this.tools.set('claude', claudeConfigurator);
+        this.tools.set('agents', agentsConfigurator);
     }
     static register(tool) {
         this.tools.set(tool.name.toLowerCase().replace(/\s+/g, '-'), tool);

package/dist/core/configurators/slash/base.d.ts

@@ -0,0 +1,17 @@
+import { SlashCommandId } from '../../templates/index.js';
+export interface SlashCommandTarget {
+    id: SlashCommandId;
+    path: string;
+    kind: 'slash';
+}
+export declare abstract class SlashCommandConfigurator {
+    abstract readonly toolId: string;
+    abstract readonly isAvailable: boolean;
+    getTargets(): SlashCommandTarget[];
+    generateAll(projectPath: string, _openspecDir: string): Promise<string[]>;
+    updateExisting(projectPath: string, _openspecDir: string): Promise<string[]>;
+    protected abstract getRelativePath(id: SlashCommandId): string;
+    protected abstract getFrontmatter(id: SlashCommandId): string | undefined;
+    private updateBody;
+}
+//# sourceMappingURL=base.d.ts.map

package/dist/core/configurators/slash/base.js

@@ -0,0 +1,61 @@
+import path from 'path';
+import { FileSystemUtils } from '../../../utils/file-system.js';
+import { TemplateManager } from '../../templates/index.js';
+import { OPENSPEC_MARKERS } from '../../config.js';
+const ALL_COMMANDS = ['proposal', 'apply', 'archive'];
+export class SlashCommandConfigurator {
+    getTargets() {
+        return ALL_COMMANDS.map((id) => ({
+            id,
+            path: this.getRelativePath(id),
+            kind: 'slash'
+        }));
+    }
+    async generateAll(projectPath, _openspecDir) {
+        const createdOrUpdated = [];
+        for (const target of this.getTargets()) {
+            const body = TemplateManager.getSlashCommandBody(target.id).trim();
+            const filePath = path.join(projectPath, target.path);
+            if (await FileSystemUtils.fileExists(filePath)) {
+                await this.updateBody(filePath, body);
+            }
+            else {
+                const frontmatter = this.getFrontmatter(target.id);
+                const sections = [];
+                if (frontmatter) {
+                    sections.push(frontmatter.trim());
+                }
+                sections.push(`${OPENSPEC_MARKERS.start}\n${body}\n${OPENSPEC_MARKERS.end}`);
+                const content = sections.join('\n') + '\n';
+                await FileSystemUtils.writeFile(filePath, content);
+            }
+            createdOrUpdated.push(target.path);
+        }
+        return createdOrUpdated;
+    }
+    async updateExisting(projectPath, _openspecDir) {
+        const updated = [];
+        for (const target of this.getTargets()) {
+            const filePath = path.join(projectPath, target.path);
+            if (await FileSystemUtils.fileExists(filePath)) {
+                const body = TemplateManager.getSlashCommandBody(target.id).trim();
+                await this.updateBody(filePath, body);
+                updated.push(target.path);
+            }
+        }
+        return updated;
+    }
+    async updateBody(filePath, body) {
+        const content = await FileSystemUtils.readFile(filePath);
+        const startIndex = content.indexOf(OPENSPEC_MARKERS.start);
+        const endIndex = content.indexOf(OPENSPEC_MARKERS.end);
+        if (startIndex === -1 || endIndex === -1 || endIndex <= startIndex) {
+            throw new Error(`Missing OpenSpec markers in ${filePath}`);
+        }
+        const before = content.slice(0, startIndex + OPENSPEC_MARKERS.start.length);
+        const after = content.slice(endIndex);
+        const updatedContent = `${before}\n${body}\n${after}`;
+        await FileSystemUtils.writeFile(filePath, updatedContent);
+    }
+}
+//# sourceMappingURL=base.js.map

package/dist/core/configurators/slash/claude.d.ts

@@ -0,0 +1,9 @@
+import { SlashCommandConfigurator } from './base.js';
+import { SlashCommandId } from '../../templates/index.js';
+export declare class ClaudeSlashCommandConfigurator extends SlashCommandConfigurator {
+    readonly toolId = "claude";
+    readonly isAvailable = true;
+    protected getRelativePath(id: SlashCommandId): string;
+    protected getFrontmatter(id: SlashCommandId): string;
+}
+//# sourceMappingURL=claude.d.ts.map