cokit-cli 1.2.7 → 1.4.0

package/docs/system-architecture.md

@@ -3,11 +3,11 @@
 ## Overview
 ```
 ┌─────────────────────────────────────────────────────────────┐
-│                        SOURCES                               │
+│                        SOURCE                                │
 ├─────────────────────────────────────────────────────────────┤
-│  ClaudeKit (~/.claude/)      SpecKit (upstream/speckit/)    │
-│  ├── commands/               ├── templates/commands/         │
-│  ├── skills/                 └── (git subtree)               │
+│  Upstream Source                                             │
+│  ├── commands/                                               │
+│  ├── skills/                                                 │
 │  └── (local install)                                         │
 └─────────────────────────────────────────────────────────────┘
                               │
@@ -17,8 +17,7 @@
 ├─────────────────────────────────────────────────────────────┤
 │  eng/sync.mjs                                                │
 │  ├── Load resource-origins.yml (mappings + ignore list)     │
-│  ├── transform-claudekit.mjs → ck-* namespace               │
-│  ├── transform-speckit.mjs → ck-spec-* namespace            │
+│  ├── transform-upstream.mjs → ck-* namespace                │
 │  ├── patch-navigation.mjs → Add "Suggested Next Steps"      │
 │  └── Write to prompts/                                       │
 └─────────────────────────────────────────────────────────────┘
@@ -28,7 +27,7 @@
 │                       OUTPUT                                 │
 ├─────────────────────────────────────────────────────────────┤
 │  prompts/                                                    │
-│  ├── ck-*.prompt.md (27 total commands)                     │
+│  ├── ck-*.prompt.md (17 commands)                           │
 │  └── agents/, skills/, instructions/, collections/         │
 └─────────────────────────────────────────────────────────────┘
                               │
@@ -45,12 +44,11 @@
 
 ### Sync Pipeline
 ```
