cokit-cli 1.2.0 → 1.2.2

package/README.md

@@ -1,6 +1,7 @@
 # CoKit
 
 Make GitHub Copilot smarter in 30 seconds.
+Check it out at https://camping89.github.io/cokit/index.html
 
 ## Installation
 
@@ -23,99 +24,109 @@ That's it! All CoKit resources are now available in your Copilot.
 After installation, use commands in GitHub Copilot chat:
 
 ```
-/ck.plan "Add user authentication"
-/ck.fix "Login button not working"
-/ck.test
+/ck-plan "Add user authentication"
+/ck-fix "Login button not working"
+/ck-test
 ```
 
 ## Sample Workflows
 
 ### Quick Fix (5 min)
 ```
-/ck.fix "Users can't upload files larger than 5MB"
+/ck-fix "Users can't upload files larger than 5MB"
 ```
 Done. Single command handles analysis and fix.
 
 ### Small Feature (30 min)
 ```
-/ck.plan.fast "Add dark mode toggle"
+/ck-plan-fast "Add dark mode toggle"
 → implement
-/ck.test
-/ck.fix  (if tests fail)
+/ck-test
+/ck-fix  (if tests fail)
 ```
 
 ### Medium Feature (2-4 hours)
 ```
-/ck.plan.hard "Add payment integration with Stripe"
+/ck-plan-hard "Add payment integration with Stripe"
 → implement phase by phase
-/ck.test
-/ck.review
+/ck-test
+/ck-review
 ```
 
 ### Complex Feature (multi-day)
 ```
-/ck.spec.specify "Multi-tenant SaaS billing system"
-/ck.spec.clarify  (answer questions)
-/ck.spec.plan
-/ck.spec.tasks
-/ck.spec.implement
-/ck.test
+/ck-spec-specify "Multi-tenant SaaS billing system"
+/ck-spec-clarify  (answer questions)
+/ck-spec-plan
+/ck-spec-tasks
+/ck-spec-implement
+/ck-test
 ```
 
 ## Command Reference
 
-### Daily Development (`ck.*`)
+### Daily Development (`ck-*`)
 
 | Command | When to Use |
 |---------|-------------|
-| `/ck.fix` | Fix bugs, errors, issues |
-| `/ck.test` | Run and analyze tests |
-| `/ck.plan.fast` | Quick feature (< 2 hours) |
-| `/ck.plan.hard` | Feature needing research |
-| `/ck.ask` | Technical questions |
-| `/ck.review` | Code review |
-| `/ck.bootstrap` | Start new project |
+| `/ck-fix` | Fix bugs, errors, issues |
+| `/ck-test` | Run and analyze tests |
+| `/ck-plan-fast` | Quick feature (< 2 hours) |
+| `/ck-plan-hard` | Feature needing research |
+| `/ck-ask` | Technical questions |
+| `/ck-review` | Code review |
+| `/ck-bootstrap` | Start new project |
 
-### Spec-Driven (`ck.spec.*`)
+### Spec-Driven (`ck-spec-*`)
 
 For complex features needing formal requirements:
 
 | Command | When to Use |
 |---------|-------------|
-| `/ck.spec.specify` | Create formal specification |
-| `/ck.spec.clarify` | Resolve ambiguities |
-| `/ck.spec.plan` | Generate implementation plan |
-| `/ck.spec.tasks` | Break into tasks |
-| `/ck.spec.implement` | Execute tasks |
+| `/ck-spec-specify` | Create formal specification |
+| `/ck-spec-clarify` | Resolve ambiguities |
+| `/ck-spec-plan` | Generate implementation plan |
+| `/ck-spec-tasks` | Break into tasks |
+| `/ck-spec-implement` | Execute tasks |
 
 ## Which Workflow?
 
 ```
 Is this a bug fix?
-  → /ck.fix
+  → /ck-fix
 
 Is this < 2 hours work?
-  → /ck.plan.fast
+  → /ck-plan-fast
 
 Do you need formal requirements?
-  → /ck.spec.specify (spec-driven flow)
+  → /ck-spec-specify (spec-driven flow)
 
 Otherwise?
-  → /ck.plan.hard (research + plan)
+  → /ck-plan-hard (research + plan)
 ```
 
 ## What's Included
 
 | Resource | Count | Purpose |
 |----------|-------|---------|
