cokit-cli 1.2.0 → 1.2.3

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

@@ -0,0 +1,50 @@
+---
+agent: 'agent'
+description: 'Analyze and fix UI issues'
+argument-hint: 'Describe the UI issue'
+---
+## Variant Notice
+**IMPORTANT — Read before proceeding.**
+`ck-fix-ui` is an internal mode for UI/UX issues — it is meant to be selected automatically by AI when you run `/ck-fix`.
+You don't need to call this directly. Just use `/ck-fix` and AI will pick the right mode for you.
+Before executing, you MUST output the following message **exactly as written** and wait for user response:
+
+---
+**Variant Notice**
+
+`ck-fix-ui` is an internal mode for UI/UX issues — it is meant to be selected automatically by AI when you run `/ck-fix`.
+You don't need to call this directly. Just use `/ck-fix` and AI will pick the right mode for you.
+
+Do you want to continue anyway, or switch to `/ck-fix`? **[Continue / Switch to /ck-fix]**
+
+---
+
+Only proceed if user explicitly confirms Continue.
+If user chooses "Switch to /ck-fix", run  immediately — do NOT ask user to re-enter their input.
+
+
+## Required Skills
+1. **`frontend-design`** - Design patterns and implementation
+
+Read and analyze `./docs/design-guidelines.md` then fix the following issues:
+<issue>${input}</issue>
+
+## Workflow
+1. Activate `frontend-design` skill to understand design patterns and best practices.
+2. Implement the fix step by step following design guidelines.
+3. Take screenshots of the fix and analyze to verify it matches the design guideline and addresses all issues.
+   - If the issues are not addressed, repeat the process until all issues are addressed.
+4. Test the fix and compile the code to make sure it works.
+   - If there are issues or failed tests, fix all of them and repeat until all tests pass.
+5. Final Report:
+   * Summary of changes, guide user to get started, suggest next steps.
+   * Ask the user if they want to commit and push to git repository.
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck-test` | Run tests and analyze results |
+| `/ck-git` | Commit changes |

package/prompts/ck-fix.prompt.md

@@ -10,38 +10,35 @@ argument-hint: 'Describe the issues to fix'
 ## Decision Tree
 
 **1. Check for existing plan:**
-- If markdown plan exists → `/ck:code <path-to-plan>`
+- If markdown plan exists → `/ck-cook <path-to-plan>`
 
 **2. Route by issue type:**
 
 **A) Type Errors** (keywords: type, typescript, tsc, type error)
-→ `/ck:fix:types`
+→ `/ck-fix-types`
 
 **B) UI/UX Issues** (keywords: ui, ux, design, layout, style, visual, button, component, css, responsive)
-→ `/ck:fix:ui <detailed-description>`
+→ `/ck-fix-ui <detailed-description>`
 
 **C) CI/CD Issues** (keywords: github actions, pipeline, ci/cd, workflow, deployment, build failed)
-→ `/ck: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)
-→ `/ck:fix:test <detailed-description>`
+→ `/ck-fix-test <detailed-description>`
 
 **E) Log Analysis** (keywords: logs, error logs, log file, stack trace)
-→ `/ck:fix:logs <detailed-description>`
+→ `/ck-fix-logs <detailed-description>`
 
-**F) Multiple Independent Issues** (2+ unrelated issues in different areas)
-→ `/ck:fix:parallel <detailed-description>`
+**F) Complex/Multiple Issues** (keywords: complex, architecture, refactor, major, system-wide, multiple components, 2+ unrelated issues)
+→ `/ck-fix-hard <detailed-description>`
 
