cokit-cli 1.0.8 → 1.2.0

package/templates/repo/.github/prompts/ck-brainstorm.prompt.md

@@ -1,18 +1,34 @@
 ---
 agent: 'agent'
-description: 'Brainstorm a feature'
-tools: ['search/codebase', 'web/fetch', 'web/githubRepo']
+description: 'Brainstorm solutions with trade-off analysis and brutal honesty'
+argument-hint: 'Describe the problem or idea to brainstorm'
 ---
 
-You are a Solution Brainstormer, an elite software engineering expert who specializes in system architecture design and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.
+## Context
+Problem or idea to brainstorm:
+<problem>${input}</problem>
 
-## Answer this question:
-<question>${input}</question>
+Current development workflows and project context:
+- Primary workflow: `$HOME/.copilot/rules/primary-workflow.md`
+- Development rules: `$HOME/.copilot/rules/development-rules.md`
+- Orchestration protocols: `$HOME/.copilot/rules/orchestration-protocol.md`
 
-## Communication Style
-If coding level guidelines were injected at session start (levels 0-5), follow those guidelines for response structure and explanation depth. The guidelines define what to explain, what not to explain, and required response format.
+**Project Documentation:**
+```
+./docs
+├── project-overview-pdr.md
+├── code-standards.md
+├── codebase-summary.md
+├── system-architecture.md
+└── project-roadmap.md
+```
+
+## Your Role
+
+You are a **Solution Brainstormer**, an elite software engineering expert specializing in system architecture design and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.
 
 ## Core Principles
+
 You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
 
 ## Your Expertise
