cokit-cli 1.2.0 → 1.2.2

package/docs/cokit-comprehensive-mapping-guide.md

@@ -23,7 +23,7 @@ Complete reference for CoKit GitHub Copilot resource toolkit.
 CoKit transforms GitHub Copilot from basic autocomplete to a structured AI development assistant with:
 
 - **12 Specialized Agents** - Planner, code-reviewer, debugger, tester, researcher, code-simplifier, fullstack-developer, ui-ux-designer, etc.
-- **28 Prompt Templates** - Reusable workflows with `ck.*` and `ck.spec.*` prefixes
+- **27 Prompt Templates** - Reusable workflows with `ck-*` and `ck-spec-*` prefixes
 - **27 Skill Packages** - Deep expertise in debugging, code-review, planning, frontend-design, databases, devops, etc.
 - **5 Instructions** - Coding standards auto-applied by file pattern (backend, frontend, testing, development, research)
 - **5 Collections** - Bundled resource sets for specific workflows (core, development-rules, documentation, git-workflow, orchestration)
@@ -56,17 +56,17 @@ description: 'Clear task description'
 Step-by-step instructions...
 ```
 
-**CoKit Prompts (28 total):**
+**CoKit Prompts (27 total):**
 
-**ClaudeKit (ck.* namespace):** Development workflows - fix, plan, cook, test, review, debug, ask, etc.
+**ClaudeKit (ck-* namespace):** Development workflows - fix, plan, cook, test, review, debug, ask, etc.
 
-**SpecKit (ck.spec.* namespace):** Spec-driven workflows - specify, clarify, constitution, plan, tasks, implement, analyze, checklist, taskstoissues, etc.
+**SpecKit (ck-spec-* namespace):** Spec-driven workflows - specify, clarify, constitution, plan, tasks, implement, analyze, checklist, etc.
 
-All 28 prompts are unified in a single namespace for seamless workflow navigation.
+All 27 prompts are unified in a single namespace for seamless workflow navigation.
 
 **Usage Example:**
 ```
-User: /ck.fix The login endpoint returns 500 error
+User: /ck-fix The login endpoint returns 500 error
 
 Copilot uses: ck-fix.prompt.md → debugger.agent.md → ck-debugging skill
 Result: Systematic debugging plan and fix
@@ -215,7 +215,7 @@ You'll be prompted to choose:
 
 | Feature | Claude Code | CoKit/Copilot | Notes |
 |---------|-------------|---|---|
-| **Commands** | `/fix:types`, `/plan:auto` | `/ck.fix`, `/ck.plan`, `/ck.cook`, etc. | 14 prompts vs sub-commands |
+| **Commands** | `/fix:types`, `/plan:auto` | `/ck-fix`, `/ck-plan`, `/ck-cook`, etc. | 14 prompts vs sub-commands |
 | **Skills** | `~/.claude/skills/` | `~/.copilot/skills/ck-*/` | Identical structure |
 | **Instructions** | `.claude/instructions/` | `.github/instructions/ck-*.md` | Auto-applied by pattern |
 | **Agents** | Task delegation | Agent references in prompts | Different invocation model |
@@ -231,7 +231,7 @@ You'll be prompted to choose:
 ### Pattern 1: Fix & Debug Workflow
 
 ```
-User: /ck.fix The API timeout is too short
+User: /ck-fix The API timeout is too short
   ↓
 Prompt (ck-fix.prompt.md)
   ↓
@@ -245,7 +245,7 @@ Output: Root cause analysis + fix
 ### Pattern 2: Feature Implementation
 
 ```
-User: /ck.plan Build user authentication
+User: /ck-plan Build user authentication
   ↓
 Prompt (ck-plan.prompt.md) + Agent (planner.agent.md)
   ↓
@@ -253,7 +253,7 @@ Skills: ck-planning, ck-sequential-thinking
   ↓
 Output: Implementation plan
 
-User: /ck.code Implement step 1
+User: /ck-code Implement step 1
   ↓
 Prompt (ck-code.prompt.md) + Agent (code-reviewer monitors)
   ↓