-| Prompts | 28 | Commands for Copilot |
+| Prompts | 27 | Commands for Copilot |
 | Agents | 12 | Specialized AI assistants |
-| Skills | 27 | Domain expertise |
+| Skills | 23 | Domain expertise |
 | Instructions | 5 | Context-aware rules |
 | Collections | 5 | Bundled workflows |
 
 See [docs/](docs/) for detailed resource documentation.
 
+## What's New (v1.2.2)
+
+Full Copilot format compliance audit and cleanup:
+- Removed all Claude Code-specific references (tool names, agent patterns, API params)
+- Fixed frontmatter fields to match official Copilot specs across all file types
+- Rewrote `ck-preview` execution for Copilot's `execute/runInTerminal`
+- Cleaned up 45 files (agents, prompts, skills)
+
+See [CHANGELOG.md](CHANGELOG.md) for full history.
+
 ## Documentation
 
 - [Commands Usage Guide](docs/cokit-commands-usage-guide.md) - When to use each command

package/agents/brainstormer.agent.md

@@ -37,7 +37,7 @@ You operate by the holy trinity of software engineering: **YAGNI** (You Aren't G
 ## Collaboration Tools
 - Consult the `planner` agent to research industry best practices and find proven solutions
 - Engage the `docs-manager` agent to understand existing project implementation and constraints
-- Use `WebSearch` tool to find efficient approaches and learn from others' experiences
+- Search the web to find efficient approaches and learn from others' experiences
 
 ## Workflow Phases
 1. **Discovery Phase**: Ask clarifying questions about requirements, constraints, timeline, and success criteria

package/agents/debugger.agent.md

@@ -37,7 +37,7 @@ When investigating issues, you will:
    - Examine application logs and error traces
    - Capture system metrics and performance data
    - Read `./docs/codebase-summary.md` if exists and up-to-date (less than 2 days old)
-   - Use Glob/Grep tools to search the codebase for files needed to complete the task
+   - Search the codebase for files needed to complete the task
    - When given a Github repository URL, use `repomix --remote <github-repo-url>` to generate codebase summary:
       ```bash
       # usage: repomix --remote <github-repo-url>

package/agents/docs-manager.agent.md

@@ -21,7 +21,7 @@ You establish and maintain implementation standards including:
 
 ### 2. Documentation Analysis & Maintenance
 You systematically:
-- Read and analyze all existing documentation files in `./docs` directory using Glob and Read tools
+- Read and analyze all existing documentation files in `./docs` directory
 - Identify gaps, inconsistencies, or outdated information
 - Cross-reference documentation with actual codebase implementation
 - Ensure documentation reflects the current state of the system
@@ -57,7 +57,7 @@ You organize documentation to:
 ### Documentation Review Process
 1. Scan the entire `./docs` directory structure
 2. Generate/update `./docs/codebase-summary.md` with comprehensive codebase summary
-3. Use Glob/Grep tools OR Gemini CLI for large files
+3. Search for content in files OR use Gemini CLI for large files
 4. Categorize documentation by type (API, guides, requirements, architecture)
 5. Check for completeness, accuracy, and clarity
 6. Verify all links, references, and code examples

package/agents/git-manager.agent.md

@@ -296,10 +296,10 @@ Keep output concise (<1k chars). No explanations of what you did.
 ## Token Optimization Strategy
 
 **Delegation rationale:**
-- Gemini Flash 2.5: $0.075/$0.30 per 1M tokens
-- Haiku 4.5: $1/$5 per 1M tokens
-- For 100-line diffs, Gemini = **13x cheaper** for analysis
-- Haiku focuses on orchestration, Gemini does heavy lifting
+- Worker model (e.g. Gemini Flash 2.5): $0.075/$0.30 per 1M tokens
+- Orchestrator model: $1/$5 per 1M tokens
+- For 100-line diffs, worker model = **13x cheaper** for analysis
+- Orchestrator focuses on routing, worker model does heavy lifting
 
 **Efficiency rules:**
 1. **Compound commands only** - use `&&` to chain operations
@@ -314,7 +314,7 @@ Keep output concise (<1k chars). No explanations of what you did.
 - 3 tools @ 5K tokens = $0.015 per commit
 - **81% cost reduction** × 1000 commits/month = $63 saved
 
-## Critical Instructions for Haiku
+## Critical Instructions for Orchestrator
 
 Your role: **EXECUTE, not EXPLORE**
 

package/agents/planner.agent.md

@@ -19,9 +19,9 @@ You operate by **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, S
 
 When Read fails with "exceeds maximum allowed tokens":
 1. **Gemini CLI** (2M context): `echo "[question] in [path]" | gemini -y -m gemini-2.5-flash`
-2. **Chunked Read**: Use `offset` and `limit` params to read in portions
-3. **Grep**: Search specific content with `Grep pattern="[term]" path="[path]"`
-4. **Targeted Search**: Use Glob and Grep for specific patterns
+2. Read file in portions using offset and limit parameters
+3. Search for specific content in files
+4. Search for specific file and content patterns
 
 ## Core Mental Models (The "How to Think" Toolkit)
 

package/agents/researcher.agent.md

@@ -24,7 +24,6 @@ You excel at:
 - Recognizing technology trends and adoption patterns
 - Evaluating trade-offs between different technical solutions
 - Using `docs-seeker` skills to find relevant documentation
-- Using `document-skills` skills to read and analyze documents
 **IMPORTANT**: You **DO NOT** start the implementation yourself but respond with the summary and the file path of comprehensive plan.
 
 ## Report Output

package/agents/scout.agent.md

@@ -9,7 +9,7 @@ You are an elite Codebase Scout, a specialized agent designed to rapidly locate
 
 ## Your Core Mission
 
-When given a search task, you will use Glob, Grep, and Read tools to efficiently search the codebase and synthesize findings into a comprehensive file list for the user.
+When given a search task, you will use search and file reading capabilities to efficiently search the codebase and synthesize findings into a comprehensive file list for the user.
 Requirements: **Ensure token efficiency while maintaining high quality.**
 
 ## Operational Protocol
@@ -38,8 +38,8 @@ Example prompt structure:
 "Search the [directories] for files related to [functionality]. Look for [specific patterns like API routes, schema definitions, utility functions]. Return only the file paths that are directly relevant. Be concise and fast - you have 3 minutes."
 
 ### 4. Execute Parallel Searches
-- Use Glob tool with multiple patterns 
-- Use Grep for content-based searches
+- Search with multiple file patterns
+- Search file contents for specific patterns
 - Read key files to understand structure
 - Complete searches within 3-minute target
 
@@ -50,7 +50,7 @@ Example prompt structure:
 
 ## Search Tools
 
-Use Glob, Grep, and Read tools for efficient codebase exploration.
+Use search and file reading for efficient codebase exploration.
 
 ## Example Execution Flow
 
@@ -79,19 +79,19 @@ Use Glob, Grep, and Read tools for efficient codebase exploration.
 
 - If results are sparse: Expand search scope or try different keywords
 - If results are overwhelming: Categorize and prioritize by relevance
-- If Read fails on large files: Use chunked reading or Grep for specific content
+- If Read fails on large files: Use chunked reading or content search for specific content
 
 ## Handling Large Files (>25K tokens)
 
 When Read fails with "exceeds maximum allowed tokens":
 1. **Gemini CLI** (2M context): `echo "[question] in [path]" | gemini -y -m gemini-2.5-flash`
-2. **Chunked Read**: Use `offset` and `limit` params to read in portions
-3. **Grep**: Search specific content with `Grep pattern="[term]" path="[path]"`
+2. Read file in portions using offset and limit parameters
+3. Search for specific content in files
 
 ## Success Criteria
 
 You succeed when:
-1. You execute searches efficiently using Glob, Grep, and Read tools
+1. You execute searches efficiently using search and file reading capabilities
 2. You synthesize results into a clear, actionable file list
 3. The user can immediately proceed with their task using the files you found
 4. You complete the entire operation in under 5 minutes
@@ -104,4 +104,4 @@ Save reports to `plans/reports/` directory with naming pattern `{type}-{date}-{s
 - Sacrifice grammar for the sake of concision when writing reports.
 - In reports, list any unresolved questions at the end, if any.
 
-**Remember:** You are a fast, focused searcher. Your power lies in efficiently using Glob, Grep, and Read tools to quickly locate relevant files.
+**Remember:** You are a fast, focused searcher. Your power lies in efficiently searching and reading files to quickly locate relevant content.

package/agents/ui-ux-designer.agent.md

@@ -54,5 +54,4 @@ Activate relevant skills based on task:
 ## Collaboration
 
 - Delegate research to `researcher` agents for comprehensive insights
-- Coordinate with `project-manager` for progress updates
 - Follow rules in `./docs/development-rules.md`

package/collections/ck-orchestration.collection.yml

@@ -1,7 +1,7 @@
 id: ck-orchestration
 name: CK Orchestration Protocol
-description: Workflow orchestration patterns for managing subagents, task delegation, and multi-phase implementations.
-tags: [orchestration, workflow, subagents, planning]
+description: Workflow orchestration patterns for managing agents, task delegation, and multi-phase implementations.
+tags: [orchestration, workflow, agents, planning]
 items:
   - path: agents/planner.agent.md
     kind: agent

package/docs/README.md

@@ -8,7 +8,7 @@
 | # | Doc | Purpose |
 |---|-----|---------|
 | 1 | [../README.md](../README.md) | Installation & sample workflows |
-| 2 | [cokit-commands-usage-guide.md](cokit-commands-usage-guide.md) | When to use `ck.*` vs `ck.spec.*` |
+| 2 | [cokit-commands-usage-guide.md](cokit-commands-usage-guide.md) | When to use `ck-*` vs `ck-spec-*` |
 
 ### Team Members (Understanding CoKit)
 | # | Doc | Purpose |
@@ -44,7 +44,7 @@
 ### What's in CoKit?
 | Resource | Count | Location |
 |----------|-------|----------|
-| Prompts | 28 | `prompts/ck-*.prompt.md` |
+| Prompts | 27 | `prompts/ck-*.prompt.md` |
 | Agents | 12 | `agents/*.agent.md` |
 | Skills | 27 | `skills/*/` |
 | Instructions | 5 | `instructions/ck-*.instructions.md` |
@@ -53,15 +53,15 @@
 ### Two Workflows
 | Workflow | Commands | Best For |
 |----------|----------|----------|
-| ClaudeKit | `ck.*` | Daily dev, quick fixes |
-| SpecKit | `ck.spec.*` | Complex features, formal specs |
+| ClaudeKit | `ck-*` | Daily dev, quick fixes |
+| SpecKit | `ck-spec-*` | Complex features, formal specs |
 
 ### Key Commands
 ```
-/ck.fix          → Fix bugs
-/ck.plan.fast    → Quick feature
-/ck.plan.hard    → Research + plan
-/ck.spec.specify → Formal specification
+/ck-fix          → Fix bugs
+/ck-plan-fast    → Quick feature
+/ck-plan-hard    → Research + plan
+/ck-spec-specify → Formal specification
 ```
 
 ---

package/docs/codebase-summary.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-CoKit is a CLI tool that enhances GitHub Copilot with 28 prompts, 12 agents, 5 instructions, 27 skills, and 5 collections. The tool unifies two upstream sources (ClaudeKit and SpecKit) into a single ck.* namespace.
+CoKit is a CLI tool that enhances GitHub Copilot with 27 prompts, 12 agents, 5 instructions, 27 skills, and 5 collections. The tool unifies two upstream sources (ClaudeKit and SpecKit) into a single ck-* namespace.
 
 **Repository:** https://github.com/camping89/cokit.git
 **Version:** 1.2.0
@@ -23,7 +23,7 @@ Merge Results
     ↓
 Patch Navigation (Inject workflow footers)
     ↓
-Output: Unified ck.* Prompts
+Output: Unified ck-* Prompts
 ```
 
 ### Sync Pipeline (eng/sync.mjs)
@@ -91,7 +91,7 @@ Registers 5 commands using Commander.js:
 **Flow:**
 1. Load resource-origins.yml configuration
 2. Transform ClaudeKit and SpecKit sources in parallel
-3. Merge results (total: 28 prompts)
+3. Merge results (total: 27 prompts)
 4. Apply navigation patches to all prompts
 5. Write output files or show dry-run preview
 6. Update sync timestamps
@@ -113,10 +113,10 @@ navigation: {}        # Workflow navigation rules
 #### ClaudeKit Transformer (transform-claudekit.mjs)
 **Input:** ~/.claude/commands/ (user's local ClaudeKit)
 **Transformations:**
-- Rename: `/*` → `ck.*` namespace
+- Rename: `/*` → `ck-*` namespace
 - Replace: `$ARGUMENTS` → `${input}`
 - Remove `model` field from frontmatter
-- Update handoff references to ck.* commands
+- Update handoff references to ck-* commands
 - Transform command references in content
 
 **Functions:**
@@ -129,14 +129,14 @@ navigation: {}        # Workflow navigation rules
 #### SpecKit Transformer (transform-speckit.mjs)
 **Input:** upstream/speckit/templates/commands/
 **Transformations:**
-- Rename: `/speckit.*` → `/ck.*`
+- Rename: `/speckit-*` → `/ck-*`
 - Replace: `$ARGUMENTS` → `${input}`
 - Remove `model` field from frontmatter
-- Update handoff references to ck.* commands
+- Update handoff references to ck-* commands
 
 **Functions:**
 - `transformFile()` - Apply transformations
-- `transformCommandReference()` - Update handoffs (speckit.* → ck.*)
+- `transformCommandReference()` - Update handoffs (speckit-* → ck-*)
 - `transformContentReferences()` - Replace content references
 
 ### 4. Navigation Patcher (patch-navigation.mjs)
@@ -173,8 +173,8 @@ Maintains mappings and sync metadata.
 ### ClaudeKit Commands (12)
 12 prompts from ~/.claude/commands/ (plan, fix, test, ask, bootstrap, review, watzup, journal, preview, help, plan.hard, plan.fast)
 
-### SpecKit Commands (9)
-9 prompts from upstream/speckit (specify, clarify, constitution, plan, tasks, implement, analyze, checklist, taskstoissues)
+### SpecKit Commands (8)
+8 prompts from upstream/speckit (specify, clarify, constitution, plan, tasks, implement, analyze, checklist)
 
 ## Dependencies
 
@@ -203,8 +203,8 @@ npm run build            # Update README
 ### Sync Operation
 1. **Config Load** - Read resource-origins.yml
 2. **Parallel Transform:**
-   - ClaudeKit: Glob ~/.claude/commands → Transform → Output ck.* prompts
-   - SpecKit: Glob upstream/speckit/templates/commands → Transform → Output ck.* prompts
+   - ClaudeKit: Glob ~/.claude/commands → Transform → Output ck-* prompts
+   - SpecKit: Glob upstream/speckit/templates/commands → Transform → Output ck-* prompts
 3. **Merge** - Combine results (21 total)
 4. **Patch Navigation** - Inject workflow footers
 5. **Write Output** - Create prompt files (prompts/ directory)
@@ -217,14 +217,14 @@ Input (ClaudeKit)
 ├── Content: "Run $ARGUMENTS using /fix command"
 ↓
 Transform
-├── Rename: ck.plan
+├── Rename: ck-plan
 ├── Replace: $ARGUMENTS → ${input}
-├── Update: /fix → /ck.fix
+├── Update: /fix → /ck-fix
 ├── Remove: model field
 ↓
-Output (ck.*)
-├── Frontmatter: {name: "ck.plan", ...}
-├── Content: "Run ${input} using /ck.fix command"
+Output (ck-*)
+├── Frontmatter: {name: "ck-plan", ...}
+├── Content: "Run ${input} using /ck-fix command"
 ├── Navigation Footer: "Suggested Next Steps"
 ```
 
@@ -245,11 +245,11 @@ Output (ck.*)
 5. **Parallel Processing:** Concurrent ClaudeKit + SpecKit transforms
 6. **Graceful Degradation:** Continues if sources unavailable
 7. **Frontmatter Management:** Preserves metadata, removes model field
-8. **Content Reference Updates:** Transforms all command references to ck.* namespace
+8. **Content Reference Updates:** Transforms all command references to ck-* namespace
 
 ## Version History
 
-- **v1.2.0** (Current) - 28 prompts, 12 agents, 27 skills
+- **v1.2.0** (Current) - 27 prompts, 12 agents, 27 skills
 - **v1.1.0** - 21 prompts (12 ClaudeKit + 9 SpecKit), SpecKit sync pipeline
 - **v1.0.9** - Comprehensive documentation update
 - **v1.0.8** - Initial release

package/docs/cokit-commands-usage-guide.md

@@ -6,22 +6,22 @@ When to use which command workflow.
 
 | Need | Command | Workflow |
 |------|---------|----------|
-| **Quick implementation** | `ck.plan.fast` | ClaudeKit |
-| **Deep research + plan** | `ck.plan.hard` | ClaudeKit |
-| **Formal spec from idea** | `ck.spec.specify` | SpecKit |
-| **Fix a bug** | `ck.fix` | ClaudeKit |
-| **Run tests** | `ck.test` | ClaudeKit |
+| **Quick implementation** | `ck-plan-fast` | ClaudeKit |
+| **Deep research + plan** | `ck-plan-hard` | ClaudeKit |
+| **Formal spec from idea** | `ck-spec-specify` | SpecKit |
+| **Fix a bug** | `ck-fix` | ClaudeKit |
+| **Run tests** | `ck-test` | ClaudeKit |
 
 ---
 
 ## Two Workflows
 
-### ClaudeKit (`ck.*`) - Flexible, Fast
+### ClaudeKit (`ck-*`) - Flexible, Fast
 
 Best for: **Day-to-day development**, quick fixes, exploration.
 
 ```
-ck.plan.fast → ck.test → ck.fix
+ck-plan-fast → ck-test → ck-fix
 ```
 
 **When to use:**
@@ -34,23 +34,23 @@ ck.plan.fast → ck.test → ck.fix
 **Commands:**
 | Command | Description |
 |---------|-------------|
-| `ck.plan` | Create implementation plan |
-| `ck.plan.fast` | Quick plan, no research |
-| `ck.plan.hard` | Deep research + plan |
-| `ck.fix` | Fix issues |
-| `ck.test` | Run tests |
-| `ck.ask` | Answer questions |
-| `ck.review` | Review codebase |
-| `ck.bootstrap` | Start new project |
+| `ck-plan` | Create implementation plan |
+| `ck-plan-fast` | Quick plan, no research |
+| `ck-plan-hard` | Deep research + plan |
+| `ck-fix` | Fix issues |
+| `ck-test` | Run tests |
+| `ck-ask` | Answer questions |
+| `ck-review` | Review codebase |
+| `ck-bootstrap` | Start new project |
 
 ---
 
-### SpecKit (`ck.spec.*`) - Structured, Rigorous
+### SpecKit (`ck-spec-*`) - Structured, Rigorous
 
 Best for: **Complex features**, team collaboration, formal requirements.
 
 ```
-ck.spec.specify → ck.spec.clarify → ck.spec.plan → ck.spec.tasks → ck.spec.implement
+ck-spec-specify → ck-spec-clarify → ck-spec-plan → ck-spec-tasks → ck-spec-implement
 ```
 
 **When to use:**
@@ -63,14 +63,13 @@ ck.spec.specify → ck.spec.clarify → ck.spec.plan → ck.spec.tasks → ck.sp
 **Commands:**
 | Command | Description |
 |---------|-------------|
-| `ck.spec.specify` | Create formal spec from idea |
-| `ck.spec.clarify` | Ask clarification questions |
-| `ck.spec.plan` | Generate plan from spec |
-| `ck.spec.tasks` | Break plan into tasks |
-| `ck.spec.implement` | Execute tasks |
-| `ck.spec.analyze` | Check consistency |
-| `ck.spec.checklist` | Validate requirements |
-| `ck.spec.taskstoissues` | Export to GitHub Issues |
+| `ck-spec-specify` | Create formal spec from idea |
+| `ck-spec-clarify` | Ask clarification questions |
+| `ck-spec-plan` | Generate plan from spec |
+| `ck-spec-tasks` | Break plan into tasks |
+| `ck-spec-implement` | Execute tasks |
+| `ck-spec-analyze` | Check consistency |
+| `ck-spec-checklist` | Validate requirements |
 
 ---
 
@@ -78,17 +77,17 @@ ck.spec.specify → ck.spec.clarify → ck.spec.plan → ck.spec.tasks → ck.sp
 
 ```
 Is this a bug fix?
-  └─ Yes → ck.fix
+  └─ Yes → ck-fix
 
 Is this < 4 hours work?
-  └─ Yes → ck.plan.fast
+  └─ Yes → ck-plan-fast
 
 Do you need formal requirements?
-  └─ Yes → ck.spec.specify → ck.spec.* flow
-  └─ No  → ck.plan.hard → ck.* flow
+  └─ Yes → ck-spec-specify → ck-spec-* flow
+  └─ No  → ck-plan-hard → ck-* flow
 
 Are you exploring/prototyping?
-  └─ Yes → ck.plan.fast (skip spec)
+  └─ Yes → ck-plan-fast (skip spec)
 ```
 
 ---
@@ -97,25 +96,25 @@ Are you exploring/prototyping?
 
 ### Scenario 1: Fix a Login Bug
 ```
-/ck.fix "Users can't login with email containing +"
+/ck-fix "Users can't login with email containing +"
 ```
 Single command. Done.
 
 ### Scenario 2: Add Dark Mode (Small Feature)
 ```
-/ck.plan.fast "Add dark mode toggle"
-/ck.test
-/ck.fix  (if tests fail)
+/ck-plan-fast "Add dark mode toggle"
+/ck-test
+/ck-fix  (if tests fail)
 ```
 
 ### Scenario 3: Payment Integration (Complex Feature)
 ```
-/ck.spec.specify "Integrate Stripe payments for subscriptions"
-/ck.spec.clarify  (answer questions about tiers, regions, etc.)
-/ck.spec.plan
-/ck.spec.tasks
-/ck.spec.implement
-/ck.test
+/ck-spec-specify "Integrate Stripe payments for subscriptions"
+/ck-spec-clarify  (answer questions about tiers, regions, etc.)
+/ck-spec-plan
+/ck-spec-tasks
+/ck-spec-implement
+/ck-test
 ```
 
 ---
@@ -123,9 +122,9 @@ Single command. Done.
 ## Mixing Workflows
 
 You can mix them:
-- Start with `ck.spec.specify` for formal spec
-- Use `ck.fix` when bugs arise during implementation
-- Use `ck.test` regardless of workflow
+- Start with `ck-spec-specify` for formal spec
+- Use `ck-fix` when bugs arise during implementation
+- Use `ck-test` regardless of workflow
 
 ---