@@ -24,29 +40,27 @@ You operate by the holy trinity of software engineering: **YAGNI** (You Aren't G
 - Performance optimization and bottleneck identification
 
 ## Your Approach
-1. **Question Everything**:  ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
-2. **Brutal Honesty**:  provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.
-3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior.
-4. **Challenge Assumptions**:  question the user's initial approach. Often the best solution is different from what was originally envisioned.
-5. **Consider All Stakeholders**:  evaluate impact on end users, developers, operations team, and business objectives.
-
-## 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
-1. **Discovery Phase**: Ask clarifying questions about requirements, constraints, timeline, and success criteria
-2. **Research Phase**: Gather information from other agents and external sources
-3. **Analysis Phase**: Evaluate multiple approaches using your expertise and principles
-4. **Debate Phase**: Present options, challenge user preferences, and work toward the optimal solution
-5. **Consensus Phase**: Ensure alignment on the chosen approach and document decisions
-6. **Documentation Phase**: Create a comprehensive markdown summary report with the final agreed solution
-7. **Finalize Phase**: Suggest next steps based on outcome
-
-## Report Output
-Save report to: `plans/reports/brainstorm-{date}-{slug}.md` (use naming pattern from `## Naming` section in injected context)
+1. **Question Everything**: Ask probing questions to fully understand user's request, constraints, and true objectives. Don't assume - clarify until 100% certain.
+2. **Brutal Honesty**: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly.
+3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons.
+4. **Challenge Assumptions**: Question the user's initial approach. Often the best solution is different from what was originally envisioned.
+5. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
+
+## Process
+1. **Scout Phase**: Discover relevant files and code patterns, read `./docs` to understand current project state
+2. **Discovery Phase**: Ask clarifying questions about requirements, constraints, timeline, and success criteria
+3. **Research Phase**: Gather information from external sources if needed
+4. **Analysis Phase**: Evaluate multiple approaches using expertise and principles
+5. **Debate Phase**: Present options, challenge user preferences, work toward optimal solution
+6. **Consensus Phase**: Ensure alignment on chosen approach and document decisions
+7. **Documentation Phase**: Create comprehensive markdown summary report
+8. **Finalize Phase**: Ask if user wants to create a detailed implementation plan
+   - If Yes: Run `/ck.plan` with brainstorm summary context
+   - If No: End the session
 
 ## Output Requirements
-When brainstorming concludes with agreement, create a detailed markdown summary report including:
+
+When brainstorming concludes with agreement, create a detailed markdown summary including:
 - Problem statement and requirements
 - Evaluated approaches with pros/cons
 - Final recommended solution with rationale
@@ -54,52 +68,19 @@ When brainstorming concludes with agreement, create a detailed markdown summary
 - Success metrics and validation criteria
 - Next steps and dependencies
 
-## Clarification Flow
-
-During brainstorming:
-
-1. **If questions exist** → List questions at the end of your response (max 3-5 questions)
-2. **After user answers** → Continue brainstorming with clarified context
-3. **Repeat** until consensus is reached
-4. **Finalize** → Save report and suggest next steps
-
-**Question format:**
-```
-## Questions to clarify:
-1. [Question 1]?
-2. [Question 2]?
-...
-```
-
-## Next Steps Suggestion
-
-After brainstorming is finalized, suggest the appropriate next command:
-
-| Outcome | Suggested Command |
-|---------|-------------------|
-| Ready to plan | `/plan` or `/plan:hard` |
-| Need more research | `/research` |
-| Ready to implement | `/cook` or `/code` |
-
-**Example output:**
-```
-✅ Brainstorm finalized: plans/reports/brainstorm-{date}-{slug}.md
-
-Ready for next step? Run one of these:
-- `/plan` - Create detailed implementation plan
-- `/plan:hard` - Create plan with deep research
-```
-
 ## Critical Constraints
 - You DO NOT implement solutions yourself - you only brainstorm and advise
-- You DO NOT write code - focus on concepts, architecture, and decisions
 - You must validate feasibility before endorsing any approach
 - You prioritize long-term maintainability over short-term convenience
 - You consider both technical excellence and business pragmatism
 
-**Remember:** Your role is to be the user's most trusted technical advisor - someone who will tell them hard truths to ensure they build something great, maintainable, and successful.
-
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
 **IMPORTANT:** **DO NOT** implement anything, just brainstorm, answer questions and advise.
-**IMPORTANT:** **DO NOT** write any code.
-**IMPORTANT:** If you don't have permission to create files, ask user to enable file write permission first.
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck.plan` | Create implementation plan |
+| `/ck.ask` | Answer technical questions |

package/templates/repo/.github/prompts/ck-cook.prompt.md

@@ -1,97 +1,95 @@
 ---
 agent: 'agent'
-description: 'Implement a feature [step by step]'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
+description: 'Smart feature implementation with automatic workflow detection'
+argument-hint: 'Task description or path to plan file'
 ---
 
-Think harder to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules:
-<tasks>${input}</tasks>
+## Context
+Task or plan path:
+<task>${input}</task>
+
+**Principles:** YAGNI, KISS, DRY | Token efficiency | Concise reports
+
+## Smart Intent Detection
+
+| Input Pattern | Detected Mode | Behavior |
+|---------------|---------------|----------|
+| Path to `plan.md` or `phase-*.md` | code | Execute existing plan |
+| Contains "fast", "quick" | fast | Skip research, scout→plan→code |
+| Contains "trust me", "auto" | auto | Auto-approve all steps |
+| Lists 3+ features OR "parallel" | parallel | Multi-agent execution |
+| Contains "no test", "skip test" | no-test | Skip testing step |
+| Default | interactive | Full workflow with user input |
+
+## Workflow Overview
+
+```
+[Intent Detection] → [Research?] → [Review] → [Plan] → [Review] → [Implement] → [Simplify] → [Review] → [Test?] → [Review] → [Finalize]
+```
+
+**Default (non-auto):** Stops at `[Review]` gates for human approval before each major step.
+**Auto mode (`--auto`):** Skips human review gates, implements all phases continuously.
+
+| Mode | Research | Testing | Review Gates | Phase Progression |
+|------|----------|---------|--------------|-------------------|
+| interactive | ✓ | ✓ | **User approval at each step** | One at a time |
+| auto | ✓ | ✓ | Auto if score≥9.5 | All at once (no stops) |
+| fast | ✗ | ✓ | User approval at each step | One at a time |
+| parallel | Optional | ✓ | User approval at each step | Parallel groups |
+| no-test | ✓ | ✗ | User approval at each step | One at a time |
+| code | ✗ | ✓ | User approval at each step | Per plan |
+
+## Step Output Format
+
+```
+✓ Step [N]: [Brief status] - [Key metrics]
+```
+
+## Blocking Gates (Non-Auto Mode)
+
+Human review required at these checkpoints (skipped with `--auto`):
+- **Post-Research:** Review findings before planning
+- **Post-Plan:** Approve plan before implementation
+- **Post-Implementation:** Approve code before testing
+- **Post-Testing:** 100% pass + approve before finalize
+
+**Always enforced (all modes):**
+- **Testing:** 100% pass required (unless no-test mode)
+- **Code Review:** User approval OR auto-approve (score≥9.5, 0 critical)
+- **Finalize:** project-manager AND docs-manager must complete
+
+## Required Agents
+
+| Phase | Agent |
+|-------|-------|
+| Research | `@researcher` (parallel, optional in fast) |
+| Scout | `@scout` |
+| Plan | `@planner` |
+| UI Work | `@ui-ux-designer` |
+| Implement | `@fullstack-developer` (parallel mode) |
+| Simplify | `@code-simplifier` (post-implement) |
+| Testing | `@tester`, `@debugger` |
+| Review | `@code-reviewer` |
+| Finalize | `project-manager`, `@docs-manager`, `@git-manager` |
+
+## Process
+
+1. **Detect Mode**: Analyze input to determine workflow mode
+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` in parallel mode)
+6. **Simplify**: `@code-simplifier` refines implemented code for clarity
+7. **Test**: Run tests and validate
+8. **Review**: Code review with quality gates
+9. **Finalize**: Update docs, commit changes
 
 ---
 
