cokit-cli 1.2.0 → 1.2.3

package/prompts/ck-preview.prompt.md

@@ -5,29 +5,27 @@ argument-hint: 'Path to markdown file or directory'
 tools: ['execute/runInTerminal', 'execute/getTerminalOutput']
 ---
 
-Universal viewer using `markdown-novel-viewer` skill - pass ANY path and see it rendered nicely.
+Universal viewer - pass ANY path and see it rendered nicely.
 
 ## Usage
 
-- `/ck.preview <file.md>` - View markdown file in novel-reader UI
-- `/ck.preview <directory/>` - Browse directory contents
-- `/ck.preview --stop` - Stop running server
+- `/ck-preview <file.md>` - View markdown file in novel-reader UI
+- `/ck-preview <directory/>` - Browse directory contents
+- `/ck-preview --stop` - Stop running server
 
 ## Examples
 
 ```bash
-/ck.preview plans/my-plan/ck.plan.md     # View markdown file
-/ck.preview plans/                    # Browse plans directory
-/ck.preview docs/                     # Browse docs directory
-/ck.preview any/path/to/file.md      # View any markdown file
-/ck.preview any/path/                 # Browse any directory
+/ck-preview plans/my-plan/ck-plan.md     # View markdown file
+/ck-preview plans/                    # Browse plans directory
+/ck-preview docs/                     # Browse docs directory
+/ck-preview any/path/to/file.md      # View any markdown file
+/ck-preview any/path/                 # Browse any directory
 ```
 
 ## Execution
 
-**IMPORTANT:** Run server as Claude Code background task using `run_in_background: true` with the Bash tool. This makes the server visible in `/tasks` and manageable via `KillShell`.
-
-The skill is located at `$HOME/.copilot/skills/markdown-novel-viewer/`.
+Run the server using `#tool:execute/runInTerminal`. The skill is located at `$HOME/.copilot/skills/markdown-novel-viewer/`.
 
 ### Stop Server
 
@@ -39,11 +37,11 @@ node $HOME/.copilot/skills/markdown-novel-viewer/scripts/server.cjs --stop
 
 ### Start Server
 
-Otherwise, run the `markdown-novel-viewer` server as CC background task with `--foreground` flag (keeps process alive for CC task management):
+Otherwise, run the `markdown-novel-viewer` server with `--foreground` flag:
 
 ```bash
 # Determine if path is file or directory
-INPUT_PATH="{{path}}"
+INPUT_PATH="${input}"
 if [[ -d "$INPUT_PATH" ]]; then
   # Directory mode - browse
   node $HOME/.copilot/skills/markdown-novel-viewer/scripts/server.cjs \
@@ -61,25 +59,10 @@ else
 fi
 ```
 
-**Critical:** When calling the Bash tool:
-- Set `run_in_background: true` to run as CC background task
-- Set `timeout: 300000` (5 minutes) to prevent premature termination
-- Parse JSON output and report URL to user
-
-Example Bash tool call:
-```json
-{
-  "command": "node $HOME/.copilot/skills/markdown-novel-viewer/scripts/server.cjs --dir \"path\" --host 0.0.0.0 --open --foreground",
-  "run_in_background": true,
-  "timeout": 300000,
-  "description": "Start preview server in background"
-}
-```
-
 After starting, parse the JSON output (e.g., `{"success":true,"url":"http://localhost:3456/view?file=...","networkUrl":"http://192.168.1.x:3456/view?file=..."}`) and report:
 - Local URL for browser access
 - Network URL for remote device access (if available)
-- Inform user that server is now running as CC background task (visible in `/tasks`)
+- Inform user that server is now running in the terminal; stop it by running the stop command
 
 **CRITICAL:** MUST display the FULL URL including path and query string (e.g., `http://localhost:3456/view?file=/path/to/file.md`). NEVER truncate to just `host:port` (e.g., `http://localhost:3456`). The full URL is required for direct file access.
 