@@ -261,7 +261,7 @@ Skills: ck-backend-development or ck-frontend-development
   ↓
 Output: Implemented code
 
-User: /ck.test Write tests
+User: /ck-test Write tests
   ↓
 Prompt (ck-test.prompt.md) + Agent (tester.agent.md)
   ↓
@@ -271,7 +271,7 @@ Output: Test coverage
 ### Pattern 3: Code Review
 
 ```
-User: /ck.review-codebase My auth changes
+User: /ck-review-codebase My auth changes
   ↓
 Prompt (ck-review-codebase.prompt.md)
   ↓
@@ -291,7 +291,7 @@ Output: Quality gates, security issues, improvements
 CoKit supports manual chaining (Copilot is stateless):
 
 ```
-/ck.plan feature  →  /ck.code step1  →  /ck.test  →  /ck.review-codebase
+/ck-plan feature  →  /ck-code step1  →  /ck-test  →  /ck-review-codebase
 ```
 
 ### 2. Context Management
@@ -300,10 +300,10 @@ Without `$ARGUMENTS`, provide context in chat:
 
 ```
 DON'T:
-/ck.fix $ARGUMENTS
+/ck-fix $ARGUMENTS
 
 DO:
-/ck.fix The login endpoint returns 401 for valid credentials in auth.ts
+/ck-fix The login endpoint returns 401 for valid credentials in auth.ts
 ```
 
 ### 3. Instructions Auto-Apply

package/docs/cokit-slides.md

@@ -61,13 +61,13 @@ npm publish                               Downloads cokit-cli
 
 ## Slide 6: What Users Get
 
-### 28 Prompts (ClaudeKit + SpecKit)
+### 27 Prompts (ClaudeKit + SpecKit)
 
-**Development workflows (ck.*):**
-- `/ck.fix`, `/ck.plan`, `/ck.cook`, `/ck.test`, `/ck.review`, `/ck.bootstrap`, `/ck.brainstorm`, etc.
+**Development workflows (ck-*):**
+- `/ck-fix`, `/ck-plan`, `/ck-cook`, `/ck-test`, `/ck-review`, `/ck-bootstrap`, `/ck-brainstorm`, etc.
 
-**Spec-driven workflows (ck.spec.*):**
-- `/ck.spec.specify`, `/ck.spec.clarify`, `/ck.spec.plan`, `/ck.spec.tasks`, `/ck.spec.implement`, etc.
+**Spec-driven workflows (ck-spec-*):**
+- `/ck-spec-specify`, `/ck-spec-clarify`, `/ck-spec-plan`, `/ck-spec-tasks`, `/ck-spec-implement`, etc.
 
 All unified in single namespace with cross-navigation.
 
@@ -127,7 +127,7 @@ $ npx cokit-cli init
 ✓ Created .github/instructions/ (5 files)
 ✓ Created .github/collections/ (5 bundles)
 
-🎉 Done! Try /ck.fix in Copilot Chat.
+🎉 Done! Try /ck-fix in Copilot Chat.
 ```
 
 ---

package/docs/cokit-sync-and-maintenance-guide.md

@@ -6,7 +6,7 @@
 
 ## Architecture Overview
 
-CoKit merges two upstream sources into a unified `ck.*` command namespace:
+CoKit merges two upstream sources into a unified `ck-*` command namespace:
 
 ```
 ┌─────────────────────────────────────────────────────────────────┐
@@ -37,13 +37,13 @@ CoKit merges two upstream sources into a unified `ck.*` command namespace:
 │                      OUTPUT                                      │
 ├─────────────────────────────────────────────────────────────────┤
 │  prompts/           agents/           skills/                   │
-│  ├── ck.brainstorm  ├── planner       ├── ck-planning/          │
-│  ├── ck.specify     ├── debugger      ├── ck-databases/         │
-│  ├── ck.plan        └── ...           └── ...                   │
+│  ├── ck-brainstorm  ├── planner       ├── ck-planning/          │
+│  ├── ck-specify     ├── debugger      ├── ck-databases/         │
+│  ├── ck-plan        └── ...           └── ...                   │
 │  └── ...                                                        │
 │                                                                 │
-│  All use unified ck.* namespace                                 │
-│  All have cross-navigation to other ck.* commands               │
+│  All use unified ck-* namespace                                 │
+│  All have cross-navigation to other ck-* commands               │
 └─────────────────────────────────────────────────────────────────┘
 ```
 