-1. git subtree pull (SpecKit)
-2. Read ~/.claude/commands/ (ClaudeKit)
-3. Transform: rename, replace $ARGUMENTS, remove model field
-4. Patch: inject navigation footer
-5. Write: prompts/*.prompt.md
-6. Update: resource-origins.yml (timestamps)
+1. Read upstream commands source
+2. Transform: rename, replace $ARGUMENTS, remove model field
+3. Patch: inject navigation footer
+4. Write: prompts/*.prompt.md
+5. Update: resource-origins.yml (timestamps)
 ```
 
 ### CLI Install
@@ -66,8 +64,7 @@
 | Component | File | Purpose |
 |-----------|------|---------|
 | Orchestrator | eng/sync.mjs | Runs full sync pipeline |
-| ClaudeKit Transform | eng/transform-claudekit.mjs | Transform ~/.claude/ commands |
-| SpecKit Transform | eng/transform-speckit.mjs | Transform upstream/speckit/ |
+| Upstream Transform | eng/transform-upstream.mjs | Transform upstream commands |
 | Navigation Patch | eng/patch-navigation.mjs | Add cross-command navigation |
 | Config | eng/resource-origins.yml | Mappings, ignore list, navigation |
 
@@ -75,5 +72,4 @@
 
 | Prefix | Source | Example |
 |--------|--------|---------|
-| `ck-*` | ClaudeKit | ck-plan, ck-fix, ck-test |
-| `ck-spec-*` | SpecKit | ck-spec-specify, ck-spec-plan |
+| `ck-*` | Upstream | ck-plan, ck-fix, ck-test |

package/docs/upstream-porting-rules.md

@@ -0,0 +1,182 @@
+# Upstream → CoKit Porting Rules
+
+**Purpose:** Definitive reference for porting upstream content to CoKit (GitHub Copilot).
+**Audience:** AI agents and developers performing sync/port operations.
+**Last Updated:** 2026-02-25
+
+---
+
+## 0. Porting Workflow
+
+**IMPORTANT:** Always follow this order when porting from upstream.
+
+### Step 1: Inventory CoKit
+Map what CoKit already has — prompts, agents, skills, instructions. This is the source of truth.
+
+### Step 2: Diff against upstream
+Compare upstream commands/agents/skills with CoKit inventory. Identify:
+- **Updates** — existing CoKit files that need content sync
+- **New variants** — upstream has a new sub-command (e.g., `/plan:red-team`) → create as `/ck-plan-red-team` variant
+- **New top-level** — entirely new prompt/agent/skill → create in CoKit
+
+### Step 3: Verify Copilot compatibility
+Before porting, **websearch** to check if Copilot now supports features that were previously unavailable. Copilot evolves fast — what didn't work last month may work now.
+
+Key things to re-check periodically:
+- Subagent spawning & orchestration (`code.visualstudio.com/docs/copilot/agents/subagents`)
+- Agent-to-agent communication (currently NOT supported — may change)
+- Persistent memory API (currently NOT supported — may change)
+- Plan mode / approval flows (currently NOT supported — may change)
+- File ownership / task management APIs (currently NOT supported — may change)
+- New frontmatter fields (check `code.visualstudio.com/docs/copilot/customization/custom-agents`)
+
+### Step 4: Apply conversion rules (sections below)
+
+### Step 5: Validate with grep patterns (section 9)
+
+### Step 6: Update version & docs (section 8)
+
+---
+
+## 1. Syntax Conversions
+
+| Upstream | CoKit | Notes |
+|----------|-------|-------|
+| `$ARGUMENTS` | `${input}` | Copilot prompt variable |
+| `@agent-name` | `` `agent-name` agent `` | No `@` prefix in Copilot |
+| `.claude/` paths | `$HOME/.copilot/` | Global config directory |
+| `~/.claude/` | `$HOME/.copilot/` | Same as above |
+| `subagent` | `agent` | Copilot terminology |
+| Unprefixed skill/agent name | `ck-` prefixed | Namespace consistency |
+
+## 2. Command References
+
+| Upstream | CoKit | Notes |
+|-----------|-------|-------|
+| `/fix:types` | `/ck-fix-types` | Colon → hyphen |
+| `/fix:tests` | `/ck-fix-test` | Colon → hyphen |
+| `/scout:ext` | `/ck-scout ext` | Colon → space (argument) |
+| `/plan --hard` | `/ck-plan-hard` | Flag → separate command |
+| `/plan --fast` | `/ck-plan-fast` | Flag → separate command |
+| `SlashCommand(/scout)` | `/ck-scout` | Remove `SlashCommand()` wrapper |
+
+**New variant?** If upstream adds a new sub-command (e.g., `/plan:red-team`), create it as a variant prompt file in CoKit (`ck-plan-red-team.prompt.md`). Variants don't count toward prompt total.
+
+## 3. Tool/API Conversions
+
+| Upstream | CoKit | Notes |
+|----------|-------|-------|
+| `AskUserQuestion` | Natural conversation | Just ask the user directly |
+| `Task(subagent_type="X")` | Natural language delegation | Describe what agent should do |
+| `TaskCreate/TaskUpdate/TaskList` | Checklist/todo tracking | No task management API |
+| `SendMessage` | Direct communication | No message passing API |
+| `EnterPlanMode/ExitPlanMode` | N/A | Copilot doesn't have plan mode |
+
+**NOTE:** Websearch these before each port session — Copilot may add equivalents.
+
+## 4. Frontmatter Fields
+
+### Remove (unsupported by Copilot)
+- `name:` — Copilot infers from filename
+- `model:` — Copilot handles model selection
+- `memory:` — No persistent memory API
+- `version:` — Not a valid field
+- `license:` — Not a valid field
+- `scripts:` — Not valid in prompts
+- `handoffs:` — Not valid in prompts
+- `agent_scripts:` — Not valid
+
+### Keep/Modify
+- `description:` — Keep, but single line only (no examples)
+- `agent: 'agent'` — Required for agent-mode prompts
+- `tools:` — Keep valid tool references
+- `argument-hint:` — Keep for user guidance
+
+## 5. Agent-Specific Rules
+
+### CoKit agents (12)
+`ck-brainstormer`, `ck-code-reviewer`, `ck-code-simplifier`, `ck-debugger`, `ck-docs-manager`, `ck-fullstack-developer`, `ck-git-manager`, `ck-planner`, `ck-researcher`, `ck-scout`, `ck-tester`, `ck-ui-ux-designer`
+
+### Upstream agents that DON'T exist in CoKit
+| Upstream Agent | CoKit Replacement |
+|-----------------|-------------------|
+| `ck-project-manager` | Direct action (describe what to do) |
+| `journal-writer` | Remove or convert to manual journaling |
+| `mcp-manager` | Remove or use `mcp-management` skill |
+
+### Agent file conventions
+- Remove `## Team Mode` sections — Copilot subagents don't support task claiming, peer communication, or file ownership
+- Add skills activation directive referencing `$HOME/.copilot/skills/*`
+
+## 6. External Tool Qualifiers
+
+If a skill/tool exists in CoKit's `skills/*/SKILL.md` → it's available, no qualifier needed.
+If NOT → add `(if available)`:
+
+| Tool | Action | Reason |
+|------|--------|--------|
+| `repomix` | Add "(if available)" | External npm package, needs CLI install |
+| `ai-multimodal` | Add "(if available)" | External Gemini skill, not in CoKit |
+| `ui-ux-pro-max` | Add "(if available)" | Not in CoKit skills |
+| `media-processing` | Add "(if available)" | Not in CoKit skills |
+| `chrome-devtools` | Use `agent-browser` | Renamed in CoKit |
+| `document-skills` | Use `docs-seeker` | Different name in CoKit |
+
+**Single flag:** Always use `(if available)` — never `(if installed)`.
+
+**Before porting:** Check if any missing skill has been added to CoKit since last port. If so, remove the qualifier.
+
+## 7. Prompt Classification
+
+- **Prompts** = top-level commands counted in "25 prompts" (e.g., `/ck-plan`, `/ck-fix`, `/ck-cook`)
+- **Variant commands** = sub-routes, NOT counted (e.g., `/ck-plan-fast`, `/ck-plan-hard`, `/ck-plan-validate`, `/ck-plan-red-team`)
+
+New variant → update flowchart + Deep Dive in `index.html`, do NOT bump prompt count.
+
+## 8. Version & Docs Update Checklist
+
+### Always update
+- [ ] `package.json` + `package-lock.json` (`npm install --package-lock-only`)
+- [ ] `CHANGELOG.md` — new entry
+- [ ] `index.html` — hero badge + footer version
+- [ ] `README.md` — "What's New" section
+- [ ] `docs/project-roadmap.md` — version + last updated
+
+### Sync if outdated (check version string)
+- [ ] `docs/README.md`
+- [ ] `docs/codebase-summary.md`
+- [ ] `docs/cokit-comprehensive-mapping-guide.md`
+- [ ] `docs/cokit-team-presentation.md`
+- [ ] `docs/cokit-sync-and-maintenance-guide.md`
+- [ ] `docs/project-overview-pdr.md`
+
+### If new commands added
+- [ ] Flowchart nodes/edges in `index.html`
+- [ ] Deep Dive section in `index.html`
+- [ ] Prompts table in `index.html` (if variant of existing command)
+
+## 9. Validation Grep Patterns
+
+After porting, run these — must return 0 matches (except historical/changelog):
+
+```bash
+grep -r "@\w+-\w+" agents/ skills/ prompts/          # @agent-name syntax
+grep -r "project-manager" agents/ skills/ prompts/    # Non-existent agent
+grep -r "subagent" agents/                            # Wrong terminology
+grep -r "\.claude/" agents/ skills/ prompts/          # Wrong path
+grep -r "AskUserQuestion\|SlashCommand" agents/ skills/ prompts/  # Upstream-only APIs
+grep -r "chrome-devtools" agents/                     # Renamed tool
+grep -r "\$ARGUMENTS" agents/ prompts/                # Wrong variable
+grep -r "^name:\|^model:\|^memory:" agents/ prompts/  # Invalid frontmatter
+```
+
+## 10. Common Mistakes
+
+1. **`@agent-name`** → Use `` `agent-name` agent `` (no `@` prefix)
+2. **`ck-project-manager` agent** → Doesn't exist, replace with direct instructions
+3. **Team Mode sections** → Don't port, Copilot subagents are isolated
+4. **Missing "(if available)"** → External tools need `(if available)` qualifier. Use this single flag only — never "(if installed)"
+5. **Counting variants as prompts** → Variants don't bump prompt count
+6. **`SlashCommand()` wrappers** → Convert to plain `/ck-*`
+7. **`document-skills`** → Use `docs-seeker`
+8. **`chrome-devtools`** → Use `agent-browser`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cokit-cli",
-  "version": "1.2.7",
+  "version": "1.4.0",
   "description": "Make GitHub Copilot smarter in 30 seconds",
   "main": "src/index.js",
   "bin": {
@@ -30,8 +30,7 @@
     "test": "node --test",
     "lint": "echo 'No linter configured'",
     "build": "echo 'Build complete'",
-    "sync": "npm run sync:pull && npm run sync:transform",
-    "sync:pull": "git subtree pull --prefix=upstream/speckit speckit main --squash",
+    "sync": "node eng/sync.mjs",
     "sync:transform": "node eng/sync.mjs",
     "sync:dry-run": "node eng/sync.mjs --dry-run",
     "convert:agents": "node eng/convert-agents.mjs",
@@ -39,7 +38,7 @@
     "convert:skills": "node eng/convert-skills.mjs",
     "convert:all": "npm run convert:agents && npm run convert:commands && npm run convert:skills && npm run rewrite && npm run clean",
     "rewrite": "node eng/rewrite-single-agent.mjs",
-    "clean": "node eng/clean-claude-references.mjs"
+    "clean": "node eng/clean-references.mjs"
   },
   "keywords": [
     "copilot",

package/prompts/ck-ask.prompt.md

@@ -64,4 +64,3 @@ This command focuses on architectural consultation and strategic guidance. Do no
 |---------|-------------|
 | `/ck-brainstorm` | Explore ideas |
 | `/ck-plan` | Create plan |
-| `/ck-spec-specify` | Write detailed feature spec |

package/prompts/ck-bootstrap.prompt.md

@@ -40,7 +40,7 @@ argument-hint: 'Describe your project requirements'
 
 Follow strictly these following steps:
 
-**First thing first:** check if Git has been initialized, if not, ask the user if they want to initialize it, if yes, use `git-manager` agent to initialize it.
+**First thing first:** check if Git has been initialized, if not, ask the user if they want to initialize it, if yes, use `ck-git-manager` agent to initialize it.
 
 ### Fullfill the request
 
@@ -48,23 +48,21 @@ Follow strictly these following steps:
 * Ask 1 question at a time, wait for the user to answer before moving to the next question.
 * If you don't have any questions, start the next step.
 
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
-
 ### Research
 
-* Use multiple `researcher` agents in parallel to explore the user's request, idea validation, challenges, and find the best possible solutions.
+* Use multiple `ck-researcher` agents in parallel to explore the user's request, idea validation, challenges, and find the best possible solutions.
 * Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
 
 ### Tech Stack
 
 1. Ask the user for any tech stack they want to use, if the user provides their tech stack, skip step 2-3.
-2. Use `planner` agent and multiple `researcher` agents in parallel to find a best fit tech stack for this project, keeping research reports within the ≤150 lines limit.
+2. Use `ck-planner` agent and multiple `ck-researcher` agents in parallel to find a best fit tech stack for this project, keeping research reports within the ≤150 lines limit.
 3. Ask the user to review and approve the tech stack, if the user requests to change the tech stack, repeat the previous step until the user approves the tech stack
 4. Write the tech stack down in `./docs` directory
 
 ### Planning
 
-* Use `planner` agent to create a detailed implementation plan following the progressive disclosure structure:
+* Use `ck-planner` agent to create a detailed implementation 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).
@@ -76,11 +74,11 @@ Follow strictly these following steps:
 ### Wireframe & Design
 
 * Ask the user if they want to create wireframes and design guidelines, if yes, continue to the next step, if no, skip to **"Implementation"** phase.
-* Use `ui-ux-designer` agent and multiple `researcher` agents in parallel to create a design plan that follows the same directory/phase structure described above, keeping related research reports within the ≤150 lines limit.
+* Use `ck-ui-ux-designer` agent and multiple `ck-researcher` agents in parallel to create a design plan that follows the same directory/phase structure described above, keeping related research reports within the ≤150 lines limit.
    - **Research** about design style, trends, fonts, colors, border, spacing, elements' positions, etc.
    - Describe details of the assets in the design so they can be generated later on.
    - **IMPORTANT:** Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use **Inter** or **Poppins** fonts.
-* Then use `ui-ux-designer` agent to create the design guidelines at `./docs/design-guidelines.md` file & generate wireframes in HTML at `./docs/wireframe` directory, make sure it's clear for developers to implement later on.
+* Then use `ck-ui-ux-designer` agent to create the design guidelines at `./docs/design-guidelines.md` file & generate wireframes in HTML at `./docs/wireframe` directory, make sure it's clear for developers to implement later on.
 * Use `agent-browser` skill to take a screenshot of the wireframes and save it at `./docs/wireframes/` directory.
 * Ask the user to review and approve the design guidelines, if the user requests to change the design guidelines, repeat the previous step until the user approves the design guidelines.
 
@@ -90,26 +88,26 @@ Follow strictly these following steps:
 ### Implementation
 
 * Use `general agent (main agent)` to implement the plan step by step, follow the implementation plan in `./plans` directory.
-* Use `ui-ux-designer` agent to implement the frontend part follow the design guidelines at `./docs/design-guidelines.md` file.
+* Use `ck-ui-ux-designer` agent to implement the frontend part follow the design guidelines at `./docs/design-guidelines.md` file.
   * Generate and verify visual assets as needed.
 * Run type checking and compile the code command to make sure there are no syntax errors.
 
 ### Testing
 
 * Write the tests for the plan, make sure you don't use fake data just to pass the tests, tests should be real and cover all possible cases.
-* Use `tester` agent to run the tests, make sure it works, then report back to main agent.
-* If there are issues or failed tests, use `debugger` agent to find the root cause of the issues, then ask main agent to fix all of them and 
+* Use `ck-tester` agent to run the tests, make sure it works, then report back to main agent.
+* If there are issues or failed tests, use `ck-debugger` agent to find the root cause of the issues, then ask main agent to fix all of them and 
 * Repeat the process until all tests pass or no more issues are reported. Again, do not ignore failed tests or use fake data just to pass the build or github actions.
 
 ### Code Review
 
-* After finishing, delegate to `code-reviewer` agent to review code. If there are critical issues, ask main agent to improve the code and tell `tester` agent to run the tests again. Repeat the process until all tests pass.
+* After finishing, delegate to `ck-code-reviewer` agent to review code. If there are critical issues, ask main agent to improve the code and tell `ck-tester` agent to run the tests again. Repeat the 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.
 
 ### Documentation
 
-* If user approves the changes, use `docs-manager` agent to update the docs if needed.
+* If user approves the changes, use `ck-docs-manager` agent to update the docs if needed.
   * Create/update `./docs/README.md` file (keep it concise, under 300 lines).
   * Create/update `./docs/codebase-summary.md` file.
   * Create/update `./docs/project-overview.-pdr.md` (Product Development Requirements) file.
@@ -126,7 +124,7 @@ Follow strictly these following 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` agent to commit and push to git repository.
+* Ask the user if they want to commit and push to git repository, if yes, use `ck-git-manager` agent to commit and push to git repository.
 - **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
 - **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
 