-**G) Complex Issues** (keywords: complex, architecture, refactor, major, system-wide, multiple components)
-→ `/ck:fix:hard <detailed-description>`
-
-**H) Simple/Quick Fixes** (default: small bug, single file, straightforward)
-→ `/ck:fix:fast <detailed-description>`
+**G) Simple/Quick Fixes** (default: small bug, single file, straightforward)
+→ `/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 → `/ck:fix:parallel`
+- Can combine routes: e.g., multiple type errors + UI issue → `/ck-fix-hard`
 
 ---
 
@@ -49,4 +46,5 @@ argument-hint: 'Describe the issues to fix'
 
 | Command | Description |
 |---------|-------------|
-| `/ck.test` | Run tests and analyze results |
+| `/ck-test` | Run tests and analyze results |
+| `/ck-git` | Commit changes |

package/prompts/ck-git.prompt.md

@@ -100,5 +100,5 @@ gh pr create --title "type(scope): description" --body "## Summary
 
 | Command | Description |
 |---------|-------------|
-| `/ck.test` | Run tests before push |
-| `/ck.review` | Code review |
+| `/ck-test` | Run tests before push |
+| `/ck-review` | Code review |

package/prompts/ck-help.prompt.md

@@ -6,7 +6,7 @@ tools: ['execute/runInTerminal', 'execute/getTerminalOutput']
 ---
 
 Think harder.
-All-in-one ClaudeKit guide. Run the script and present output based on type markers.
+All-in-one CoKit guide. Run the script and present output based on type markers.
 
 ## Intent Validation
 
@@ -126,9 +126,9 @@ Never replace or summarize the script output. Always show it fully, then enhance
 
 ## Important: Correct Workflows
 
-- **`/ck.plan` → `/cook`**: Plan first, then execute the plan
-- **`/cook`**: Standalone - plans internally, no separate `/ck.plan` needed
-- **NEVER** suggest `/ck.plan` → `/cook` (cook has its own planning)
+- **`/ck-plan` → `/cook`**: Plan first, then execute the plan
+- **`/cook`**: Standalone - plans internally, no separate `/ck-plan` needed
+- **NEVER** suggest `/ck-plan` → `/cook` (cook has its own planning)
 
 ---
 
@@ -136,5 +136,7 @@ Never replace or summarize the script output. Always show it fully, then enhance
 
 | 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/prompts/ck-journal.prompt.md

@@ -3,7 +3,7 @@ agent: 'agent'
 description: 'Write journal entries from recent changes and memories'
 ---
 
-Use the `journal-writer` subagent to explore the memories and recent code changes, and write some journal entries.
+Use the `journal-writer` agent to explore the memories and recent code changes, and write some journal entries.
 Journal entries should be concise and focused on the most important events, key changes, impacts, and decisions.
 Keep journal entries in the `./docs/journals/` directory.
 
@@ -13,5 +13,7 @@ Keep journal entries in the `./docs/journals/` directory.
 
 | Command | Description |
 |---------|-------------|
-| `/ck.brainstorm` | Explore ideas |
-| `/ck.plan` | Create plan |
+| `/ck-brainstorm` | Explore ideas |
+| `/ck-plan` | Create plan |
+| `/ck-fix` | Analyze and fix issues |
+| `/ck-spec-specify` | Write detailed feature spec |

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

@@ -3,6 +3,25 @@ agent: 'agent'
 description: 'No research. Only analyze and create an implementation plan'
 argument-hint: 'Task description or requirements'
 ---
+## Variant Notice
+**IMPORTANT — Read before proceeding.**
+`ck-plan-fast` is an internal mode for quick planning without research — it is meant to be selected automatically by AI when you run `/ck-plan`.
+You don't need to call this directly. Just use `/ck-plan` and AI will pick the right mode for you.
+Before executing, you MUST output the following message **exactly as written** and wait for user response:
+
+---
+**Variant Notice**
+
+`ck-plan-fast` is an internal mode for quick planning without research — it is meant to be selected automatically by AI when you run `/ck-plan`.
+You don't need to call this directly. Just use `/ck-plan` and AI will pick the right mode for you.
+
+Do you want to continue anyway, or switch to `/ck-plan`? **[Continue / Switch to /ck-plan]**
+
+---
+
+Only proceed if user explicitly confirms Continue.
+If user chooses "Switch to /ck-plan", run  immediately — do NOT ask user to re-enter their input.
+
 
 Think.
 Activate `planning` skill.
@@ -20,10 +39,10 @@ Check the `## Plan Context` section in the injected context:
 - If "Plan: none" → Create new plan using naming from `## Naming` section.
 
 ## Workflow
