@dccxx/auggiegw 1.0.24 → 1.0.26

package/openspec/changes/archive/2026-02-01-add-opencode-agent-support/specs/kit-command/spec.md

@@ -0,0 +1,157 @@
+## MODIFIED Requirements
+
+### Requirement: Command Invocation
+WHEN the user runs `auggiegw kit <kit-id>`, THE SYSTEM SHALL prompt the user to select target AI tool (including OpenCode) and installation scope, then fetch the kit from the public API endpoint.
+
+#### Scenario: User runs kit command without flags
+- **WHEN** user runs `auggiegw kit <kit-id>` without any flags
+- **THEN** system displays interactive prompt for target selection with options: Claude, Augment, OpenCode, Both
+- **THEN** system displays interactive prompt for scope selection
+- **THEN** system fetches the kit from the public API endpoint
+
+#### Scenario: User runs kit command with flags
+- **WHEN** user runs `auggiegw kit <kit-id> --target claude --scope user`
+- **THEN** system skips prompts and uses provided flag values
+- **THEN** system fetches the kit from the public API endpoint
+
+#### Scenario: User selects OpenCode target via flag
+- **WHEN** user runs `auggiegw kit <kit-id> --target opencode`
+- **THEN** system skips target prompt and uses OpenCode as target
+- **THEN** system displays interactive prompt for scope selection
+- **THEN** system fetches the kit from the public API endpoint
+
+#### Scenario: User selects multiple targets via flag
+- **WHEN** user runs `auggiegw kit <kit-id> --target claude,opencode`
+- **THEN** system parses comma-separated targets
+- **THEN** system installs to both Claude and OpenCode
+- **THEN** system fetches the kit from the public API endpoint
+
+#### Scenario: Missing kit-id argument
+- **WHEN** kit-id argument is missing
+- **THEN** system displays "Error: Kit ID is required" and usage message, and exits with code 1
+
+### Requirement: Prompt Installation
+WHEN processing prompts, THE SYSTEM SHALL create the target directories based on user selection (including OpenCode) and save markdown files with YAML frontmatter to the selected locations.
+
+#### Scenario: Install prompts to Claude user level
+- **WHEN** user selects target "Claude" and scope "User level"
+- **THEN** system creates directory `~/.claude/commands/` if it does not exist
+- **THEN** for each prompt in the kit, system saves a markdown file to `~/.claude/commands/{command}.md` with YAML frontmatter containing `description` and `type: "manual"` fields
+
+#### Scenario: Install prompts to Augment project level
+- **WHEN** user selects target "Augment" and scope "Project level"
+- **THEN** system creates directory `./.augment/commands/` if it does not exist
+- **THEN** for each prompt in the kit, system saves a markdown file to `./.augment/commands/{command}.md` with YAML frontmatter containing `description` and `type: "manual"` fields
+
+#### Scenario: Install prompts to OpenCode user level
+- **WHEN** user selects target "OpenCode" and scope "User level"
+- **THEN** system creates directory `~/.config/opencode/commands/` if it does not exist
+- **THEN** for each prompt in the kit, system saves a markdown file to `~/.config/opencode/commands/{command}.md` with YAML frontmatter containing `description` and `type: "manual"` fields
+
+#### Scenario: Install prompts to OpenCode project level
+- **WHEN** user selects target "OpenCode" and scope "Project level"
+- **THEN** system creates directory `./.opencode/commands/` if it does not exist
+- **THEN** for each prompt in the kit, system saves a markdown file to `./.opencode/commands/{command}.md` with YAML frontmatter containing `description` and `type: "manual"` fields
+
+#### Scenario: Install prompts to both targets at user level
+- **WHEN** user selects target "Both" and scope "User level"
+- **THEN** system creates directories `~/.augment/commands/` and `~/.claude/commands/` if they do not exist
+- **THEN** for each prompt in the kit, system saves markdown files to both `~/.augment/commands/{command}.md` and `~/.claude/commands/{command}.md`
+
+#### Scenario: Install prompts to multiple targets including OpenCode
+- **WHEN** user selects targets "Claude" and "OpenCode" via comma-separated flag and scope "User level"
+- **THEN** system creates directories `~/.claude/commands/` and `~/.config/opencode/commands/` if they do not exist
+- **THEN** for each prompt in the kit, system saves markdown files to both directories
+
+#### Scenario: Overwrite existing prompt files
+- **WHEN** a prompt file with the same filename already exists
+- **THEN** system overwrites the existing file without confirmation
+
+#### Scenario: Prompt file save failure
+- **WHEN** a prompt file fails to save
+- **THEN** system throws an error with message "Failed to save prompt file for command '{command}': {error}"
+
+#### Scenario: Partial save failure with multiple targets
+- **WHEN** user selects multiple targets and a prompt file fails to save to one directory
+- **THEN** system still attempts to save to the other directories before throwing an error
+
+### Requirement: Subagent Installation
+WHEN processing subagents, THE SYSTEM SHALL create the target directories based on user selection (including OpenCode) and save markdown files with appropriate YAML frontmatter to the selected locations.
+
+#### Scenario: Install subagents to Claude user level
+- **WHEN** user selects target "Claude" and scope "User level"
+- **THEN** system creates directory `~/.claude/agents/` if it does not exist
+- **THEN** for each subagent in the kit, system saves a markdown file to `~/.claude/agents/{name}.md` with YAML frontmatter containing `name`, `description`, `model`, and `color` fields
+
+#### Scenario: Install subagents to Augment project level
+- **WHEN** user selects target "Augment" and scope "Project level"
+- **THEN** system creates directory `./.augment/agents/` if it does not exist
+- **THEN** for each subagent in the kit, system saves a markdown file to `./.augment/agents/{name}.md` with YAML frontmatter containing `name`, `description`, `model`, and `color` fields
+
+#### Scenario: Install subagents to OpenCode user level
+- **WHEN** user selects target "OpenCode" and scope "User level"
+- **THEN** system creates directory `~/.config/opencode/agents/` if it does not exist
+- **THEN** for each subagent in the kit, system saves a markdown file to `~/.config/opencode/agents/{name}.md` with YAML frontmatter containing `mode: subagent`, `name`, `description`, and `color` fields
+- **THEN** system excludes `model` field from YAML frontmatter
+
+#### Scenario: Install subagents to OpenCode project level
+- **WHEN** user selects target "OpenCode" and scope "Project level"
+- **THEN** system creates directory `./.opencode/agents/` if it does not exist
+- **THEN** for each subagent in the kit, system saves a markdown file to `./.opencode/agents/{name}.md` with YAML frontmatter containing `mode: subagent`, `name`, `description`, and `color` fields
+- **THEN** system excludes `model` field from YAML frontmatter
+
+#### Scenario: Install subagents to both targets at user level
+- **WHEN** user selects target "Both" and scope "User level"
+- **THEN** system creates directories `~/.augment/agents/` and `~/.claude/agents/` if they do not exist
+- **THEN** for each subagent in the kit, system saves markdown files to both `~/.augment/agents/{name}.md` and `~/.claude/agents/{name}.md`
+
+#### Scenario: Install subagents to multiple targets including OpenCode
+- **WHEN** user selects targets "Augment" and "OpenCode" via comma-separated flag and scope "User level"
+- **THEN** system creates directories `~/.augment/agents/` and `~/.config/opencode/agents/` if they do not exist
+- **THEN** for Augment target, system saves with `model` field in YAML frontmatter
+- **THEN** for OpenCode target, system saves with `mode: subagent` field and excludes `model` field
+
+#### Scenario: Overwrite existing subagent files
+- **WHEN** a subagent file with the same filename already exists
+- **THEN** system overwrites the existing file without confirmation
+
+#### Scenario: Subagent file save failure
+- **WHEN** a subagent file fails to save
+- **THEN** system throws an error with message "Failed to save subagent file for '{name}': {error}"
+
+#### Scenario: Partial save failure with multiple targets
+- **WHEN** user selects multiple targets and a subagent file fails to save to one directory
+- **THEN** system still attempts to save to the other directories before throwing an error
+
+### Requirement: User Feedback
+WHILE fetching and installing the kit, THE SYSTEM SHALL display progress information and show detailed success message with exact installation paths (including OpenCode paths).
+
+#### Scenario: Display fetching progress
+- **WHEN** fetching the kit
+- **THEN** system displays a spinner with text "Fetching kit {kitId}..."
+
+#### Scenario: Display processing progress
+- **WHEN** processing the kit
+- **THEN** system updates the spinner text to "Processing kit \"{name}\"..."
+
+#### Scenario: Display saving prompts progress
+- **WHEN** saving prompts
+- **THEN** system updates the spinner text to "Saving {count} prompts..."
+
+#### Scenario: Display saving subagents progress
+- **WHEN** saving subagents
+- **THEN** system updates the spinner text to "Saving {count} subagents..."
+
+#### Scenario: Display success message with exact paths
+- **WHEN** installation completes successfully
+- **THEN** system displays "Successfully installed kit \"{name}\": {promptsCount} prompts, {subagentsCount} subagents"
+- **THEN** system displays exact installation paths showing where files were saved
+
+#### Scenario: Display success message with OpenCode paths
+- **WHEN** installation to OpenCode completes successfully
+- **THEN** system displays OpenCode commands directory path with prompt count
+- **THEN** system displays OpenCode agents directory path with subagent count
+
+#### Scenario: Display error message
+- **WHEN** any error occurs during the process
+- **THEN** system displays "Kit fetch failed: {error}" and exits with code 1