@@ -138,4 +136,3 @@ Follow strictly these following steps:
 |---------|-------------|
 | `/ck-brainstorm` | Explore ideas |
 | `/ck-plan` | Create plan |
-| `/ck-spec-specify` | Write detailed feature spec |

package/prompts/ck-brainstorm.prompt.md

@@ -84,4 +84,3 @@ When brainstorming concludes with agreement, create a detailed markdown summary
 |---------|-------------|
 | `/ck-plan` | Create implementation plan |
 | `/ck-ask` | Answer technical questions |
-| `/ck-spec-specify` | Write detailed feature spec |

package/prompts/ck-cook.prompt.md

@@ -62,15 +62,15 @@ Human review required at these checkpoints (skipped with `--auto`):
 
 | Phase | Agent |
 |-------|-------|
-| Research | `researcher` agent (parallel, optional in fast) |
-| Scout | `scout` agent |
-| Plan | `planner` agent |
-| UI Work | `ui-ux-designer` agent |
-| Implement | `fullstack-developer` agent (parallel mode) |
-| Simplify | `code-simplifier` agent (post-implement) |
-| Testing | `tester`, `debugger` agents |
-| Review | `code-reviewer` agent |
-| Finalize | `docs-manager`, `git-manager` agents |
+| Research | `ck-researcher` agent (parallel, optional in fast) |
+| Scout | `ck-scout` agent |
+| Plan | `ck-planner` agent |
+| UI Work | `ck-ui-ux-designer` agent |
+| Implement | `ck-fullstack-developer` agent (parallel mode) |
+| Simplify | `ck-code-simplifier` agent (post-implement) |
+| Testing | `ck-tester`, `ck-debugger` agents |
+| Review | `ck-code-reviewer` agent |
+| Finalize | `ck-docs-manager`, `ck-git-manager` agents |
 
 ## Process
 