@@ -57,7 +57,7 @@ CoKit merges two upstream sources into a unified `ck.*` command namespace:
 | `eng/transform-claudekit.mjs` | ClaudeKit → CoKit transform rules |
 | `eng/transform-speckit.mjs` | SpecKit → CoKit transform rules |
 | `eng/patch-navigation.mjs` | Injects unified navigation footer |
-| `eng/resource-origins.yml` | **CRITICAL** - Maps ck.* commands to upstream sources |
+| `eng/resource-origins.yml` | **CRITICAL** - Maps ck-* commands to upstream sources |
 
 ---
 
@@ -81,42 +81,42 @@ sources:
     last_sync: "2026-02-03"
 
 # COMMAND MAPPINGS
-# Format: ck.{name} → source info
+# Format: ck-{name} → source info
 mappings:
   # ═══════════════════════════════════════════════════════════════
   # FROM SPECKIT
   # ═══════════════════════════════════════════════════════════════
-  ck.specify:
+  ck-specify:
     origin: speckit
     original: speckit.specify
     upstream_file: templates/commands/specify.md
     description: Create feature specification from description
 
-  ck.clarify:
+  ck-clarify:
     origin: speckit
     original: speckit.clarify
     upstream_file: templates/commands/clarify.md
     description: Resolve specification ambiguities
 
-  ck.constitution:
+  ck-constitution:
     origin: speckit
     original: speckit.constitution
     upstream_file: templates/commands/constitution.md
     description: Create/update project constitution
 
-  ck.tasks:
+  ck-tasks:
     origin: speckit
     original: speckit.tasks
     upstream_file: templates/commands/tasks.md
     description: Generate task list from plan
 
-  ck.analyze:
+  ck-analyze:
     origin: speckit
     original: speckit.analyze
     upstream_file: templates/commands/analyze.md
     description: Analyze spec consistency
 
-  ck.checklist:
+  ck-checklist:
     origin: speckit
     original: speckit.checklist
     upstream_file: templates/commands/checklist.md
@@ -125,43 +125,43 @@ mappings:
   # ═══════════════════════════════════════════════════════════════
   # FROM CLAUDEKIT
   # ═══════════════════════════════════════════════════════════════
-  ck.brainstorm:
+  ck-brainstorm:
     origin: claudekit
     original: brainstorm
     upstream_file: skills/brainstorm/SKILL.md
     description: Explore solutions with trade-off analysis
 
-  ck.plan:
+  ck-plan:
     origin: claudekit
     original: plan
     upstream_file: commands/plan.md
     description: Intelligent plan creation
 
-  ck.plan.hard:
+  ck-plan-hard:
     origin: claudekit
     original: plan/hard
     upstream_file: commands/plan/hard.md
     description: Deep research + comprehensive plan
 
-  ck.plan.fast:
+  ck-plan-fast:
     origin: claudekit
     original: plan/fast
     upstream_file: commands/plan/fast.md
     description: Quick plan without research
 
-  ck.cook:
+  ck-cook:
     origin: claudekit
     original: cook
     upstream_file: skills/cook/SKILL.md
     description: Implement feature step by step
 
-  ck.fix:
+  ck-fix:
     origin: claudekit
     original: fix
     upstream_file: skills/fix/SKILL.md
     description: Analyze and fix issues
 
-  ck.test:
+  ck-test:
     origin: claudekit
     original: test
     upstream_file: commands/test.md