-Use `planner` subagent to:
+Use `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 subagent during the process.
+   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. Analyze the codebase by reading `codebase-summary.md`, `code-standards.md`, `system-architecture.md` and `project-overview-pdr.md` file.
 4. Gathers all information and create an implementation plan of this task.
@@ -65,7 +84,7 @@ This reminder is **NON-NEGOTIABLE** - always output it after presenting the plan
   created: {YYYY-MM-DD}
   ---
   ```
-- Save the overview access point at `{plan-dir}/ck.plan.md`. Keep it generic, under 80 lines, and list each implementation phase with status and progress plus links to phase files.
+- Save the overview access point at `{plan-dir}/ck-plan.md`. Keep it generic, under 80 lines, and list each implementation phase with status and progress plus links to phase files.
 - 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
@@ -81,5 +100,7 @@ This reminder is **NON-NEGOTIABLE** - always output it after presenting the plan
 
 | Command | Description |
 |---------|-------------|
-| `/ck.test` | Run tests and analyze results |
-| `/ck.fix` | Analyze and fix issues |
+| `/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

@@ -4,6 +4,25 @@ description: 'Research, analyze, and create an implementation plan'
 argument-hint: 'Task description or requirements'
 tools: ['web/fetch', 'search/codebase', 'read/readFile', 'search/listDirectory', 'edit/createFile', 'edit/editFiles']
 ---
+## Variant Notice
+**IMPORTANT — Read before proceeding.**
+`ck-plan-hard` is an internal mode for deep research + planning — it is meant to be selected automatically by AI when you run `/ck-plan`.
+You don't need to call this directly. Just use `/ck-plan` and AI will pick the right mode for you.
+Before executing, you MUST output the following message **exactly as written** and wait for user response:
+
+---
+**Variant Notice**
+
+`ck-plan-hard` is an internal mode for deep research + planning — it is meant to be selected automatically by AI when you run `/ck-plan`.
+You don't need to call this directly. Just use `/ck-plan` and AI will pick the right mode for you.
+
+Do you want to continue anyway, or switch to `/ck-plan`? **[Continue / Switch to /ck-plan]**
+
+---
+
+Only proceed if user explicitly confirms Continue.
+If user chooses "Switch to /ck-plan", run  immediately — do NOT ask user to re-enter their input.
+
 
 Think harder.
 Activate `planning` skill.
@@ -23,14 +42,14 @@ Check the `## Plan Context` section in the injected context:
 ## Workflow
 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 subagent during the process.
+   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:
    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` subagent with the prompt to create an implementation plan of this task.
-6. Main agent receives the implementation plan from `planner` subagent, and ask user to review the plan
+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
 
 ## Post-Plan Validation (Optional)
 
@@ -41,11 +60,11 @@ After plan creation, offer validation interview to confirm decisions before impl
 | Mode | Behavior |
 |------|----------|
 | `prompt` | Ask user: "Validate this plan with a brief interview?" → Yes (Recommended) / No |
-| `auto` | Automatically execute `/ck.plan:validate {plan-path}` |
+| `auto` | Automatically execute `/ck-plan-validate {plan-path}` |
 | `off` | Skip validation step entirely |
 
-**If mode is `prompt`:** Use `AskUserQuestion` tool with options above.
-**If user chooses validation or mode is `auto`:** Execute `/ck.plan:validate {plan-path}` SlashCommand.
+**If mode is `prompt`:** Present the options above directly in your response and wait for user to choose.
+**If user chooses validation or mode is `auto`:** Execute `/ck-plan-validate {plan-path}` SlashCommand.
 
 ## Context Reminder (MANDATORY)
 
@@ -92,7 +111,7 @@ This reminder is **NON-NEGOTIABLE** when validation is skipped.
   created: {YYYY-MM-DD}
   ---
   ```