@@ -78,8 +78,8 @@ Human review required at these checkpoints (skipped with `--auto`):
 2. **Scout**: Use `/ck-scout` to discover relevant files
 3. **Research** (if applicable): Gather technical context
 4. **Plan**: Create or load implementation plan
-5. **Implement**: Execute plan phases (use `fullstack-developer` agent in parallel mode)
-6. **Simplify**: `code-simplifier` agent refines implemented code for clarity
+5. **Implement**: Execute plan phases (use `ck-fullstack-developer` agent in parallel mode)
+6. **Simplify**: `ck-code-simplifier` agent refines implemented code for clarity
 7. **Test**: Run tests and validate
 8. **Review**: Code review with quality gates
 9. **Finalize**: Update docs, commit changes
@@ -93,4 +93,3 @@ Human review required at these checkpoints (skipped with `--auto`):
 | `/ck-test` | Run tests |
 | `/ck-review` | Code review |
 | `/ck-git` | Commit changes |
-| `/ck-spec-implement` | Spec-driven implementation instead |

package/prompts/ck-debug.prompt.md

@@ -112,4 +112,3 @@ Stop and follow process if thinking:
 | `/ck-test` | Run tests to verify |
 | `/ck-fix` | Apply fix |
 | `/ck-git` | Commit fix |