@@ -203,7 +203,7 @@ git commit -m "sync: update from claudekit + speckit $(date +%Y-%m-%d)"
 
 1. **Sync detects unknown command** → logged to `unknown_commands` in resource-origins.yml
 2. **Review the new command** → check upstream docs
-3. **Add to mappings** with appropriate `ck.*` name
+3. **Add to mappings** with appropriate `ck-*` name
 4. **Re-run transform**
 5. **Test the new command**
 
@@ -222,17 +222,17 @@ git commit -m "sync: update from claudekit + speckit $(date +%Y-%m-%d)"
 
 | Original | Transformed |
 |----------|-------------|
-| `/speckit.specify` | `/ck.specify` |
-| `/speckit.plan` | `/ck.plan` (conflicts with claudekit, see below) |
-| `/plan` (claudekit) | `/ck.plan` |
-| `/plan:hard` | `/ck.plan.hard` |
-| `/brainstorm` | `/ck.brainstorm` |
+| `/speckit.specify` | `/ck-specify` |
+| `/speckit.plan` | `/ck-plan` (conflicts with claudekit, see below) |
+| `/plan` (claudekit) | `/ck-plan` |
+| `/plan:hard` | `/ck-plan-hard` |
+| `/brainstorm` | `/ck-brainstorm` |
 
 ### Conflict Resolution
 
 When both sources have same command name (e.g., `plan`):
 - **Default**: ClaudeKit version wins (more mature)
-- **SpecKit version**: Available as `ck.plan.spec` if needed
+- **SpecKit version**: Available as `ck-plan.spec` if needed
 - **Document in resource-origins.yml**
 
 ### Placeholder Substitution
@@ -260,7 +260,7 @@ Transform to:
 ```yaml
 handoffs:
   - label: Build Technical Plan
-    agent: ck.plan
+    agent: ck-plan
 ```
 
 ---
@@ -276,13 +276,13 @@ Every prompt gets a navigation footer injected:
 
 | Current | Next Options |
 |---------|--------------|
-| After `ck.brainstorm` | `/ck.specify`, `/ck.plan.fast` |
-| After `ck.specify` | `/ck.clarify`, `/ck.brainstorm`, `/ck.plan` |
-| After `ck.clarify` | `/ck.specify` (update), `/ck.plan` |
-| After `ck.plan` | `/ck.cook`, `/ck.brainstorm` (rethink) |
-| After `ck.cook` | `/ck.test`, `/ck.fix` |
+| After `ck-brainstorm` | `/ck-specify`, `/ck-plan-fast` |
+| After `ck-specify` | `/ck-clarify`, `/ck-brainstorm`, `/ck-plan` |
+| After `ck-clarify` | `/ck-specify` (update), `/ck-plan` |
+| After `ck-plan` | `/ck-cook`, `/ck-brainstorm` (rethink) |
+| After `ck-cook` | `/ck-test`, `/ck-fix` |
 