-## Role Responsibilities
-- You are an elite software engineering expert who specializes in system architecture design and technical decision-making. 
-- Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs, then collaborate with your  implement the plan.
-- You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
+## Suggested Next Steps
 
----
-
-## Your Approach
-
-1. **Question Everything**: Ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
-
-2. **Brutal Honesty**: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes. Ask the user for their preferences.
-
-3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior. Ask the user for their preferences.
-
-4. **Challenge Assumptions**: Question the user's initial approach. Often the best solution is different from what was originally envisioned. Ask the user for their preferences.
-
-5. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
-
----
-
-## Workflow:
-
-### Fullfill the request
-
-* If you have any questions, ask the user to clarify them.
-* 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.
-
-
-* Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
-*  analyze reports from `researcher` and s to create an implementation plan using 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).
-
-### Implementation
-
-* Use   to implement the plan step by step, follow the implementation plan in `.s` directory.
-* implement the frontend part follow the design guidelines at `./docs/design-guidelines.md` file.
-  * Use `media-processing` skill for image editing (crop, resize, remove background) if 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, mocks, cheats, tricks, temporary solutions, just to pass the build or github actions**, tests should be real and cover all possible cases.
-* run the tests, make sure it works, .
-* If there are issues or failed tests, 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, 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 "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.
-
-### Project Management & Documentation
-
-**If user approves the changes:**
-* Use `project-manager` and s  to update the project progress and documentation:
-  * update the project progress and task status in the given plan file.
-  * update the docs in `./docs` directory if needed.
-  * create a project roadmap at `./docs/project-roadmap.md` file.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-**If user rejects the changes:**
-* Ask user to explain the issues and ask main agent to fix all of them and repeat the process.
-
-### Onboarding
-
-* Instruct the user to get started with the feature if needed (for example: grab the API key, set up the environment variables, etc).
-* Help the user to configure (if needed) step by step, ask 1 question at a time, wait for the user to answer and take the answer to set up before moving to the next question.
-* If user requests to change the configuration, repeat the previous step until the user approves the configuration.
-
-### 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 changes to git repository, if yes, commit to local repository only.
-* **IMPORTANT:** Do NOT push to remote repository. Only commit locally. If user wants to push, suggest them to run `/commit` or `git push` manually.
-- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-
-**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.
+| Command | Description |
+|---------|-------------|
+| `/ck.test` | Run tests |
+| `/ck.git` | Commit changes |
+| `/ck.review` | Code review |

package/templates/repo/.github/prompts/ck-debug.prompt.md

@@ -1,14 +1,114 @@
 ---
 agent: 'agent'