-- Save the overview access point at `{plan-dir}/ck.plan.md`. Keep it generic, under 80 lines, and list each implementation phase with status and progress plus links to phase files.
+- Save the overview access point at `{plan-dir}/ck-plan.md`. Keep it generic, under 80 lines, and list each implementation phase with status and progress plus links to phase files.
 - 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
@@ -108,5 +127,7 @@ This reminder is **NON-NEGOTIABLE** when validation is skipped.
 
 | Command | Description |
 |---------|-------------|
-| `/ck.test` | Run tests and analyze results |
-| `/ck.fix` | Analyze and fix issues |
+| `/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-validate.prompt.md

@@ -0,0 +1,209 @@
+---
+agent: 'agent'
+description: 'Validate plan with critical questions interview'
+argument-hint: 'Path to plan directory'
+---
+## Variant Notice
+**IMPORTANT — Read before proceeding.**
+`ck-plan-validate` is an internal mode for validating an existing plan with interview questions — it is meant to be selected automatically by AI when you run `/ck-plan`.
+You don't need to call this directly. Just use `/ck-plan` and AI will pick the right mode for you.
+Before executing, you MUST output the following message **exactly as written** and wait for user response:
+
+---
+**Variant Notice**
+
+`ck-plan-validate` is an internal mode for validating an existing plan with interview questions — it is meant to be selected automatically by AI when you run `/ck-plan`.
+You don't need to call this directly. Just use `/ck-plan` and AI will pick the right mode for you.
+
+Do you want to continue anyway, or switch to `/ck-plan`? **[Continue / Switch to /ck-plan]**
+
+---
+
+Only proceed if user explicitly confirms Continue.
+If user chooses "Switch to /ck-plan", run  immediately — do NOT ask user to re-enter their input.
+
+
+## Your mission
+
+Interview the user with critical questions to validate assumptions, confirm decisions, and surface potential issues in an implementation plan before coding begins.
+
+## Plan Resolution
+
+1. If `${input}` provided → Use that path
+2. Else check `## Plan Context` section → Use active plan path
+3. If no plan found → Ask user to specify path or run `/ck-plan-hard` first
+
+## Configuration (from injected context)
+
+Check `## Plan Context` section for validation settings:
+- `mode` - Controls auto/prompt/off behavior
+- `questions` - Range like `3-8` (min-max)
+
+These values are automatically injected from user config. Use them as constraints.
+
+## Workflow
+
+### Step 1: Read Plan Files
+
+Read the plan directory:
+- `plan.md` - Overview and phases list
+- `phase-*.md` - All phase files
+- Look for decision points, assumptions, risks, tradeoffs
+
+### Step 2: Extract Question Topics
+
+Scan plan content for:
+
+| Category | Keywords to detect |
+|----------|-------------------|
+| **Architecture** | "approach", "pattern", "design", "structure", "database", "API" |
+| **Assumptions** | "assume", "expect", "should", "will", "must", "default" |
+| **Tradeoffs** | "tradeoff", "vs", "alternative", "option", "choice", "either/or" |
+| **Risks** | "risk", "might", "could fail", "dependency", "blocker", "concern" |
+| **Scope** | "phase", "MVP", "future", "out of scope", "nice to have" |
+
+### Step 3: Generate Questions
+
+For each detected topic, formulate a concrete question:
+
+**Question format rules:**
+- Each question must have 2-4 concrete options
+- Mark recommended option with "(Recommended)" suffix
+- Include "Other" option is automatic - don't add it
+- Questions should surface implicit decisions
+
+**Example questions:**
+
+```
+Category: Architecture
+Question: "How should the validation results be persisted?"
+Options:
+1. Save to plan.md frontmatter (Recommended) - Updates existing plan
+2. Create validation-answers.md - Separate file for answers
+3. Don't persist - Ephemeral validation only
+```
+
+```
+Category: Assumptions
+Question: "The plan assumes API rate limiting is not needed. Is this correct?"
+Options:
+1. Yes, rate limiting not needed for MVP
+2. No, add basic rate limiting now (Recommended)
+3. Defer to Phase 2
+```
+
+### Step 4: Interview User
+
+Present questions directly in your response, listing each with numbered options. Then stop and wait for the user to answer before proceeding.
+
+**Rules:**
+- Use question count from `## Plan Context` → `Validation: mode=X, questions=MIN-MAX`
+- Group related questions when possible (max 4 questions per response)
+- Focus on: assumptions, risks, tradeoffs, architecture
+- Format each question with numbered options for easy selection
+
+### Step 5: Document Answers
+
+After collecting answers, update `plan.md` with a detailed validation log. If a `## Validation Log` section already exists (from previous sessions), **append** a new session block — never overwrite history.
+
+1. Add or append to `## Validation Log` section in `plan.md`:
+
+```markdown
+## Validation Log
+
+### Session 1 — {YYYY-MM-DD}
+**Trigger:** {what prompted this validation — initial plan creation, re-validation after scope change, etc.}
+**Questions asked:** {count}
+
+#### Questions & Answers
+
+1. **[{Category}]** {full question text}
+   - Options: {A} | {B} | {C}
+   - **Answer:** {user's choice}
+   - **Custom input:** {verbatim "Other" text if user selected Other, otherwise omit this line}
+   - **Rationale:** {why this decision matters for implementation}
+
+2. **[{Category}]** {full question text}
+   - Options: {A} | {B} | {C}
+   - **Answer:** {user's choice}
+   - **Custom input:** {verbatim text, omit if N/A}
+   - **Rationale:** {why this matters}
+
+#### Confirmed Decisions
+- {decision}: {choice} — {brief why}
+
+#### Action Items
+- [ ] {specific change needed based on answers}
+
+#### Impact on Phases
+- Phase {N}: {what needs updating and why}
+```
+
+**Recording rules:**
+- **Full question text**: Copy the exact question asked, not a summary
+- **All options**: List every option that was presented
+- **Verbatim custom input**: If user selected "Other" and typed custom text, record it exactly as entered — this often contains critical context
+- **Rationale**: Explain why the decision affects implementation (helps future agents understand intent)
+- **Session numbering**: Increment session number from last existing session. First validation = Session 1
+- **Trigger**: State what prompted this validation round (initial, re-validation, scope change, etc.)
+
+2. If answers require plan changes, document them in `#### Impact on Phases` section.
+
+### Step 6: Propagate Changes to Phases (Auto-Apply)
+
+**Auto-propagate** validation decisions to affected phase files.
+
+**Process:**
+1. Parse "Impact on Phases" section → If empty, skip and report "No phase changes required"
+2. For each phase reference (accepts "Phase 2", "phase-02", "P2"):
+   - Search for `phase-{N:02d}-*.md` files → If missing, warn and skip
+   - Locate target section (exact → fuzzy → fallback to Key Insights)
+   - Apply change + add marker: `<!-- Updated: Validation Session N - {change} -->`
+   - Skip if same-session marker already exists (prevent duplication)
+
+**Section mapping:**
+| Change Type | Target Section |
+|-------------|----------------|
+| Requirements | Requirements |
+| Architecture | Architecture |
+| Scope | Overview / Implementation Steps |
+| Risk | Risk Assessment |
+| Unknown | Key Insights (new subsection) |
+
+**Error handling:** Best-effort — log warnings for missing files/sections, continue with others, report all in Output.
+
+## Output
+
+After validation completes, provide summary:
+- Number of questions asked
+- Key decisions confirmed
+- **Phase propagation results:**
+  - Files updated (with section names)
+  - Warnings (skipped phases, fallback sections)
+  - Errors (if any write failures)
+- Any items flagged for plan revision
+- Recommendation: proceed to implementation or revise plan first
+
+## Next Steps (MANDATORY)
+
+**IMPORTANT:** After providing the validation summary, you MUST remind the user with the **full absolute path**:
+
+> **Best Practice:** Run `/clear` before implementing to start with fresh context.
+> Then run:
+> ```
+> /cook --auto {ABSOLUTE_PATH_TO_PLAN_DIR}/plan.md
+> ```
+> *(Replace with actual absolute path)*
+>
+> **Why `--auto`?** Plan was already validated - safe to skip review gates.
+> **Why absolute path?** After `/clear`, the new session loses context. Worktree paths won't be discoverable without the full path.
+>
+> Fresh context helps the agent focus solely on implementation without planning context pollution, improving plan adherence.
+
+This reminder is **NON-NEGOTIABLE** - always output it at the end of validation with the actual absolute path.
+
+## Important Notes
+
+**IMPORTANT:** Only ask questions about genuine decision points - don't manufacture artificial choices.
+**IMPORTANT:** If plan is simple with few decisions, it's okay to ask fewer than min questions.
+**IMPORTANT:** Prioritize questions that could change implementation significantly.