package/openspec/changes/archive/2026-02-01-add-opencode-agent-support/specs/opencode-agent-support/spec.md

@@ -0,0 +1,65 @@
+## ADDED Requirements
+
+### Requirement: OpenCode Directory Structure
+THE SYSTEM SHALL support OpenCode's directory structure for user-level and project-level installations.
+
+#### Scenario: User-level OpenCode installation
+- **WHEN** user selects target "OpenCode" and scope "User level"
+- **THEN** system uses directory `~/.config/opencode/commands/` for prompts
+- **THEN** system uses directory `~/.config/opencode/agents/` for subagents
+
+#### Scenario: Project-level OpenCode installation
+- **WHEN** user selects target "OpenCode" and scope "Project level"
+- **THEN** system uses directory `./.opencode/commands/` for prompts
+- **THEN** system uses directory `./.opencode/agents/` for subagents
+
+### Requirement: OpenCode YAML Format for Subagents
+THE SYSTEM SHALL generate OpenCode-compatible YAML frontmatter for subagents with required `mode` field and without `model` field.
+
+#### Scenario: Save subagent to OpenCode
+- **WHEN** saving a subagent to OpenCode target
+- **THEN** system generates YAML frontmatter with `mode: subagent` field
+- **THEN** system includes `name`, `description`, and `color` fields
+- **THEN** system excludes `model` field from YAML frontmatter
+
+#### Scenario: Save subagent to Claude or Augment
+- **WHEN** saving a subagent to Claude or Augment target
+- **THEN** system generates YAML frontmatter with `name`, `description`, `model`, and `color` fields
+- **THEN** system excludes `mode` field from YAML frontmatter
+
+### Requirement: OpenCode Prompt Format
+THE SYSTEM SHALL use the same YAML frontmatter format for OpenCode prompts as Claude and Augment.
+
+#### Scenario: Save prompt to OpenCode
+- **WHEN** saving a prompt to OpenCode target
+- **THEN** system generates YAML frontmatter with `description` and `type: "manual"` fields
+- **THEN** format is identical to Claude and Augment prompt format
+
+### Requirement: OpenCode Path Resolution
+THE SYSTEM SHALL resolve OpenCode installation paths based on user selection of scope.
+
+#### Scenario: Resolve OpenCode user-level paths
+- **WHEN** resolving paths for target "OpenCode" and scope "User level"
+- **THEN** system returns commands path `~/.config/opencode/commands/`
+- **THEN** system returns agents path `~/.config/opencode/agents/`
+
+#### Scenario: Resolve OpenCode project-level paths
+- **WHEN** resolving paths for target "OpenCode" and scope "Project level"
+- **THEN** system returns commands path `./.opencode/commands/`
+- **THEN** system returns agents path `./.opencode/agents/`
+
+### Requirement: OpenCode Directory Creation
+THE SYSTEM SHALL create OpenCode directories if they do not exist before saving files.
+
+#### Scenario: Create missing OpenCode directories
+- **WHEN** OpenCode target directories do not exist
+- **THEN** system creates directories recursively before saving files
+- **THEN** system does not fail if directories already exist
+
+### Requirement: OpenCode Installation Success Feedback
+THE SYSTEM SHALL include OpenCode installation paths in success messages.
+
+#### Scenario: Display OpenCode installation paths
+- **WHEN** installation to OpenCode completes successfully
+- **THEN** system displays OpenCode commands directory path with prompt count
+- **THEN** system displays OpenCode agents directory path with subagent count