-**All commands:** `ck.brainstorm`, `ck.specify`, `ck.clarify`, `ck.constitution`, `ck.plan`, `ck.plan.hard`, `ck.plan.fast`, `ck.tasks`, `ck.cook`, `ck.fix`, `ck.test`
+**All commands:** `ck-brainstorm`, `ck-specify`, `ck-clarify`, `ck-constitution`, `ck-plan`, `ck-plan-hard`, `ck-plan-fast`, `ck-tasks`, `ck-cook`, `ck-fix`, `ck-test`
 ```
 
 ---
@@ -298,32 +298,32 @@ Every prompt gets a navigation footer injected:
 │       │                                                         │
 │       ▼                                                         │
 │  ┌─────────────┐                                                │
-│  │ck.brainstorm│ ← Always start here (question everything)     │
+│  │ck-brainstorm│ ← Always start here (question everything)     │
 │  └──────┬──────┘                                                │
 │         │                                                       │
 │         ▼                                                       │
 │  ┌─────────────┐                                                │
-│  │ ck.specify  │ ← Formalize into spec                         │
+│  │ ck-specify  │ ← Formalize into spec                         │
 │  └──────┬──────┘                                                │
 │         │ Has ambiguities?                                      │
 │         ▼                                                       │
 │  ┌─────────────┐                                                │
-│  │ ck.clarify  │ ← Resolve (optional)                          │
+│  │ ck-clarify  │ ← Resolve (optional)                          │
 │  └──────┬──────┘                                                │
 │         │◄────────────────────────┐                             │
 │         ▼                         │                             │
 │  ┌─────────────┐                  │                             │
-│  │ ck.plan     │    Loop back if  │                             │
+│  │ ck-plan     │    Loop back if  │                             │
 │  └──────┬──────┘    approach needs│                             │
 │         │           rethinking    │                             │
 │         ▼                         │                             │
 │  ┌─────────────┐                  │                             │
-│  │ ck.cook     │──────────────────┘                             │
-│  └──────┬──────┘    (via ck.brainstorm)                         │
+│  │ ck-cook     │──────────────────┘                             │
+│  └──────┬──────┘    (via ck-brainstorm)                         │
 │         │                                                       │
 │         ▼                                                       │
 │  ┌─────────────┐                                                │
-│  │ ck.test     │                                                │
+│  │ ck-test     │                                                │
 │  └─────────────┘                                                │
 │                                                                 │
 └─────────────────────────────────────────────────────────────────┘
@@ -342,7 +342,7 @@ Every prompt gets a navigation footer injected:
 ### New command not appearing
 
 1. Check if it's in `unknown_commands` list
-2. Add to `mappings` section with `ck.*` name
+2. Add to `mappings` section with `ck-*` name
 3. Re-run sync
 
 ### Merge conflicts in generated files
@@ -369,11 +369,11 @@ ls ~/.claude/skills/
 
 For commands that don't come from upstream:
 
-1. Create directly in `prompts/` with `ck.` prefix
+1. Create directly in `prompts/` with `ck-` prefix
 2. Add to resource-origins.yml with `origin: cokit-native`:
 
 ```yaml