-| `/ck-spec-analyze` | Analyze spec consistency |

package/prompts/ck-deploy.prompt.md

@@ -0,0 +1,22 @@
+---
+agent: 'agent'
+description: 'Deploy to any platform with auto-detection'
+argument-hint: '[platform] [environment]'
+---
+
+## Context
+Deploy target:
+<target>${input}</target>
+
+Auto-detects deployment target from config files. Supports Vercel, Netlify, Cloudflare, Railway, Fly.io, Render, Docker, AWS, GCP, and more.
+
+**IMPORTANT**: Verify deployment target before executing.
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck-test` | Run tests before deploy |
+| `/ck-fix` | Fix deployment issues |

package/prompts/ck-docs.prompt.md

@@ -99,4 +99,3 @@ Search and retrieve up-to-date documentation for libraries, frameworks, and pack
 | `/ck-ask` | Ask technical questions |
 | `/ck-plan` | Create implementation plan |
 | `/ck-cook` | Implement feature |
-| `/ck-spec-specify` | Write detailed feature spec |

package/prompts/ck-fix-fast.prompt.md

@@ -28,7 +28,7 @@ If user chooses "Switch to /ck-fix", run `/ck-fix ${input}` immediately — do N
 <issues>${input}</issues>
 
 ## Workflow
-1. Activate `debug` and `problem-solving` skills to find the root cause.
+1. Activate `ck-debug` and `ck-problem-solving` skills to find the root cause.
 2. Implement the fix.
 3. Test the fix and make sure it works.
 4. If there are issues or failed tests, repeat from step 1.

package/prompts/ck-fix-hard.prompt.md

@@ -36,8 +36,8 @@ If user chooses "Switch to /ck-fix", run  immediately — do NOT ask user to re-
 
 ### Fix the issue
 
-Use `sequential-thinking` skill to break complex problems into sequential thought steps.
-Use `problem-solving` skills to tackle the issues.
+Use `ck-sequential-thinking` skill to break complex problems into sequential thought steps.
+Use `ck-problem-solving` skills to tackle the issues.
 
 1. Investigate and find the root cause of the issues.
 2. Research about the root causes on the internet (if needed).

package/prompts/ck-frontend.prompt.md

@@ -0,0 +1,20 @@
+---
+agent: 'agent'
+description: 'Build React/TypeScript frontends with modern patterns'
+argument-hint: '[component or feature]'
+---
+
+## Context
+Frontend task:
+<task>${input}</task>
+
+Build React/TypeScript frontends with modern patterns. Covers components, Suspense, lazy loading, useSuspenseQuery, MUI v7 styling, TanStack Router, and performance optimization.
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck-test` | Test frontend components |
+| `/ck-review` | Review frontend code |