package/openspec/changes/archive/2026-02-01-add-opencode-agent-support/tasks.md

@@ -0,0 +1,54 @@
+## 1. Type Definitions
+
+- [x] 1.1 Update `AITarget` type to include `'opencode'` option: `type AITarget = 'claude' | 'augment' | 'opencode' | 'both';`
+- [x] 1.2 Update `KitInstallConfig['paths']` interface to include optional `opencode` property with `commands` and `agents` paths
+
+## 2. Path Constants
+
+- [x] 2.1 Add `OPENCODE_CONFIG_DIR` constant: `path.join(os.homedir(), '.config', 'opencode')`
+- [x] 2.2 Add `OPENCODE_COMMANDS_DIR` constant: `path.join(OPENCODE_CONFIG_DIR, 'commands')`
+- [x] 2.3 Add `OPENCODE_AGENTS_DIR` constant: `path.join(OPENCODE_CONFIG_DIR, 'agents')`
+
+## 3. Interactive Prompts
+
+- [x] 3.1 Update `promptAITarget()` to add 'OpenCode' option to the select menu
+- [x] 3.2 Update scope prompt description in `promptInstallScope()` to mention `.opencode` alongside `.augment` and `.claude`
+
+## 4. Path Resolution
+
+- [x] 4.1 Update `resolveInstallPaths()` to handle `target === 'opencode'` case
+- [x] 4.2 Add OpenCode user-level paths: `~/.config/opencode/commands/` and `~/.config/opencode/agents/`
+- [x] 4.3 Add OpenCode project-level paths: `./.opencode/commands/` and `./.opencode/agents/`
+- [x] 4.4 Ensure `resolveInstallPaths()` includes opencode in paths object when target is 'opencode'
+
+## 5. Save Functions
+
+- [x] 5.1 Update `saveSubagentToPath()` signature to accept `targetType: 'claude' | 'augment' | 'opencode'` parameter
+- [x] 5.2 Add conditional logic in `saveSubagentToPath()` to check if `targetType === 'opencode'`
+- [x] 5.3 For OpenCode: generate YAML with `mode: subagent` field and exclude `model` field
+- [x] 5.4 For Claude/Augment: keep existing YAML format with `model` field and no `mode` field
+- [x] 5.5 Verify `savePromptToPath()` works for OpenCode without changes (same format as Claude/Augment)
+
+## 6. Kit Installation Handler
+
+- [x] 6.1 Update `handleKit()` to pass target type to `saveSubagentToPath()` when saving to augment paths
+- [x] 6.2 Update `handleKit()` to pass target type to `saveSubagentToPath()` when saving to claude paths
+- [x] 6.3 Add logic in `handleKit()` to save prompts to opencode paths if `installConfig.paths.opencode` exists
+- [x] 6.4 Add logic in `handleKit()` to save subagents to opencode paths with `targetType: 'opencode'` if `installConfig.paths.opencode` exists
+- [x] 6.5 Update success message in `handleKit()` to include OpenCode paths when present
+
+## 7. Flag Parsing (Optional Enhancement)
+
+- [x] 7.1 Add support for comma-separated targets in `--target` flag (e.g., `--target claude,opencode`)
+- [x] 7.2 Parse comma-separated string into array of targets
+- [x] 7.3 Validate each target value against allowed options
+- [x] 7.4 Update installation logic to handle array of targets
+
+## 8. Testing & Verification
+
+- [x] 8.1 Run `bun run lint` to check for code quality issues
+- [x] 8.2 Fix any linting errors manually (no --unsafe flag)
+- [x] 8.3 Run `bun run build` to verify the build succeeds
+- [ ] 8.4 Test interactive mode: `auggiegw kit <test-kit-id>` and select OpenCode target
+- [ ] 8.5 Test flag mode: `auggiegw kit <test-kit-id> --target opencode --scope user`
+- [ ] 8.6 Verify OpenCode directories are created and files have correct YAML format