-ck.workflow.enterprise:
+ck-workflow.enterprise:
   origin: cokit-native
   description: Full enterprise flow (brainstorm → specify → plan → cook)
 ```

package/docs/cokit-team-presentation.md

@@ -18,7 +18,7 @@
 - Project-specific context
 
 **Solution:** CoKit ports proven Claude Code workflow patterns to GitHub Copilot via:
-- 28 prompts with unified `ck.*` namespace (ClaudeKit + SpecKit) using `mode: agent`
+- 27 prompts with unified `ck-*` namespace (ClaudeKit + SpecKit) using `mode: agent`
 - 27 skills teaching Copilot best practices (debugging, code-review, planning, frontend-design, databases, devops, etc.)
 - 12 specialized agents (including code-simplifier, fullstack-developer, ui-ux-designer)
 - 5 instructions (backend, frontend, testing, development, research)
@@ -79,16 +79,16 @@
 │   ┌─────────────────────────────────────────────────────────┐ │
 │   │ ✓ .github/copilot-instructions.md                       │ │
 │   │ ✓ .github/AGENTS.md                                     │ │
-│   │ ✓ .github/prompts/ck-*.prompt.md (28 prompts)           │ │
+│   │ ✓ .github/prompts/ck-*.prompt.md (27 prompts)           │ │
 │   │ ✓ .github/instructions/ck-*.instructions.md (5 files)   │ │
 │   │ ✓ .github/collections/ck-*.collection.yml (5 bundles)   │ │
 │   │ ✓ .vscode/settings.json                                 │ │
 │   │                                                         │ │
-│   │ 🎉 Done! Try /ck.fix in Copilot Chat.                   │ │
+│   │ 🎉 Done! Try /ck-fix in Copilot Chat.                   │ │
 │   └─────────────────────────────────────────────────────────┘ │
 │                              │                                 │
 │                              ▼                                 │
-│   Step 5: User opens VS Code, types /ck.fix or /ck.plan       │
+│   Step 5: User opens VS Code, types /ck-fix or /ck-plan       │
 │   ┌─────────────────────────────────────────────────────────┐ │
 │   │ Copilot Chat: "I'll help you debug systematically..."   │ │
 │   └─────────────────────────────────────────────────────────┘ │
@@ -167,15 +167,15 @@ your-project/
 
 ---
 
-## 5. Prompts Included (28 total)
+## 5. Prompts Included (27 total)
 
-**ClaudeKit (ck.*):** Development workflow commands
-- `/ck.fix`, `/ck.plan`, `/ck.cook`, `/ck.test`, `/ck.review`, `/ck.debug`, `/ck.ask`, etc.
+**ClaudeKit (ck-*):** Development workflow commands
+- `/ck-fix`, `/ck-plan`, `/ck-cook`, `/ck-test`, `/ck-review`, `/ck-debug`, `/ck-ask`, etc.
 
-**SpecKit (ck.spec.*):** Spec-driven workflow commands
-- `/ck.spec.specify`, `/ck.spec.clarify`, `/ck.spec.plan`, `/ck.spec.tasks`, `/ck.spec.implement`, etc.
+**SpecKit (ck-spec-*):** Spec-driven workflow commands
+- `/ck-spec-specify`, `/ck-spec-clarify`, `/ck-spec-plan`, `/ck-spec-tasks`, `/ck-spec-implement`, etc.
 
-All 28 prompts unified in single namespace with cross-navigation support.
+All 27 prompts unified in single namespace with cross-navigation support.
 
 ---
 
@@ -300,7 +300,7 @@ npx cokit-cli init          # Always fetches latest
 | $ARGUMENTS variables | ❌ Skip | User provides context in chat |
 | Session state | ❌ Skip | Copilot is stateless |
 
-**Workaround:** Users manually chain prompts (`/ck.plan` → `/ck.code` → `/ck.test` → `/ck.review-codebase`)
+**Workaround:** Users manually chain prompts (`/ck-plan` → `/ck-code` → `/ck-test` → `/ck-review-codebase`)
 
 ---
 

package/docs/copilot-processing-flow.md

@@ -18,7 +18,7 @@ How Copilot processes user input through CoKit resources to produce output.
 
 ### CoKit Examples
 
-**Prompts (28 total):** ClaudeKit (ck.*) and SpecKit (ck.spec.*) namespaces with 28 unified commands
+**Prompts (27 total):** ClaudeKit (ck-*) and SpecKit (ck-spec-*) namespaces with 27 unified commands
 
 **Agents (12 total):** planner, code-reviewer, debugger, tester, researcher, scout, git-manager, brainstormer, docs-manager, code-simplifier, fullstack-developer, ui-ux-designer
 
@@ -54,10 +54,10 @@ You are debugging an issue. Follow systematic troubleshooting...
 ```
 
 **CoKit Examples:**
-- `/ck.fix` - Debug and fix
-- `/ck.plan` - Create implementation plan
-- `/ck.cook` - Step-by-step feature implementation
-- `/ck.review-codebase` - Scan and analyze code
+- `/ck-fix` - Debug and fix
+- `/ck-plan` - Create implementation plan
+- `/ck-cook` - Step-by-step feature implementation
+- `/ck-review-codebase` - Scan and analyze code
 
 **When to use:** User wants to execute a specific workflow
 
@@ -135,7 +135,7 @@ When editing React files:
 
 **Example: ck-debugging/SKILL.md**
 ```
-skills/ck.debugging/
+skills/ck-debugging/
 ├── SKILL.md                  # Main methodology
 ├── references/               # Case studies, patterns
 └── examples/                 # Real debugging examples
@@ -166,9 +166,9 @@ description: Essential agents, prompts, and skills
 items:
   - path: agents/planner.agent.md
   - path: agents/code-reviewer.agent.md
-  - path: prompts/ck.plan.prompt.md
-  - path: prompts/ck.code.prompt.md
-  - path: skills/ck.planning/
+  - path: prompts/ck-plan.prompt.md
+  - path: prompts/ck-code.prompt.md
+  - path: skills/ck-planning/
 ```
 
 **CoKit Collections:**