package/prompts/ck-plan.prompt.md

@@ -4,23 +4,57 @@ description: 'Intelligent plan creation with prompt enhancement'
 argument-hint: 'Task description or requirements'
 ---
 
-## Your mission
-<task>
-${input}
-</task>
+**Analyze task and route to the right planning mode:**
+<task>${input}</task>
 
-## Pre-Creation Check (Active vs Suggested Plan Detection)
+## Decision Tree
 
-Check the `## Plan Context` section in the injected context:
+**1. Check for existing plan:**
+- Check `## Plan Context` section in injected context
 - If "Plan:" shows a path → Active plan exists. Ask user: "Active plan found: {path}. Continue with this? [Y/n]"
-- If "Suggested:" shows a path → Branch-matched plan hint only. Ask user if they want to activate it or create new.
-- If "Plan: none" → Proceed to create new plan using naming pattern from `## Naming` section.
+- If "Suggested:" shows a path → Branch-matched hint. Ask user to activate or create new.
+- If "Plan: none" → Proceed to step 2.
+
+**2. Route by complexity:**
+
+**A) Simple/Quick Tasks** (keywords: small, quick, simple, straightforward, single file, minor, tweak, < 2 hours)
+→ `/ck-plan-fast <detailed-instructions-prompt>`
+
+**B) Complex/Research-Heavy Tasks** (keywords: complex, research, unfamiliar, architecture, multi-component, integration, large, major, multi-day)
+→ `/ck-plan-hard <detailed-instructions-prompt>`
+
+**C) Validate Existing Plan** (keywords: validate, review plan, check plan, verify assumptions)
+→ `/ck-plan-validate <path-to-plan>`
+
+**D) Default/Medium Tasks** (anything else)
+→ Execute planning workflow below directly.
+
+## Workflow (for Default/Medium tasks)
 