package/prompts/ck-help.prompt.md

@@ -139,4 +139,3 @@ Never replace or summarize the script output. Always show it fully, then enhance
 | `/ck-brainstorm` | Explore ideas |
 | `/ck-plan` | Create plan |
 | `/ck-cook` | Implement feature |
-| `/ck-spec-specify` | Write detailed feature spec |

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

@@ -39,7 +39,7 @@ Check the `## Plan Context` section in the injected context:
 - If "Plan: none" → Create new plan using naming from `## Naming` section.
 
 ## Workflow
-Use `planner` agent to:
+Use `ck-planner` agent to:
 1. If creating new: Create directory using `Plan dir:` from `## Naming` section, then run `node $HOME/.copilot/scripts/set-active-plan.cjs {plan-dir}`
    If reusing: Use the active plan path from Plan Context.
    Make sure you pass the directory path to every agent during the process.
@@ -89,7 +89,6 @@ This reminder is **NON-NEGOTIABLE** - always output it after presenting the plan
 
 ## Important Notes
 - **IMPORTANT:** Ensure token consumption efficiency while maintaining high quality.
-- **IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
 - **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
 - **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
 - **IMPORTANT**: **Do not** start implementing.
@@ -100,8 +99,6 @@ This reminder is **NON-NEGOTIABLE** - always output it after presenting the plan
 
 | Command | Description |
 |---------|-------------|