@@ -197,7 +197,7 @@ items:
 ## CoKit Processing Example
 
 ```
-User types: /ck.fix
+User types: /ck-fix
     ↓
 Prompt (ck-fix.prompt.md) activates
     ↓
@@ -212,4 +212,4 @@ Output: Systematic debugging solution
 
 ## One-liner
 
-> User calls **Prompt** (e.g., `/ck.fix`) → Prompt references **Agent** (e.g., `debugger`) → Agent auto-receives **Instructions** by file pattern → Agent activates **Skills** when needed → All can be bundled in **Collection** (e.g., `ck-core`).
+> User calls **Prompt** (e.g., `/ck-fix`) → Prompt references **Agent** (e.g., `debugger`) → Agent auto-receives **Instructions** by file pattern → Agent activates **Skills** when needed → All can be bundled in **Collection** (e.g., `ck-core`).

package/docs/guide-next-steps-speckit-cokit-implementation.md

@@ -105,7 +105,7 @@ cokit workflow fix         → fix --auto
 ```bash
 # Update /instructions/ with combo workflows
 touch instructions/workflow-enterprise.md
-touch instructions/workflow-quick.md
+touch instructions/workflow-quick-md
 touch instructions/workflow-fix.md
 ```
 

package/docs/migration-guide.md

@@ -6,7 +6,7 @@ This guide helps Claude Code users adapt to GitHub Copilot with CoKit.
 
 | Feature | Claude Code | CoKit/Copilot |
 |---------|-------------|---------------|
-| Commands | `/fix:types`, `/plan:auto` | `/ck.fix`, `/ck.plan`, `/ck.cook`, etc. |
+| Commands | `/fix:types`, `/plan:auto` | `/ck-fix`, `/ck-plan`, `/ck-cook`, etc. |
 | Arguments | `$ARGUMENTS` variable | User provides in chat |
 | Subagents | Task tool delegates to agents | Referenced in prompts |
 | Hooks | Pre/post execution | Not supported |
@@ -27,8 +27,8 @@ This guide helps Claude Code users adapt to GitHub Copilot with CoKit.
 
 **Copilot:**
 ```
-/ck.fix the type errors in auth.ts
-/ck.fix the failing tests in user.test.ts
+/ck-fix the type errors in auth.ts
+/ck-fix the failing tests in user.test.ts
 ```
 
 Provide context directly in your message.
@@ -107,10 +107,10 @@ After fixing:
 
 2. Use prompts directly:
    ```