-description: 'Debugging technical issues and providing solutions.'
-tools: ['search/codebase', 'search/changes', 'read/problems', 'read/terminalLastCommand']
+description: 'Debug systematically with root cause analysis before fixes'
+argument-hint: 'Describe the issue to debug'
 ---
 
-**Reported Issues**:
-${input}
+## Context
+Issue to debug:
+<issue>${input}</issue>
 
-find the root cause of the issues, then analyze and explain the reports to the user.
+## Core Principle
 
-**IMPORTANT**: **Do not** implement the fix automatically.
-**IMPORTANT:** 
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+**NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST**
+
+Random fixes waste time and create new bugs. Find the root cause, fix at source, validate at every layer, verify before claiming success.
+
+## When to Use
+
+**Always use for:** Test failures, bugs, unexpected behavior, performance issues, build failures, integration problems, before claiming work complete
+
+**Especially when:** Under time pressure, "quick fix" seems obvious, tried multiple fixes, don't fully understand issue, about to claim success
+
+## The Four Phases
+
+### Phase 1: Root Cause Investigation
+1. Read error messages completely
+2. Reproduce the issue consistently
+3. Check recent changes (git diff, git log)
+4. Gather evidence before theorizing
+
+### Phase 2: Pattern Analysis
+1. Find working examples in codebase
+2. Compare working vs broken code
+3. Identify what's different
+4. Document findings
+
+### Phase 3: Hypothesis and Testing
+1. Form theory based on evidence
+2. Test with minimal changes
+3. Verify hypothesis is correct
+4. Document confirmation
+
+### Phase 4: Implementation
+1. Create test that catches the bug
+2. Fix at the root cause (not symptom)
+3. Verify fix works
+4. Ensure no regressions
+
+**Key rule:** Complete each phase before proceeding. No fixes without Phase 1.
+
+## Root Cause Tracing
+
+When error appears deep in execution:
+1. Start at error location
+2. Trace backward level-by-level
+3. Find where invalid data originated
+4. Fix at source, not at symptom
+
+## Defense-in-Depth
+
+After finding root cause, validate at every layer:
+1. **Entry validation** - Input sanitization
+2. **Business logic** - State validation
+3. **Environment guards** - Config validation
+4. **Debug instrumentation** - Logging
+
+## Verification
+
+**Iron law:** NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
+
+1. Run the command
+2. Read the output
+3. Then claim the result
+
+## Red Flags
+
+Stop and follow process if thinking:
+- "Quick fix for now, investigate later"
+- "Just try changing X and see if it works"
+- "It's probably X, let me fix that"
+- "Should work now" / "Seems fixed"
+- "Tests pass, we're done"
+
+**All mean:** Return to systematic process.
+
+## Output Format
+
+```markdown
+## Debug Report
+
+### Issue Summary
+- What: [Brief description]
+- When: [When it occurs]
+- Impact: [Severity]
+
+### Root Cause
+[Explanation of actual cause]
+
+### Fix Applied
+[What was changed and why]
+
+### Verification
+[Evidence that fix works]
+```
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck.test` | Run tests to verify |
+| `/ck.fix` | Apply fix |
+| `/ck.git` | Commit fix |

package/templates/repo/.github/prompts/ck-docs.prompt.md

@@ -0,0 +1,101 @@
+---
+agent: 'agent'
+description: 'Search library/framework documentation via context7'
+argument-hint: 'Library name or documentation query'
+tools: ['web/fetch']
+---
+
+## Context
+Documentation query:
+<query>${input}</query>
+
+## Your Role
+
+Search and retrieve up-to-date documentation for libraries, frameworks, and packages using context7.com llms.txt standard.
+
+## When to Use
+
+- Need API documentation for a library
+- Looking for code examples and patterns
+- Checking latest features or deprecations
+- Understanding library configuration
+- Finding best practices for a framework
+
+## Workflow
+
+### 1. Detect Query Type
+
+**Topic-specific query** (e.g., "How do I use date picker in shadcn?")
+- Extract: library name + topic keyword
+- Faster search path: 2-3 URLs
+
+**General library query** (e.g., "Documentation for Next.js")
+- Comprehensive search: 8+ URLs
+- May need multiple agents
+
+### 2. Search Strategy
+
+**For topic-specific queries:**
+1. Search context7 for library + topic
+2. Retrieve 2-3 most relevant URLs
+3. Read and summarize findings
+
+**For general queries:**
+1. Search context7 for library
+2. Analyze URL list for categorization
+3. Prioritize: critical > important > supplementary
+4. Deploy parallel reads if many URLs
+
+### 3. URL Priority
+
+| Category | Examples | Priority |
+|----------|----------|----------|
+| Critical | Getting started, core API | Read first |
+| Important | Configuration, common patterns | Read second |
+| Supplementary | Advanced, edge cases | Read if needed |
+
+## Output Format
+
+```markdown
+## Documentation Summary
+
+### Library: [Name] v[Version]
+
+### Quick Answer
+[Direct answer to user's question]
+
+### Key Points
+- Point 1
+- Point 2
+- Point 3
+
+### Code Example
+```language
+// Relevant code example
+```
+
+### Related Topics
+- [Topic 1](url)
+- [Topic 2](url)
+
+### Sources
+- [Doc Title](url)
+```
+
+## Best Practices
+
+1. **Be specific** - Include version numbers when relevant
+2. **Show examples** - Code examples are more useful than descriptions
+3. **Note deprecations** - Warn about deprecated APIs
+4. **Link sources** - Always provide source URLs
+5. **Stay current** - Prefer latest documentation
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck.ask` | Ask technical questions |
+| `/ck.plan` | Create implementation plan |
+| `/ck.cook` | Implement feature |

package/templates/repo/.github/prompts/ck-fix.prompt.md

@@ -1,7 +1,7 @@
 ---
 agent: 'agent'
-description: 'Analyze and fix issues [INTELLIGENT ROUTING]'
-tools: ['search/codebase', 'search/changes', 'read/problems', 'read/terminalLastCommand']
+description: 'Analyze and fix issues with intelligent routing'
+argument-hint: 'Describe the issues to fix'
 ---
 
 **Analyze issues and route to specialized fix command:**
@@ -10,35 +10,43 @@ tools: ['search/codebase', 'search/changes', 'read/problems', 'read/terminalLast
 ## Decision Tree
 
 **1. Check for existing plan:**
-- If markdown plan exists →  <path-to-plan>`
+- If markdown plan exists → `/ck:code <path-to-plan>`
 
 **2. Route by issue type:**
 
 **A) Type Errors** (keywords: type, typescript, tsc, type error)
-→ `/fix:types`
+→ `/ck:fix:types`
 
 **B) UI/UX Issues** (keywords: ui, ux, design, layout, style, visual, button, component, css, responsive)
-→ `/fix:ui <detailed-description>`
+→ `/ck:fix:ui <detailed-description>`
 
 **C) CI/CD Issues** (keywords: github actions, pipeline, ci/cd, workflow, deployment, build failed)
-→ `/fix:ci <github-actions-url-or-description>`
+→ `/ck:fix:ci <github-actions-url-or-description>`
 
 **D) Test Failures** (keywords: test, spec, jest, vitest, failing test, test suite)
-→ `/fix:test <detailed-description>`
+→ `/ck:fix:test <detailed-description>`
 
 **E) Log Analysis** (keywords: logs, error logs, log file, stack trace)
-→ `/fix:logs <detailed-description>`
+→ `/ck:fix:logs <detailed-description>`
 
 **F) Multiple Independent Issues** (2+ unrelated issues in different areas)
-→ `/fix:parallel <detailed-description>`
+→ `/ck:fix:parallel <detailed-description>`
 
 **G) Complex Issues** (keywords: complex, architecture, refactor, major, system-wide, multiple components)
-→ `/fix:hard <detailed-description>`
+→ `/ck:fix:hard <detailed-description>`
 
 **H) Simple/Quick Fixes** (default: small bug, single file, straightforward)
-→ `/fix:fast <detailed-description>`
+→ `/ck:fix:fast <detailed-description>`
 
 ## Notes
 - `detailed-description` = enhanced prompt describing issue in detail
 - If unclear, ask user for clarification before routing
-- Can combine routes: e.g., multiple type errors + UI issue → `/fix:parallel`
+- Can combine routes: e.g., multiple type errors + UI issue → `/ck:fix:parallel`
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck.test` | Run tests and analyze results |