-| `/ck-spec-tasks` | Break plan into actionable tasks |
 | `/ck-cook` | Implement plan |
 | `/ck-test` | Run tests and analyze results |
 | `/ck-fix` | Analyze and fix issues |
-| `/ck-spec-specify` | Too complex? Switch to spec-driven flow |

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

@@ -44,12 +44,12 @@ Check the `## Plan Context` section in the injected context:
    If reusing: Use the active plan path from Plan Context.
    Make sure you pass the directory path to every agent during the process.
 2. Follow strictly to the "Plan Creation & Organization" rules of `planning` skill.
-3. Use multiple `researcher` agents (max 2 agents) in parallel to research for this task:
+3. Use multiple `ck-researcher` agents (max 2 agents) in parallel to research for this task:
    Each agent research for a different aspect of the task and are allowed to perform max 5 tool calls.
 4. Analyze the codebase by reading `codebase-summary.md`, `code-standards.md`, `system-architecture.md` and `project-overview-pdr.md` file.
    **ONLY PERFORM THIS FOLLOWING STEP IF `codebase-summary.md` is not available or older than 3 days**: Use `/scout <instructions>` slash command to search the codebase for files needed to complete the task.
-5. Main agent gathers all research and scout report filepaths, and pass them to `planner` agent with the prompt to create an implementation plan of this task.
-6. Main agent receives the implementation plan from `planner` agent, and ask user to review the plan
+5. Main agent gathers all research and scout report filepaths, and pass them to `ck-planner` agent with the prompt to create an implementation plan of this task.
+6. Main agent receives the implementation plan from `ck-planner` agent, and ask user to review the plan
 
 ## Post-Plan Validation (Optional)
 