-   /ck.fix (describe your issue)
-   /ck.plan (describe your feature)
-   /ck.cook (implement a feature)
-   /ck.bootstrap (setup new project)
+   /ck-fix (describe your issue)
+   /ck-plan (describe your feature)
+   /ck-cook (implement a feature)
+   /ck-bootstrap (setup new project)
    ```
 
 3. Skills and agents work automatically:
@@ -120,10 +120,10 @@ After fixing:
 ## Tips for Claude Users
 
 1. **Be descriptive** - Without $ARGUMENTS, include context in chat
-2. **Use specialized prompts** - `/ck.cook` for implementation, `/ck.bootstrap` for setup
+2. **Use specialized prompts** - `/ck-cook` for implementation, `/ck-bootstrap` for setup
 3. **Explicit instructions** - Put everything in the prompt
 4. **Manual verification** - No automatic hooks
-5. **Chain workflows** - Use `/ck.plan` → `/ck.code` → `/ck.test` → `/ck.review-codebase`
+5. **Chain workflows** - Use `/ck-plan` → `/ck-code` → `/ck-test` → `/ck-review-codebase`
 
 ## Getting Help
 

package/docs/project-overview-pdr.md

@@ -10,7 +10,7 @@ Make GitHub Copilot smarter in 30 seconds via curated prompts, agents, and workf
 
 ## Solution
 CoKit CLI installs pre-built resources to `~/.copilot/`:
-- **28 prompts**: ClaudeKit (ck.*) + SpecKit (ck.spec.*)
+- **27 prompts**: ClaudeKit (ck-*) + SpecKit (ck-spec-*)
 - **12 agents**: brainstormer, planner, tester, code-simplifier, fullstack-developer, ui-ux-designer, etc.
 - **27 skills**: debugging, planning, code-review, frontend-design, databases, devops, etc.
 - **5 collections**: bundled workflows
@@ -19,7 +19,7 @@ CoKit CLI installs pre-built resources to `~/.copilot/`:
 
 | Feature | Description |
 |---------|-------------|
-| Two Workflows | `ck.*` (flexible) vs `ck.spec.*` (spec-driven) |
+| Two Workflows | `ck-*` (flexible) vs `ck-spec-*` (spec-driven) |
 | Sync Pipeline | Auto-merge upstream ClaudeKit + SpecKit |
 | Navigation | Cross-command suggestions in all prompts |
 | Global Install | Single `npx cokit-cli init -g` command |
@@ -32,7 +32,7 @@ CoKit CLI installs pre-built resources to `~/.copilot/`:
 ## Success Metrics
 - Install time < 30 seconds
 - Sync time < 30 seconds
-- 28+ prompts available post-install
+- 27+ prompts available post-install
 - 12+ agents available post-install
 - 27+ skills available post-install
 

package/docs/project-roadmap.md

@@ -12,7 +12,7 @@
 CoKit makes it dead-simple for non-technical users to port Claude Code workflow patterns to GitHub Copilot with a single command: `npx cokit-cli init`.
 
 ### Key Features (Current)
-- 28 prompt files with `ck-` and `ck.spec-` prefixes
+- 27 prompt files with `ck-` and `ck-spec-` prefixes
 - 27 specialized skills (debugging, code-review, planning, frontend-design, databases, devops, etc.)
 - 12 expert agents (planner, code-reviewer, debugger, tester, code-simplifier, fullstack-developer, ui-ux-designer, etc.)
 - 5 instructions (backend, frontend, testing, development, research)
@@ -60,10 +60,10 @@ CoKit makes it dead-simple for non-technical users to port Claude Code workflow
 **Status:** COMPLETE (2026-01-06, Enhanced 2026-02-10)
 **Effort:** 4h
 **Deliverables:**
-- 28 prompt files from ClaudeKit + SpecKit
-  - ClaudeKit: `ck.fix`, `ck.plan`, `ck.cook`, `ck.test`, `ck.review`, etc.
-  - SpecKit: `ck.spec.specify`, `ck.spec.clarify`, `ck.spec.plan`, `ck.spec.tasks`, etc.
-- Unified namespace: `ck.*` for all commands
+- 27 prompt files from ClaudeKit + SpecKit
+  - ClaudeKit: `ck-fix`, `ck-plan`, `ck-cook`, `ck-test`, `ck-review`, etc.
+  - SpecKit: `ck-spec-specify`, `ck-spec-clarify`, `ck-spec-plan`, `ck-spec-tasks`, etc.
+- Unified namespace: `ck-*` for all commands
 - Sync pipeline combines upstream sources
 - All prompts follow Copilot format with `mode: agent`
 - 0 critical issues
@@ -162,10 +162,10 @@ CoKit makes it dead-simple for non-technical users to port Claude Code workflow
 ### 2026-02-10 - v1.2.0 Release (SpecKit Integration)
 
 **Resources Expanded:**
-- Prompts: 21 → 28 (added SpecKit spec-driven workflow commands)
+- Prompts: 21 → 27 (added SpecKit spec-driven workflow commands)
 - Agents: 9 → 12 (added code-simplifier, fullstack-developer, ui-ux-designer)
 - Skills: 7 → 27 (major expansion including frontend-design, databases, devops, etc.)
-- Sync Pipeline: Unified ClaudeKit + SpecKit sources into single `ck.*` namespace
+- Sync Pipeline: Unified ClaudeKit + SpecKit sources into single `ck-*` namespace
 
 **Features Added:**
 - Sync pipeline (eng/sync.mjs) for automated upstream merging