package/openspec/config.yaml

@@ -0,0 +1,20 @@
+schema: spec-driven
+
+# Project context (optional)
+# This is shown to AI when creating artifacts.
+# Add your tech stack, conventions, style guides, domain knowledge, etc.
+# Example:
+#   context: |
+#     Tech stack: TypeScript, React, Node.js
+#     We use conventional commits
+#     Domain: e-commerce platform
+
+# Per-artifact rules (optional)
+# Add custom rules for specific artifacts.
+# Example:
+#   rules:
+#     proposal:
+#       - Keep proposals under 500 words
+#       - Always include a "Non-goals" section
+#     tasks:
+#       - Break tasks into chunks of max 2 hours

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dccxx/auggiegw",
-  "version": "1.0.24",
+  "version": "1.0.26",
   "description": "A Node.js TypeScript package",
   "main": "./dist/cli.js",
   "types": "./dist/cli.d.ts",
@@ -28,6 +28,7 @@
     "node": ">=18.0.0"
   },
   "dependencies": {
+    "@clack/prompts": "^1.0.0",
     "commander": "^14.0.1",
     "ora": "^5.4.1",
     "uuid": "^13.0.0"

package/specs/kit-command/spec.md

@@ -0,0 +1,157 @@
+## MODIFIED Requirements
+
+### Requirement: Command Invocation
+WHEN the user runs `auggiegw kit <kit-id>`, THE SYSTEM SHALL prompt the user to select target AI tool (including OpenCode) and installation scope, then fetch the kit from the public API endpoint.
+
+#### Scenario: User runs kit command without flags
+- **WHEN** user runs `auggiegw kit <kit-id>` without any flags
+- **THEN** system displays interactive prompt for target selection with options: Claude, Augment, OpenCode, Both
+- **THEN** system displays interactive prompt for scope selection
+- **THEN** system fetches the kit from the public API endpoint
+
+#### Scenario: User runs kit command with flags
+- **WHEN** user runs `auggiegw kit <kit-id> --target claude --scope user`
+- **THEN** system skips prompts and uses provided flag values
+- **THEN** system fetches the kit from the public API endpoint
+
+#### Scenario: User selects OpenCode target via flag
+- **WHEN** user runs `auggiegw kit <kit-id> --target opencode`
+- **THEN** system skips target prompt and uses OpenCode as target
+- **THEN** system displays interactive prompt for scope selection
+- **THEN** system fetches the kit from the public API endpoint
+
+#### Scenario: User selects multiple targets via flag
+- **WHEN** user runs `auggiegw kit <kit-id> --target claude,opencode`
+- **THEN** system parses comma-separated targets
+- **THEN** system installs to both Claude and OpenCode
+- **THEN** system fetches the kit from the public API endpoint
+
+#### Scenario: Missing kit-id argument
+- **WHEN** kit-id argument is missing
+- **THEN** system displays "Error: Kit ID is required" and usage message, and exits with code 1
+
+### Requirement: Prompt Installation
+WHEN processing prompts, THE SYSTEM SHALL create the target directories based on user selection (including OpenCode) and save markdown files with YAML frontmatter to the selected locations.
+
+#### Scenario: Install prompts to Claude user level
+- **WHEN** user selects target "Claude" and scope "User level"
+- **THEN** system creates directory `~/.claude/commands/` if it does not exist
+- **THEN** for each prompt in the kit, system saves a markdown file to `~/.claude/commands/{command}.md` with YAML frontmatter containing `description` and `type: "manual"` fields
+
+#### Scenario: Install prompts to Augment project level
+- **WHEN** user selects target "Augment" and scope "Project level"
+- **THEN** system creates directory `./.augment/commands/` if it does not exist
+- **THEN** for each prompt in the kit, system saves a markdown file to `./.augment/commands/{command}.md` with YAML frontmatter containing `description` and `type: "manual"` fields
+
+#### Scenario: Install prompts to OpenCode user level
+- **WHEN** user selects target "OpenCode" and scope "User level"
+- **THEN** system creates directory `~/.config/opencode/commands/` if it does not exist
+- **THEN** for each prompt in the kit, system saves a markdown file to `~/.config/opencode/commands/{command}.md` with YAML frontmatter containing `description` and `type: "manual"` fields
+
+#### Scenario: Install prompts to OpenCode project level
+- **WHEN** user selects target "OpenCode" and scope "Project level"
+- **THEN** system creates directory `./.opencode/commands/` if it does not exist
+- **THEN** for each prompt in the kit, system saves a markdown file to `./.opencode/commands/{command}.md` with YAML frontmatter containing `description` and `type: "manual"` fields
+
+#### Scenario: Install prompts to both targets at user level
+- **WHEN** user selects target "Both" and scope "User level"
+- **THEN** system creates directories `~/.augment/commands/` and `~/.claude/commands/` if they do not exist
+- **THEN** for each prompt in the kit, system saves markdown files to both `~/.augment/commands/{command}.md` and `~/.claude/commands/{command}.md`
+
+#### Scenario: Install prompts to multiple targets including OpenCode
+- **WHEN** user selects targets "Claude" and "OpenCode" via comma-separated flag and scope "User level"
+- **THEN** system creates directories `~/.claude/commands/` and `~/.config/opencode/commands/` if they do not exist
+- **THEN** for each prompt in the kit, system saves markdown files to both directories
+
+#### Scenario: Overwrite existing prompt files
+- **WHEN** a prompt file with the same filename already exists
+- **THEN** system overwrites the existing file without confirmation
+
+#### Scenario: Prompt file save failure
+- **WHEN** a prompt file fails to save
+- **THEN** system throws an error with message "Failed to save prompt file for command '{command}': {error}"
+
+#### Scenario: Partial save failure with multiple targets
+- **WHEN** user selects multiple targets and a prompt file fails to save to one directory
+- **THEN** system still attempts to save to the other directories before throwing an error
+
+### Requirement: Subagent Installation
+WHEN processing subagents, THE SYSTEM SHALL create the target directories based on user selection (including OpenCode) and save markdown files with appropriate YAML frontmatter to the selected locations.
+
+#### Scenario: Install subagents to Claude user level
+- **WHEN** user selects target "Claude" and scope "User level"
+- **THEN** system creates directory `~/.claude/agents/` if it does not exist
+- **THEN** for each subagent in the kit, system saves a markdown file to `~/.claude/agents/{name}.md` with YAML frontmatter containing `name`, `description`, `model`, and `color` fields
+
+#### Scenario: Install subagents to Augment project level
+- **WHEN** user selects target "Augment" and scope "Project level"
+- **THEN** system creates directory `./.augment/agents/` if it does not exist
+- **THEN** for each subagent in the kit, system saves a markdown file to `./.augment/agents/{name}.md` with YAML frontmatter containing `name`, `description`, `model`, and `color` fields
+
+#### Scenario: Install subagents to OpenCode user level
+- **WHEN** user selects target "OpenCode" and scope "User level"
+- **THEN** system creates directory `~/.config/opencode/agents/` if it does not exist
+- **THEN** for each subagent in the kit, system saves a markdown file to `~/.config/opencode/agents/{name}.md` with YAML frontmatter containing `mode: subagent`, `name`, `description`, and `color` fields
+- **THEN** system excludes `model` field from YAML frontmatter
+
+#### Scenario: Install subagents to OpenCode project level
+- **WHEN** user selects target "OpenCode" and scope "Project level"
+- **THEN** system creates directory `./.opencode/agents/` if it does not exist
+- **THEN** for each subagent in the kit, system saves a markdown file to `./.opencode/agents/{name}.md` with YAML frontmatter containing `mode: subagent`, `name`, `description`, and `color` fields
+- **THEN** system excludes `model` field from YAML frontmatter
+
+#### Scenario: Install subagents to both targets at user level
+- **WHEN** user selects target "Both" and scope "User level"
+- **THEN** system creates directories `~/.augment/agents/` and `~/.claude/agents/` if they do not exist
+- **THEN** for each subagent in the kit, system saves markdown files to both `~/.augment/agents/{name}.md` and `~/.claude/agents/{name}.md`
+
+#### Scenario: Install subagents to multiple targets including OpenCode
+- **WHEN** user selects targets "Augment" and "OpenCode" via comma-separated flag and scope "User level"
+- **THEN** system creates directories `~/.augment/agents/` and `~/.config/opencode/agents/` if they do not exist
+- **THEN** for Augment target, system saves with `model` field in YAML frontmatter
+- **THEN** for OpenCode target, system saves with `mode: subagent` field and excludes `model` field
+
+#### Scenario: Overwrite existing subagent files
+- **WHEN** a subagent file with the same filename already exists
+- **THEN** system overwrites the existing file without confirmation
+
+#### Scenario: Subagent file save failure
+- **WHEN** a subagent file fails to save
+- **THEN** system throws an error with message "Failed to save subagent file for '{name}': {error}"
+
+#### Scenario: Partial save failure with multiple targets
+- **WHEN** user selects multiple targets and a subagent file fails to save to one directory
+- **THEN** system still attempts to save to the other directories before throwing an error
+
+### Requirement: User Feedback
+WHILE fetching and installing the kit, THE SYSTEM SHALL display progress information and show detailed success message with exact installation paths (including OpenCode paths).
+
+#### Scenario: Display fetching progress
+- **WHEN** fetching the kit
+- **THEN** system displays a spinner with text "Fetching kit {kitId}..."
+
+#### Scenario: Display processing progress
+- **WHEN** processing the kit
+- **THEN** system updates the spinner text to "Processing kit \"{name}\"..."
+
+#### Scenario: Display saving prompts progress
+- **WHEN** saving prompts
+- **THEN** system updates the spinner text to "Saving {count} prompts..."
+
+#### Scenario: Display saving subagents progress
+- **WHEN** saving subagents
+- **THEN** system updates the spinner text to "Saving {count} subagents..."
+
+#### Scenario: Display success message with exact paths
+- **WHEN** installation completes successfully
+- **THEN** system displays "Successfully installed kit \"{name}\": {promptsCount} prompts, {subagentsCount} subagents"
+- **THEN** system displays exact installation paths showing where files were saved
+
+#### Scenario: Display success message with OpenCode paths
+- **WHEN** installation to OpenCode completes successfully
+- **THEN** system displays OpenCode commands directory path with prompt count
+- **THEN** system displays OpenCode agents directory path with subagent count
+
+#### Scenario: Display error message
+- **WHEN** any error occurs during the process
+- **THEN** system displays "Kit fetch failed: {error}" and exits with code 1

package/specs/kit-install-prompts/spec.md

@@ -0,0 +1,90 @@
+## ADDED Requirements
+
+### Requirement: User can select target AI tool
+The system SHALL prompt the user to select which AI tool to install the kit to: Claude, Augment, or Both.
+
+#### Scenario: User selects Claude only
+- **WHEN** user runs `auggiegw kit <kit-id>` without `--target` flag
+- **THEN** system displays interactive prompt with options: Claude, Augment, Both
+- **WHEN** user selects "Claude"
+- **THEN** system installs kit files only to Claude directories
+
+#### Scenario: User selects Augment only
+- **WHEN** user runs `auggiegw kit <kit-id>` without `--target` flag
+- **THEN** system displays interactive prompt with options: Claude, Augment, Both
+- **WHEN** user selects "Augment"
+- **THEN** system installs kit files only to Augment directories
+
+#### Scenario: User selects Both
+- **WHEN** user runs `auggiegw kit <kit-id>` without `--target` flag
+- **THEN** system displays interactive prompt with options: Claude, Augment, Both
+- **WHEN** user selects "Both"
+- **THEN** system installs kit files to both Claude and Augment directories
+
+#### Scenario: User provides target via CLI flag
+- **WHEN** user runs `auggiegw kit <kit-id> --target claude`
+- **THEN** system skips the target prompt and uses "claude" as the target
+
+### Requirement: User can select installation scope
+The system SHALL prompt the user to select the installation scope: User level or Project level.
+
+#### Scenario: User selects user level installation
+- **WHEN** user runs `auggiegw kit <kit-id>` without `--scope` flag
+- **THEN** system displays interactive prompt with options: User level, Project level
+- **WHEN** user selects "User level"
+- **THEN** system installs kit files to home directory paths (~/.augment or ~/.claude)
+
+#### Scenario: User selects project level installation
+- **WHEN** user runs `auggiegw kit <kit-id>` without `--scope` flag
+- **THEN** system displays interactive prompt with options: User level, Project level
+- **WHEN** user selects "Project level"
+- **THEN** system installs kit files to current working directory paths (./.augment or ./.claude)
+
+#### Scenario: User provides scope via CLI flag
+- **WHEN** user runs `auggiegw kit <kit-id> --scope project`
+- **THEN** system skips the scope prompt and uses "project" as the scope
+
+### Requirement: System resolves installation paths based on selections
+The system SHALL resolve the correct installation paths based on the user's target and scope selections.
+
+#### Scenario: Claude target with user scope
+- **WHEN** user selects target "Claude" and scope "User level"
+- **THEN** system resolves paths to ~/.claude/commands/ and ~/.claude/agents/
+
+#### Scenario: Augment target with project scope
+- **WHEN** user selects target "Augment" and scope "Project level"
+- **THEN** system resolves paths to ./.augment/commands/ and ./.augment/agents/
+
+#### Scenario: Both targets with user scope
+- **WHEN** user selects target "Both" and scope "User level"
+- **THEN** system resolves paths to both ~/.augment/ and ~/.claude/ directories
+
+#### Scenario: Both targets with project scope
+- **WHEN** user selects target "Both" and scope "Project level"
+- **THEN** system resolves paths to both ./.augment/ and ./.claude/ directories
+
+### Requirement: System creates directories automatically
+The system SHALL automatically create target directories if they do not exist.
+
+#### Scenario: Target directory does not exist
+- **WHEN** system attempts to save files to a directory that does not exist
+- **THEN** system creates the directory recursively before saving files
+
+#### Scenario: Multiple target directories need creation
+- **WHEN** user selects "Both" targets and directories do not exist
+- **THEN** system creates all required directories for both Claude and Augment
+
+### Requirement: System displays installation paths in success message
+The system SHALL display the exact installation paths in the success message after kit installation completes.
+
+#### Scenario: Single target installation
+- **WHEN** kit installation completes successfully with single target
+- **THEN** success message includes exact paths where prompts and subagents were installed
+
+#### Scenario: Both targets installation
+- **WHEN** kit installation completes successfully with both targets
+- **THEN** success message includes exact paths for both Claude and Augment installations
+
+#### Scenario: Success message shows file counts per location
+- **WHEN** kit installation completes successfully
+- **THEN** success message shows the number of prompts and subagents installed to each location

package/specs/opencode-agent-support/spec.md

@@ -0,0 +1,65 @@
+## ADDED Requirements
+
+### Requirement: OpenCode Directory Structure
+THE SYSTEM SHALL support OpenCode's directory structure for user-level and project-level installations.
+
+#### Scenario: User-level OpenCode installation
+- **WHEN** user selects target "OpenCode" and scope "User level"
+- **THEN** system uses directory `~/.config/opencode/commands/` for prompts
+- **THEN** system uses directory `~/.config/opencode/agents/` for subagents
+
+#### Scenario: Project-level OpenCode installation
+- **WHEN** user selects target "OpenCode" and scope "Project level"
+- **THEN** system uses directory `./.opencode/commands/` for prompts
+- **THEN** system uses directory `./.opencode/agents/` for subagents
+
+### Requirement: OpenCode YAML Format for Subagents
+THE SYSTEM SHALL generate OpenCode-compatible YAML frontmatter for subagents with required `mode` field and without `model` field.
+
+#### Scenario: Save subagent to OpenCode
+- **WHEN** saving a subagent to OpenCode target
+- **THEN** system generates YAML frontmatter with `mode: subagent` field
+- **THEN** system includes `name`, `description`, and `color` fields
+- **THEN** system excludes `model` field from YAML frontmatter
+
+#### Scenario: Save subagent to Claude or Augment
+- **WHEN** saving a subagent to Claude or Augment target
+- **THEN** system generates YAML frontmatter with `name`, `description`, `model`, and `color` fields
+- **THEN** system excludes `mode` field from YAML frontmatter
+
+### Requirement: OpenCode Prompt Format
+THE SYSTEM SHALL use the same YAML frontmatter format for OpenCode prompts as Claude and Augment.
+
+#### Scenario: Save prompt to OpenCode
+- **WHEN** saving a prompt to OpenCode target
+- **THEN** system generates YAML frontmatter with `description` and `type: "manual"` fields
+- **THEN** format is identical to Claude and Augment prompt format
+
+### Requirement: OpenCode Path Resolution
+THE SYSTEM SHALL resolve OpenCode installation paths based on user selection of scope.
+
+#### Scenario: Resolve OpenCode user-level paths
+- **WHEN** resolving paths for target "OpenCode" and scope "User level"
+- **THEN** system returns commands path `~/.config/opencode/commands/`
+- **THEN** system returns agents path `~/.config/opencode/agents/`
+
+#### Scenario: Resolve OpenCode project-level paths
+- **WHEN** resolving paths for target "OpenCode" and scope "Project level"
+- **THEN** system returns commands path `./.opencode/commands/`
+- **THEN** system returns agents path `./.opencode/agents/`
+
+### Requirement: OpenCode Directory Creation
+THE SYSTEM SHALL create OpenCode directories if they do not exist before saving files.
+
+#### Scenario: Create missing OpenCode directories
+- **WHEN** OpenCode target directories do not exist
+- **THEN** system creates directories recursively before saving files
+- **THEN** system does not fail if directories already exist
+
+### Requirement: OpenCode Installation Success Feedback
+THE SYSTEM SHALL include OpenCode installation paths in success messages.
+
+#### Scenario: Display OpenCode installation paths
+- **WHEN** installation to OpenCode completes successfully
+- **THEN** system displays OpenCode commands directory path with prompt count
+- **THEN** system displays OpenCode agents directory path with subagent count