@@ -115,7 +115,6 @@ This reminder is **NON-NEGOTIABLE** when validation is skipped.
 - For each phase, create `{plan-dir}/phase-XX-phase-name-here.md` containing the following sections in order: Context links (reference parent plan, dependencies, docs), Overview (date, description, priority, implementation status, review status), Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps.
 
 ## Important Notes
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
 **IMPORTANT:** Ensure token efficiency while maintaining high quality.
 **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
 **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
@@ -127,8 +126,6 @@ This reminder is **NON-NEGOTIABLE** when validation is skipped.
 
 | Command | Description |
 |---------|-------------|
-| `/ck-spec-tasks` | Break plan into actionable tasks |
 | `/ck-cook` | Implement plan |
 | `/ck-test` | Run tests and analyze results |
 | `/ck-fix` | Analyze and fix issues |
-| `/ck-spec-specify` | Need formal spec? Switch to spec-driven flow |

package/prompts/ck-plan-red-team.prompt.md

@@ -69,7 +69,7 @@ Available lenses (select per Step 2):
 
 ### Step 4: Spawn Reviewers
 
-Launch reviewers simultaneously using `code-reviewer` agents in parallel.
+Launch reviewers simultaneously using `ck-code-reviewer` agents in parallel.
 
 **Each reviewer prompt MUST include:**
 1. This override: `"IGNORE your default code-review instructions. You are reviewing a PLAN DOCUMENT, not code. There is no code to lint, build, or test. Focus exclusively on plan quality."`

package/prompts/ck-plan.prompt.md

@@ -56,7 +56,6 @@ If user chooses validation or mode is `auto`: Execute `/ck-plan-validate {plan-p
 - Hard plans recommend validation
 
 ## Important Notes
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
 **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
 **IMPORTANT:** Ensure token efficiency while maintaining high quality.
 **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
@@ -69,8 +68,6 @@ If user chooses validation or mode is `auto`: Execute `/ck-plan-validate {plan-p
 | Command | Description |
 |---------|-------------|
 | `/ck-plan-validate` | Validate plan with critical questions |
-| `/ck-spec-tasks` | Break plan into actionable tasks |
 | `/ck-cook` | Implement plan |
 | `/ck-test` | Run tests and analyze results |
 | `/ck-fix` | Analyze and fix issues |
-| `/ck-spec-specify` | Need detailed spec first? Start spec-driven flow |

package/prompts/ck-project.prompt.md

@@ -0,0 +1,20 @@
+---
+agent: 'agent'
+description: 'Track progress, manage tasks, generate reports'
+argument-hint: '[status|hydrate|sync|report]'
+---
+
+## Context
+Project management task:
+<task>${input}</task>
+
+Track progress, update plan statuses, generate reports, coordinate docs updates.
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck-plan` | Create implementation plan |
+| `/ck-cook` | Implement features |