-## Workflow
-- Analyze the given task and use `AskUserQuestion` tool to ask for more details if needed.
 - Activate `planning` skill.
+- Analyze the given task and ask clarifying questions directly if needed. Wait for user response before proceeding.
 - Note: `detailed-instructions-prompt` is **an enhanced prompt** that describes the task in detail based on the provided task description.
 
+## Post-Plan Validation (Optional)
+
+After plan creation, offer validation for non-trivial plans.
+
+Check `## Plan Context` → `Validation: mode=X, questions=MIN-MAX`:
+
+| Mode | Behavior |
+|------|----------|
+| `prompt` | Ask user: "Validate this plan with a brief interview?" → Yes (Recommended) / No |
+| `auto` | Automatically execute `/ck-plan-validate {plan-path}` |
+| `off` | Skip validation step entirely |
+
+If user chooses validation or mode is `auto`: Execute `/ck-plan-validate {plan-path}`.
+
+## Notes
+- `detailed-instructions-prompt` = enhanced prompt describing task in detail
+- If unclear about complexity, default to this prompt's workflow (medium)
+- Fast plans skip validation by default
+- 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.
@@ -34,5 +68,8 @@ Check the `## Plan Context` section in the injected context:
 
 | Command | Description |
 |---------|-------------|
-| `/ck.test` | Run tests and analyze results |
-| `/ck.fix` | Analyze and fix issues |
+| `/ck-plan-validate` | Validate plan with critical questions |
+| `/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 |