@@ -89,5 +72,6 @@ After starting, parse the JSON output (e.g., `{"success":true,"url":"http://loca
 
 | Command | Description |
 |---------|-------------|
-| `/ck.brainstorm` | Explore ideas |
-| `/ck.plan` | Create plan |
+| `/ck-brainstorm` | Explore ideas |
+| `/ck-plan` | Create plan |
+| `/ck-spec-specify` | Write detailed feature spec |

package/prompts/ck-review.prompt.md

@@ -4,7 +4,7 @@ description: 'Scan and analyze the codebase'
 argument-hint: 'Tasks or prompt to review'
 ---
 
-Think harder to scan the codebase and analyze it follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
+Think harder to scan the codebase and analyze it follow the Orchestration Protocol, Core Responsibilities, Agents Team and Development Rules:
 <tasks>${input}</tasks>
 
 ---
@@ -23,31 +23,29 @@ Think harder to scan the codebase and analyze it follow the Orchestration Protoc
 
 ### Research
 
-* Use 2 `researcher` subagents in parallel to search up to max 5 sources for the user's request, idea validation, best practices, challenges, and find the best possible solutions.
+* Use 2 `researcher` agents in parallel to search up to max 5 sources for the user's request, idea validation, best practices, challenges, and find the best possible solutions.
 * Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
-* Use `/scout:ext` (preferred) or `/scout` (fallback) slash command to search the codebase for files needed to complete the task
+* Use `/ck-scout` slash command to search the codebase for files needed to complete the task
 
 ### Code Review
 
-* After finishing, use multiple `code-reviewer` subagents in parallel to review code. 
+* After finishing, use multiple `code-reviewer` agents in parallel to review code. 
 * If there are any issues, duplicate code, or security vulnerabilities, ask main agent to improve the code and repeat the "Testing" process until all tests pass. 
 * When all tests pass, code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
 * **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
 
 ### Plan
-* Use `planner` subagent to analyze reports from `researcher` and `scout` subagents to create an improvement plan following the progressive disclosure structure:
+* Use `planner` agent to analyze reports from `researcher` and `scout` agents to create an improvement plan following the progressive disclosure structure:
   - Create a directory using naming pattern from `## Naming` section.
   - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
   - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
 
 ### Final Report
 * Report back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.
-* Ask the user if they want to commit and push to git repository, if yes, use `git-manager` subagent to commit and push to git repository.
+* Ask the user if they want to commit and push to git repository, if yes, use `git-manager` agent to commit and push to git repository.
 
 **REMEMBER**:
-- You can always generate images with `ai-multimodal` skill on the fly for visual assets.
-- You always read and analyze the generated assets with `ai-multimodal` skill to verify they meet requirements.
-- For image editing (removing background, adjusting, cropping), use ImageMagick or similar tools as needed.
+- Always verify generated assets meet design requirements before proceeding.
 
 ---
 
@@ -55,5 +53,6 @@ Think harder to scan the codebase and analyze it follow the Orchestration Protoc
 
 | Command | Description |
 |---------|-------------|
-| `/ck.brainstorm` | Explore ideas |
-| `/ck.plan` | Create plan |
+| `/ck-fix` | Fix issues found in review |
+| `/ck-git` | Commit changes |
+| `/ck-spec-checklist` | Validate against spec requirements |

package/prompts/ck-scout.prompt.md

@@ -34,7 +34,7 @@ Fast, token-efficient codebase scouting to find files needed for tasks.
 - Ensure no overlap, maximize coverage
 
 ### 3. Execute Parallel Searches
-Use Glob and Grep with wide range of patterns:
+Search the codebase with a wide range of patterns:
 - File patterns: `**/*.ts`, `**/*.tsx`, `**/*.md`
 - Content patterns: function names, class names, keywords
 - Directory patterns: `src/`, `lib/`, `components/`
@@ -79,6 +79,7 @@ Use Glob and Grep with wide range of patterns:
 
 | Command | Description |
 |---------|-------------|
-| `/ck.plan` | Create implementation plan |
-| `/ck.cook` | Implement feature |
-| `/ck.ask` | Ask technical questions |
+| `/ck-plan` | Create implementation plan |
+| `/ck-cook` | Implement feature |
+| `/ck-ask` | Ask technical questions |
+| `/ck-spec-analyze` | Cross-artifact consistency check |

package/prompts/ck-simplify.prompt.md

@@ -41,6 +41,6 @@ Scope:
 
 | Command | Description |
 |---------|-------------|
-| `/ck.test` | Run tests to verify nothing broke |
-| `/ck.review` | Code review the simplified code |
-| `/ck.git` | Commit changes |
+| `/ck-test` | Run tests to verify nothing broke |
+| `/ck-review` | Code review the simplified code |
+| `/ck-git` | Commit changes |

package/prompts/ck-spec-analyze.prompt.md

@@ -1,9 +1,6 @@
 ---
 agent: 'agent'
 description: 'Cross-artifact consistency and quality analysis across spec, plan, and tasks'
-scripts:
-  sh: spec-kit/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks
-  ps: spec-kit/scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks
 ---
 
 ## User Input
@@ -16,13 +13,13 @@ You **MUST** consider the user input before proceeding (if not empty).
 
 ## Goal
 
-Identify inconsistencies, duplications, ambiguities, and underspecified items across the three core artifacts (`spec.md`, `plan.md`, `tasks.md`) before implementation. This command MUST run only after `/ck.spec.tasks` has successfully produced a complete `tasks.md`.
+Identify inconsistencies, duplications, ambiguities, and underspecified items across the three core artifacts (`spec.md`, `plan.md`, `tasks.md`) before implementation. This command MUST run only after `/ck-spec-tasks` has successfully produced a complete `tasks.md`.
 
 ## Operating Constraints
 
 **STRICTLY READ-ONLY**: Do **not** modify any files. Output a structured analysis report. Offer an optional remediation plan (user must explicitly approve before any follow-up editing commands would be invoked manually).
 
-**Constitution Authority**: The project constitution (`constitution.md` at project root) is **non-negotiable** within this analysis scope. Constitution conflicts are automatically CRITICAL and require adjustment of the spec, plan, or tasks—not dilution, reinterpretation, or silent ignoring of the principle. If a principle itself needs to change, that must occur in a separate, explicit constitution update outside `/ck.spec.analyze`.
+**Constitution Authority**: The project constitution (`constitution.md` at project root) is **non-negotiable** within this analysis scope. Constitution conflicts are automatically CRITICAL and require adjustment of the spec, plan, or tasks—not dilution, reinterpretation, or silent ignoring of the principle. If a principle itself needs to change, that must occur in a separate, explicit constitution update outside `/ck-spec-analyze`.
 
 ## Execution Steps
 
@@ -161,9 +158,9 @@ Output a Markdown report (no file writes) with the following structure:
 
 At end of report, output a concise Next Actions block:
 
-- If CRITICAL issues exist: Recommend resolving before `/ck.spec.implement`
+- If CRITICAL issues exist: Recommend resolving before `/ck-spec-implement`
 - If only LOW/MEDIUM: User may proceed, but provide improvement suggestions
-- Provide explicit command suggestions: e.g., "Run /ck.spec.specify with refinement", "Run /ck.spec.plan to adjust architecture", "Manually edit tasks.md to add coverage for 'performance-metrics'"
+- Provide explicit command suggestions: e.g., "Run /ck-spec-specify with refinement", "Run /ck-spec-plan to adjust architecture", "Manually edit tasks.md to add coverage for 'performance-metrics'"
 
 ### 8. Offer Remediation
 
@@ -196,8 +193,9 @@ Ask the user: "Would you like me to suggest concrete remediation edits for the t
 
 | Command | Description | When to Use |
 |---------|-------------|-------------|
-| `/ck.spec.implement` | Start implementation | Analysis passed, no critical issues |
-| `/ck.spec.clarify` | Clarify requirements | Analysis found ambiguities in spec |
-| `/ck.spec.tasks` | Regenerate tasks | Task coverage gaps identified |
+| `/ck-spec-implement` | Start implementation | Analysis passed, no critical issues |
+| `/ck-spec-clarify` | Clarify requirements | Analysis found ambiguities in spec |
+| `/ck-spec-tasks` | Regenerate tasks | Task coverage gaps identified |
+| `/ck-fix` | Fix issues found in analysis | Code-level bugs identified |
 
-**Workflow:** `/ck.spec.analyze` → fix issues → `/ck.spec.implement`
+**Workflow:** `/ck-spec-analyze` → fix issues → `/ck-spec-implement`

package/prompts/ck-spec-checklist.prompt.md

@@ -1,9 +1,6 @@
 ---
 agent: 'agent'
 description: 'Generate a custom checklist for the current feature based on user requirements'
-scripts:
-  sh: spec-kit/scripts/bash/check-prerequisites.sh --json
-  ps: spec-kit/scripts/powershell/check-prerequisites.ps1 -Json
 ---
 
 ## Checklist Purpose: "Unit Tests for English"
@@ -97,7 +94,7 @@ You **MUST** consider the user input before proceeding (if not empty).
      - Format: `[domain].md`
      - If file exists, append to existing file
    - Number items sequentially starting from CHK001
-   - Each `/ck.spec.checklist` run creates a NEW file (never overwrites existing checklists)
+   - Each `/ck-spec-checklist` run creates a NEW file (never overwrites existing checklists)
 
    **CORE PRINCIPLE - Test the Requirements, Not the Implementation**:
    Every checklist item MUST evaluate the REQUIREMENTS THEMSELVES for:
@@ -215,7 +212,7 @@ You **MUST** consider the user input before proceeding (if not empty).
    - Actor/timing
    - Any explicit user-specified must-have items incorporated
 
-**Important**: Each `/ck.spec.checklist` command invocation creates a checklist file using short, descriptive names unless file already exists. This allows:
+**Important**: Each `/ck-spec-checklist` command invocation creates a checklist file using short, descriptive names unless file already exists. This allows:
 
 - Multiple checklists of different types (e.g., `ux.md`, `test.md`, `security.md`)
 - Simple, memorable filenames that indicate checklist purpose
@@ -303,8 +300,9 @@ Sample items:
 
 | Command | Description | When to Use |
 |---------|-------------|-------------|
-| `/ck.spec.clarify` | Clarify requirements | Checklist revealed gaps in spec |
-| `/ck.spec.plan` | Generate implementation plan | Checklist passed, spec is solid |
-| `/ck.spec.implement` | Start implementation | Plan exists, checklist validated |
+| `/ck-spec-clarify` | Clarify requirements | Checklist revealed gaps in spec |
+| `/ck-spec-plan` | Generate implementation plan | Checklist passed, spec is solid |
+| `/ck-spec-implement` | Start implementation | Plan exists, checklist validated |
+| `/ck-test` | Run tests to validate | Checklist passed, verify with tests |
 
-**Usage:** Run `/ck.spec.checklist [domain]` for focused validation (e.g., security, ux, api)
+**Usage:** Run `/ck-spec-checklist [domain]` for focused validation (e.g., security, ux, api)

package/prompts/ck-spec-clarify.prompt.md

@@ -1,13 +1,6 @@
 ---
 agent: 'agent'
 description: 'Identify underspecified areas and ask targeted clarification questions'
-handoffs:
-  - label: Build Technical Plan
-    agent: ck.spec.plan
-    prompt: Create a plan for the spec. I am building with...
-scripts:
-  sh: spec-kit/scripts/bash/check-prerequisites.sh --json --paths-only
-  ps: spec-kit/scripts/powershell/check-prerequisites.ps1 -Json -PathsOnly
 ---
 
 ## User Input
@@ -22,7 +15,7 @@ You **MUST** consider the user input before proceeding (if not empty).
 
 Goal: Detect and reduce ambiguity or missing decision points in the active feature specification and record the clarifications directly in the spec file.
 
-Note: This clarification workflow is expected to run (and be completed) BEFORE invoking `/ck.spec.plan`. If the user explicitly states they are skipping clarification (e.g., exploratory spike), you may proceed, but must warn that downstream rework risk increases.
+Note: This clarification workflow is expected to run (and be completed) BEFORE invoking `/ck-spec-plan`. If the user explicitly states they are skipping clarification (e.g., exploratory spike), you may proceed, but must warn that downstream rework risk increases.
 
 Execution steps:
 
@@ -30,7 +23,7 @@ Execution steps:
    - `FEATURE_DIR`
    - `FEATURE_SPEC`
    - (Optionally capture `IMPL_PLAN`, `TASKS` for future chained flows.)
-   - If JSON parsing fails, abort and instruct user to re-run `/ck.spec.specify` or verify feature branch environment.
+   - If JSON parsing fails, abort and instruct user to re-run `/ck-spec-specify` or verify feature branch environment.
    - For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").
 
 2. Load the current spec file. Perform a structured ambiguity & coverage scan using this taxonomy. For each category, mark status: Clear / Partial / Missing. Produce an internal coverage map used for prioritization (do not output raw map unless no questions will be asked).
@@ -169,13 +162,13 @@ Execution steps:
    - Path to updated spec.
    - Sections touched (list names).
    - Coverage summary table listing each taxonomy category with Status: Resolved (was Partial/Missing and addressed), Deferred (exceeds question quota or better suited for planning), Clear (already sufficient), Outstanding (still Partial/Missing but low impact).
-   - If any Outstanding or Deferred remain, recommend whether to proceed to `/ck.spec.plan` or run `/ck.spec.clarify` again later post-plan.
+   - If any Outstanding or Deferred remain, recommend whether to proceed to `/ck-spec-plan` or run `/ck-spec-clarify` again later post-plan.
    - Suggested next command.
 
 Behavior rules:
 
 - If no meaningful ambiguities found (or all potential questions would be low-impact), respond: "No critical ambiguities detected worth formal clarification." and suggest proceeding.
-- If spec file missing, instruct user to run `/ck.spec.specify` first (do not create a new spec here).
+- If spec file missing, instruct user to run `/ck-spec-specify` first (do not create a new spec here).
 - Never exceed 5 total asked questions (clarification retries for a single question do not count as new questions).
 - Avoid speculative tech stack questions unless the absence blocks functional clarity.
 - Respect user early termination signals ("stop", "done", "proceed").
@@ -190,8 +183,8 @@ Context for prioritization: {ARGS}
 
 | Command | Description | When to Use |
 |---------|-------------|-------------|
-| `/ck.spec.plan` | Generate implementation plan | All clarifications resolved, spec is complete |
-| `/ck.spec.checklist` | Generate validation checklist | Need domain-specific requirements validation |
-| `/ck.spec.specify` | Update/rewrite spec | Major scope changes or new feature |
+| `/ck-spec-plan` | Generate implementation plan | All clarifications resolved, spec is complete |
+| `/ck-spec-checklist` | Generate validation checklist | Need domain-specific requirements validation |
+| `/ck-spec-specify` | Update/rewrite spec | Major scope changes or new feature |
 
-**Workflow:** `/ck.spec.specify` → `/ck.spec.clarify` → `/ck.spec.plan` → `/ck.spec.tasks` → `/ck.spec.implement`
+**Workflow:** `/ck-spec-specify` → `/ck-spec-clarify` → `/ck-spec-plan` → `/ck-spec-tasks` → `/ck-spec-implement`

package/prompts/ck-spec-constitution.prompt.md

@@ -1,12 +1,6 @@
 ---
 agent: 'agent'
 description: 'Create or update the project constitution from principle inputs'
-handoffs:
-  - label: Build Specification
-    agent: ck.spec.specify
-    prompt: >-
-      Implement the feature specification based on the updated constitution. I
-      want to build...
 ---
 
 ## User Input
@@ -47,7 +41,7 @@ Follow this execution flow:
    - Read `spec-kit/templates/plan-template.md` and ensure any "Constitution Check" or rules align with updated principles.
    - Read `spec-kit/templates/spec-template.md` for scope/requirements alignment—update if constitution adds/removes mandatory sections or constraints.
    - Read `spec-kit/templates/tasks-template.md` and ensure task categorization reflects new or removed principle-driven task types (e.g., observability, versioning, testing discipline).
-   - Read each command file in `spec-kit/templates/commands/*.md` (including this one) to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required.
+   - Read each command file in `spec-kit/templates/commands/*.md` (including this one) to verify no outdated references (agent-specific names only) remain when generic guidance is required.
    - Read any runtime guidance docs (e.g., `README.md`, `docs/quickstart.md`, or agent-specific guidance files if present). Update references to principles changed.
 
 5. Produce a Sync Impact Report (prepend as an HTML comment at top of the constitution file after update):
@@ -90,8 +84,9 @@ The template at `spec-kit/memory/constitution.md` should NOT be modified; always
 
 | Command | Description | When to Use |
 |---------|-------------|-------------|
-| `/ck.spec.specify` | Create feature spec | Constitution ready, start defining features |
-| `/ck.spec.plan` | Generate implementation plan | Update existing plan with new principles |
-| `/ck.spec.analyze` | Validate consistency | Check if existing artifacts align with constitution |
+| `/ck-spec-specify` | Create feature spec | Constitution ready, start defining features |
+| `/ck-spec-plan` | Generate implementation plan | Update existing plan with new principles |
+| `/ck-spec-analyze` | Validate consistency | Check if existing artifacts align with constitution |
+| `/ck-brainstorm` | Brainstorm project ideas | Early stage, exploring project direction |
 
-**Usage:** Run `/ck.spec.constitution` at project start to establish non-negotiable principles
+**Usage:** Run `/ck-spec-constitution` at project start to establish non-negotiable principles

package/prompts/ck-spec-implement.prompt.md

@@ -1,9 +1,6 @@
 ---
 agent: 'agent'
 description: 'Execute the implementation plan by processing all tasks in tasks.md'
-scripts:
-  sh: spec-kit/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks
-  ps: spec-kit/scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks
 ---
 
 ## User Input
@@ -98,8 +95,8 @@ You **MUST** consider the user input before proceeding (if not empty).
    **Tool-Specific Patterns**:
    - **Docker**: `node_modules/`, `.git/`, `Dockerfile*`, `.dockerignore`, `*.log*`, `.env*`, `coverage/`
    - **ESLint**: `node_modules/`, `dist/`, `build/`, `coverage/`, `*.min.js`
-   - **Prettier**: `node_modules/`, `dist/`, `build/`, `coverage/`, `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`
-   - **Terraform**: `.terraform/`, `*.tfstate*`, `*.tfvars`, `.terraform.lock.hcl`
+   - **Prettier**: `node_modules/`, `dist/`, `build/`, `coverage/`, `package-lock.json`, `yarn.lock`, `pnpm-lock-yaml`
+   - **Terraform**: `.terraform/`, `*.tfstate*`, `*.tfvars`, `.terraform.lock-hcl`
    - **Kubernetes/k8s**: `*.secret.yaml`, `secrets/`, `.kube/`, `kubeconfig*`, `*.key`, `*.crt`
 
 5. Parse task structure and extract:
@@ -144,7 +141,7 @@ You **MUST** consider the user input before proceeding (if not empty).
 
 **Notes**:
 - This command supports both single-file (tasks.md only) and hybrid structure (tasks.md + tasks/phase-*.md)
-- If tasks are incomplete or missing, suggest running `/ck.spec.tasks` first to regenerate the task list
+- If tasks are incomplete or missing, suggest running `/ck-spec-tasks` first to regenerate the task list
 - Hybrid structure enables parallel work: multiple agents can work on different phase files simultaneously
 
 ---
@@ -153,8 +150,8 @@ You **MUST** consider the user input before proceeding (if not empty).
 
 | Command | Description | When to Use |
 |---------|-------------|-------------|
-| `/ck.test` | Run tests and analyze | Validate implementation against requirements |
-| `/ck.review` | Code review | Implementation complete, ready for QA |
-| `/ck.fix` | Fix issues | Tests failed or bugs discovered |
+| `/ck-test` | Run tests and analyze | Validate implementation against requirements |
+| `/ck-review` | Code review | Implementation complete, ready for QA |
+| `/ck-fix` | Fix issues | Tests failed or bugs discovered |
 
-**Workflow:** `/ck.spec.implement` → `/ck.test` → `/ck.review` → `/ck.git`
+**Workflow:** `/ck-spec-implement` → `/ck-test` → `/ck-review` → `/ck-git`

package/prompts/ck-spec-plan.prompt.md

@@ -1,20 +1,6 @@
 ---
 agent: 'agent'
 description: 'Execute implementation planning workflow to generate design artifacts'
-handoffs:
-  - label: Create Tasks
-    agent: ck.spec.tasks
-    prompt: Break the plan into tasks
-    send: true
-  - label: Create Checklist
-    agent: ck.spec.checklist
-    prompt: Create a checklist for the following domain...
-scripts:
-  sh: spec-kit/scripts/bash/setup-plan.sh --json
-  ps: spec-kit/scripts/powershell/setup-plan.ps1 -Json
-agent_scripts:
-  sh: spec-kit/scripts/bash/update-agent-context.sh __AGENT__
-  ps: spec-kit/scripts/powershell/update-agent-context.ps1 -AgentType __AGENT__
 ---
 
 ## User Input
@@ -101,8 +87,9 @@ You **MUST** consider the user input before proceeding (if not empty).
 
 | Command | Description | When to Use |
 |---------|-------------|-------------|
-| `/ck.spec.tasks` | Generate executable tasks | Plan complete with data-model.md, contracts/ ready |
-| `/ck.spec.checklist` | Generate validation checklist | Need domain-specific QA before implementation |
-| `/ck.spec.analyze` | Cross-artifact analysis | After tasks generated, check consistency |
+| `/ck-spec-tasks` | Generate executable tasks | Plan complete with data-model.md, contracts/ ready |
+| `/ck-spec-checklist` | Generate validation checklist | Need domain-specific QA before implementation |
+| `/ck-spec-analyze` | Cross-artifact analysis | After tasks generated, check consistency |
+| `/ck-cook` | Quick flow — implement plan directly | Plan is simple, skip spec-tasks |
 
-**Workflow:** `/ck.spec.specify` → `/ck.spec.clarify` → `/ck.spec.plan` → `/ck.spec.tasks` → `/ck.spec.implement`
+**Workflow:** `/ck-spec-specify` → `/ck-spec-clarify` → `/ck-spec-plan` → `/ck-spec-tasks` → `/ck-spec-implement`

package/prompts/ck-spec-specify.prompt.md

@@ -1,17 +1,6 @@
 ---
 agent: 'agent'
 description: 'Create or update the feature specification from a natural language description'
-handoffs:
-  - label: Build Technical Plan
-    agent: ck.spec.plan
-    prompt: Create a plan for the spec. I am building with...
-  - label: Clarify Spec Requirements
-    agent: ck.spec.clarify
-    prompt: Clarify specification requirements
-    send: true
-scripts:
-  sh: 'spec-kit/scripts/bash/create-new-feature.sh --json "{ARGS}"'
-  ps: 'spec-kit/scripts/powershell/create-new-feature.ps1 -Json "{ARGS}"'
 ---
 
 ## User Input
@@ -24,7 +13,7 @@ You **MUST** consider the user input before proceeding (if not empty).
 
 ## Outline
 
-The text the user typed after `/ck.spec.specify` in the triggering message **is** the feature description. Assume you always have it available in this conversation even if `{ARGS}` appears literally below. Do not ask the user to repeat it unless they provided an empty command.
+The text the user typed after `/ck-spec-specify` in the triggering message **is** the feature description. Assume you always have it available in this conversation even if `{ARGS}` appears literally below. Do not ask the user to repeat it unless they provided an empty command.
 
 Given that feature description, do this:
 
@@ -138,7 +127,7 @@ Given that feature description, do this:
       
       ## Notes
       
-      - Items marked incomplete require spec updates before `/ck.spec.clarify` or `/ck.spec.plan`
+      - Items marked incomplete require spec updates before `/ck-spec-clarify` or `/ck-spec-plan`
       ```
 
    b. **Run Validation Check**: Review the spec against each checklist item:
@@ -192,7 +181,7 @@ Given that feature description, do this:
 
    d. **Update Checklist**: After each validation iteration, update the checklist file with current pass/fail status
 
-7. Report completion with branch name, spec file path, checklist results, and readiness for the next phase (`/ck.spec.clarify` or `/ck.spec.plan`).
+7. Report completion with branch name, spec file path, checklist results, and readiness for the next phase (`/ck-spec-clarify` or `/ck-spec-plan`).
 
 **NOTE:** The script creates and checks out the new branch and initializes the spec file before writing.
 
@@ -265,6 +254,8 @@ Success criteria must be:
 
 | Command | Description | When to Use |
 |---------|-------------|-------------|
-| `/ck.spec.clarify` | Ask clarification questions | Spec has [NEEDS CLARIFICATION] markers or vague requirements |
-| `/ck.spec.plan` | Generate implementation plan | Spec is complete and ready for technical planning |
-| `/ck.spec.constitution` | Create project principles | Need to establish non-negotiable rules before planning |
+| `/ck-spec-clarify` | Ask clarification questions | Spec has [NEEDS CLARIFICATION] markers or vague requirements |
+| `/ck-spec-plan` | Generate implementation plan | Spec is complete and ready for technical planning |
+| `/ck-spec-constitution` | Create project principles | Need to establish non-negotiable rules before planning |
+| `/ck-plan` | Create implementation plan | Spec is finalized, ready to plan and implement |
+| `/ck-brainstorm` | Brainstorm ideas first | Not sure what to build yet |

package/prompts/ck-spec-tasks.prompt.md

@@ -1,18 +1,6 @@
 ---
 agent: 'agent'
 description: 'Generate actionable, dependency-ordered tasks.md from design artifacts'
-handoffs:
-  - label: Analyze For Consistency
-    agent: ck.spec.analyze
-    prompt: Run a project analysis for consistency
-    send: true
-  - label: Implement Project
-    agent: ck.spec.implement
-    prompt: Start the implementation in phases
-    send: true
-scripts:
-  sh: spec-kit/scripts/bash/check-prerequisites.sh --json
-  ps: spec-kit/scripts/powershell/check-prerequisites.ps1 -Json
 ---
 
 ## User Input
@@ -186,8 +174,8 @@ Every task MUST strictly follow this format:
 
 | Command | Description | When to Use |
 |---------|-------------|-------------|
-| `/ck.spec.analyze` | Cross-artifact consistency check | Before implementation, validate spec/plan/tasks alignment |
-| `/ck.spec.implement` | Execute implementation | All tasks validated, ready to code |
-| `/ck.spec.taskstoissues` | Create GitHub issues | Track tasks in GitHub project board |
+| `/ck-spec-analyze` | Cross-artifact consistency check | Before implementation, validate spec/plan/tasks alignment |
+| `/ck-spec-implement` | Execute implementation | All tasks validated, ready to code |
+| `/ck-cook` | Quick flow — implement without full spec | Simple tasks that don't need spec-implement |
 
-**Workflow:** `/ck.spec.specify` → `/ck.spec.clarify` → `/ck.spec.plan` → `/ck.spec.tasks` → `/ck.spec.implement`
+**Workflow:** `/ck-spec-specify` → `/ck-spec-clarify` → `/ck-spec-plan` → `/ck-spec-tasks` → `/ck-spec-implement`

package/prompts/ck-test.prompt.md

@@ -4,7 +4,7 @@ description: 'Run tests locally and analyze the summary report'
 tools: ['execute/runInTerminal', 'execute/getTerminalOutput', 'execute/runTests', 'execute/testFailure', 'read/problems']
 ---
 
-Use the `tester` subagent to run tests locally and analyze the summary report.
+Use the `tester` agent to run tests locally and analyze the summary report.
 
 **IMPORTANT**: **Do not** start implementing.
 **IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
@@ -15,5 +15,7 @@ Use the `tester` subagent to run tests locally and analyze the summary report.
 
 | Command | Description |
 |---------|-------------|
-| `/ck.fix` | Analyze and fix issues |
-| `/ck.review` | Scan and analyze codebase |
+| `/ck-fix` | Analyze and fix issues |
+| `/ck-review` | Scan and analyze codebase |
+| `/ck-git` | Commit changes |
+| `/ck-spec-checklist` | Validate against spec requirements |

package/prompts/ck-watzup.prompt.md

@@ -15,5 +15,7 @@ Analyze the overall impact and quality of the changes.
 
 | Command | Description |
 |---------|-------------|
-| `/ck.brainstorm` | Explore ideas |
-| `/ck.plan` | Create plan |
+| `/ck-brainstorm` | Explore ideas |
+| `/ck-plan` | Create plan |
+| `/ck-cook` | Implement feature |
+| `/ck-spec-specify` | Write detailed feature spec |

package/skills/INSTALLATION.md

@@ -1,6 +1,6 @@
 # Skills Installation Guide
 
-This guide explains how to install dependencies for Claude Code skills.
+This guide explains how to install dependencies for skills.
 
 ## Overview
 
@@ -203,7 +203,7 @@ Skills respect environment variable loading priority:
 1. **process.env** (highest priority - runtime environment)
 2. **`$HOME/.copilot/skills/{skill-name}/.env`** (skill-specific config)
 3. **`$HOME/.copilot/skills/.env`** (shared skills config)
-4. **`$HOME/.copilot/.env`** (global Claude config)
+4. **`$HOME/.copilot/.env`** (global config)
 
 Example `.env` files are provided where needed (e.g., `devops/.env.example`).
 
@@ -308,4 +308,4 @@ If dependencies fail to install or scripts don't work:
 2. Verify system tools are installed and in PATH
 3. Check environment variables are set correctly
 4. Review skill's `SKILL.md` for additional setup instructions
-5. Open an issue: https://github.com/anthropics/claude-code/issues
+5. Open an issue on the project repository