cokit-cli 1.0.8 → 1.2.0

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

@@ -1,117 +0,0 @@
----
-agent: 'agent'
-description: 'Validate plan with critical questions interview'
-tools: ['search/codebase', 'search/changes', 'read/problems']
----
-
-## 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 :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 to user.
-
-**Rules:**
-- Use question count from `## Plan Context` → `Validation: mode=X, questions=MIN-MAX`
-- Group related questions when possible (max 4 questions per tool call)
-- Focus on: assumptions, risks, tradeoffs, architecture
-
-### Step 5: Document Answers
-
-After collecting answers, update the plan:
-
-1. Add `## Validation Summary` section to `plan.md`:
-```markdown
-## Validation Summary
-
-**Validated:** {date}
-**Questions asked:** {count}
-
-### Confirmed Decisions
-- {decision 1}: {user choice}
-- {decision 2}: {user choice}
-
-### Action Items
-- [ ] {any changes needed based on answers}
-```
-
-2. If answers require plan changes, note them but **do not modify phase files** - just document what needs updating.
-
-## Output
-
-After validation completes, provide summary:
-- Number of questions asked
-- Key decisions confirmed
-- Any items flagged for plan revision
-- Recommendation: proceed to implementation or revise plan first
-
-## 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-review-codebase.prompt.md

@@ -1,44 +0,0 @@
----
-agent: 'agent'
-description: 'Scan & analyze the codebase.'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems']
----
-
-Think harder to scan the codebase and analyze it follow the Orchestration Protocol, Core Responsibilities,  Team and Development Rules: 
-<tasks>${input}</tasks>
-
----
-
-## Role Responsibilities
-- You are an elite software engineering expert who specializes in system architecture design and technical decision-making. 
-- 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.
-- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-
----
-
-## Workflow:
-
-**IMPORTANT:** 
-
-### Research
-
-* 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.
-* 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
-* analyze reports from `researcher` and s 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, 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.

package/prompts/ck-scout-ext.prompt.md

@@ -1,35 +0,0 @@
----
-agent: 'agent'
-description: 'Use external agentic tools to scout given directories'
-tools: ['search/codebase', 'search/changes', 'read/terminalLastCommand']
----
-
-## Purpose
-
-Utilize external agentic tools to scout given directories or explore the codebase for files needed to complete the task using a fast, token efficient agent.
-
-## Variables
-
-USER_PROMPT: $1
-SCALE: $2 (defaults to 3)
-RELEVANT_FILE_OUTPUT_DIR: Use `Report:` from `## Naming` section
-
-## Workflow:
-- 5-flash-preview-09-2025` (if count <= 3)
-  - `opencode run "[prompt]" --model opencode/grok-code` (if count > 3 and count < 6)
-  - if count >= 6, spawn s to search the codebase 
-
-**Why use external agentic tools?**
-- External agentic tools are faster and more efficient when using LLMs with large context windows (1M+ tokens).
-
-**How to prompt the agents:**
-- If `gemini` or `opencode` is not available, ask the user if they want to install it:
-  - If **yes**, install it (if there are permission issues, instruct the user to install it manually, including authentication steps)
-  - If **no**, use the default s.
-- IMPORTANT: Kick these agents off  using the , analyze and divide folders for each agent to scout intelligently and quickly.
-- IMPORTANT: These agents are calling OTHER agentic coding tools to search the codebase. DO NOT call any search tools yourself.
-- IMPORTANT: That means )
-- IMPORTANT: Instruct the agents to quickly search the codebase for files needed to complete the task. This isn't about a full blown search, just a quick search to find the files needed to complete the task.
-- Instruct the  use a timeout of 3 minutes for each agent's bash call. Skip any agents that don't return within the timeout, don't restart them.
-- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.

package/prompts/ck-skill-add.prompt.md

@@ -1,36 +0,0 @@
----
-agent: 'agent'
-description: 'Add new reference files or scripts to a skill'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems']
----
-
-Think harder.
-Use `skill-creator` skill.
-
-## Arguments
-$1: skill name (required, default: "")
-$2: reference or script prompt (required, default: "")
-If $1 or $2 is not provided, ask the user to provide it.
-
-## Your mission
-Add new reference files or scripts to a skill at  directory.
-
-## Requirements
-<reference-or-script-prompt>
-$2
-</reference-or-script-prompt>
-
-## Rules of Skill Creation:
-Base on the requirements:
-- Always keep in mind that `SKILL.md` and reference files should be token consumption efficient, so that **progressive disclosure** can be leveraged at best.
-- `SKILL.md` is always short and concise, straight to the point, treat it as a quick reference guide.
-- If you're given nothing, ask for clarifications and  to research about the topic.
-- If you're given an URL, it's documentation page, explore every internal link and .
-- If you receive a lot of URLs, use multiple s to explore them , .
-- If you receive a lot of files, use multiple s to explore them , .
-- If you're given a Github URL, use [](https://repomix.com/guide/usage) command to summarize ([install it](https://repomix.com/guide/installation) if needed) and spawn multiple s to explore it , .
-
-**IMPORTANT:**
-- Skills are not documentation, they are practical instructions for GitHub Copilot to use the tools, packages, plugins or APIs to achieve the tasks.
-- Each skill teaches GitHub Copilot how to perform a specific development task, not what a tool does.
-- GitHub Copilot can activate multiple skills automatically to achieve the user's request.

package/prompts/ck-skill-create.prompt.md

@@ -1,29 +0,0 @@
----
-agent: 'agent'
-description: 'Create a new agent skill'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems']
----
-
-Ultrathink.
-Use `skill-creator` skill.
-
-## Your mission
-Create a new skill in  directory.
-
-## Requirements
-<user-prompt>${input}</user-prompt>
-
-## Rules of Skill Creation:
-Base on the requirements:
-- Always keep in mind that `SKILL.md` and reference files should be token consumption efficient, so that **progressive disclosure** can be leveraged at best.
-- `SKILL.md` is always short and concise, straight to the point, treat it as a quick reference guide.
-- If you're given nothing, ask for clarifications and  to research about the topic.
-- If you're given an URL, it's documentation page, explore every internal link and .
-- If you receive a lot of URLs, use multiple s to explore them , .
-- If you receive a lot of files, use multiple s to explore them , .
-- If you're given a Github URL, use [](https://repomix.com/guide/usage) command to summarize ([install it](https://repomix.com/guide/installation) if needed) and spawn multiple s to explore it , .
-
-**IMPORTANT:**
-- Skills are not documentation, they are practical instructions for GitHub Copilot to use the tools, packages, plugins or APIs to achieve the tasks.
-- Each skill teaches GitHub Copilot how to perform a specific development task, not what a tool does.
-- GitHub Copilot can activate multiple skills automatically to achieve the user's request.

package/prompts/ck-skill-fix-logs.prompt.md

@@ -1,22 +0,0 @@
----
-agent: 'agent'
-description: 'Fix the agent skill based on `logs.txt` file.'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems', 'read/terminalLastCommand']
----
-
-Think harder.
-Use `skill-creator` skill.
-
-## Your mission
-Fix the agent skill based on the current `logs.txt` file (in the project root directory).
-
-## Requirements
-<user-prompt>${input}</user-prompt>
-
-## Rules of Skill Fixing:
-Base on the requirements:
-- If you're given nothing, ask for clarifications and  to research about the topic.
-- If you're given an URL, it's documentation page, explore every internal link and .
-- If you receive a lot of URLs, use multiple s to explore them , .
-- If you receive a lot of files, use multiple s to explore them , .
-- If you're given a Github URL, use [](https://repomix.com/guide/usage) command to summarize ([install it](https://repomix.com/guide/installation) if needed) and spawn multiple s to explore it , .

package/prompts/ck-skill-optimize-auto.prompt.md

@@ -1,25 +0,0 @@
----
-agent: 'agent'
-description: 'Optimize an existing agent skill [auto]'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems']
----
-
-Think harder.
-Use `skill-creator` skill.
-
-## Arguments
-SKILL: $1 (default: `*`)
-PROMPT: $2 (default: empty)
-
-## Your mission
-Optimize an existing skill in  directory.
-Always keep in mind that `SKILL.md` and reference files should be token consumption efficient, so that **progressive disclosure** can be leveraged at best.
-`SKILL.md` is always short and concise, straight to the point, treat it as a quick reference guide.
-
-**IMPORTANT:**
-- Skills are not documentation, they are practical instructions for GitHub Copilot to use the tools, packages, plugins or APIs to achieve the tasks.
-- Each skill teaches GitHub Copilot how to perform a specific development task, not what a tool does.
-- GitHub Copilot can activate multiple skills automatically to achieve the user's request.
-
-## Additional instructions
-<additional-instructions>$PROMPT</additional-instructions>

package/prompts/ck-skill-optimize.prompt.md

@@ -1,34 +0,0 @@
----
-agent: 'agent'
-description: 'Optimize an existing agent skill'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems']
----
-
-Think harder.
-Use `skill-creator` skill.
-
-## Arguments
-SKILL: $1 (default: `*`)
-PROMPT: $2 (default: empty)
-
-## Your mission
-Propose a plan to optimize an existing skill in  directory.
-When you finish, ask user to review your plan:
-- If the user approve: Write down a plan follow "Output Requirements", then ask user if they want to start implementing.
-- If the user reject: Revise the plan or ask more questions to clarify more about the user's request (ask one question at the time), then repeat the review process.
-
-## Additional instructions
-<additional-instructions>$PROMPT</additional-instructions>
-
-## Output Requirements
-An output implementation plan must also follow the progressive disclosure structure:
-- Always keep in mind that `SKILL.md` and reference files should be token consumption efficient, so that **progressive disclosure** can be leveraged at best.
-- `SKILL.md` is always short and concise, straight to the point, treat it as a quick reference guide.
-- 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).
-
-**IMPORTANT:**
-- Skills are not documentation, they are practical instructions for GitHub Copilot to use the tools, packages, plugins or APIs to achieve the tasks.
-- Each skill teaches GitHub Copilot how to perform a specific development task, not what a tool does.
-- GitHub Copilot can activate multiple skills automatically to achieve the user's request.

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

@@ -1,46 +0,0 @@
----
-agent: 'agent'
-description: 'Plan to create a new agent skill'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems']
----
-
-Think harder.
-First: Activate `skill-creator` skill.
-
-Employ `sequential-thinking` or `problem-solving` skills for complex problem-solving that requires structured analysis
-Finally, when creating a plan,
-
-## Arguments
-SKILL: $1 (default: `*`)
-PROMPT: $2 (default: empty)
-
-## Your mission
-Propose a plan to create a new skill in  directory.
-When you finish, ask user to review your plan:
-- If the user approve: Write down a plan follow "Output Requirements", then ask user if they want to start implementing.
-- If the user reject: Revise the plan or ask more questions to clarify more about the user's request (ask one question at the time), then repeat the review process.
-
-## Additional instructions
-<additional-instructions>$PROMPT</additional-instructions>
-
-## 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.
-
-## Output Requirements
-An output implementation plan must also follow the progressive disclosure structure:
-- Always keep in mind that `SKILL.md` and reference files should be token consumption efficient, so that **progressive disclosure** can be leveraged at best.
-- `SKILL.md` is always short and concise, straight to the point, treat it as a quick reference guide.
-- 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).
-
-**IMPORTANT:**
-- Analyze the given task and ask for more details if needed.
-- Ensure token consumption efficiency while maintaining high quality.
-- Skills are not documentation, they are practical instructions for GitHub Copilot to use the tools, packages, plugins or APIs to achieve the tasks.
-- Each skill teaches GitHub Copilot how to perform a specific development task, not what a tool does.
-- GitHub Copilot can activate multiple skills automatically to achieve the user's request.

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

@@ -1,92 +0,0 @@
----
-agent: 'agent'
-description: 'Run UI tests on a website & generate a detailed report.'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems', 'read/terminalLastCommand']
----
-
-Activate the chrome-devtools skill.
-
-## Purpose
-Run comprehensive UI tests on a website and generate a detailed report.
-
-## Arguments
-- $1: URL - The URL of the website to test
-- $2: OPTIONS - Optional test configuration (e.g., --headless, --mobile, --auth)
-
-## Testing Protected Routes (Authentication)
-
-For testing protected routes that require authentication, follow this workflow:
-
-### Step 1: User Manual Login
-Instruct the user to:
-1. Open the target site in their browser
-2. Log in manually with their credentials
-3. Open browser DevTools (F12) → Application tab → Cookies/Storage
-
-### Step 2: Extract Auth Credentials
-Ask the user to provide one of:
-- **Cookies**: Copy cookie values (name, value, domain)
-- **Access Token**: Copy JWT/Bearer token from localStorage or cookies
-- **Session Storage**: Copy relevant session keys
-
-### Step 3: Inject Authentication
-Use the `inject-auth.js` script to inject credentials before testing:
-
-```bash
-cd $SKILL_DIR  # 
-
-# Option A: Inject cookies
-node inject-auth.js --url https://example.com --cookies '[{"name":"session","value":"abc123","domain":".example.com"}]'
-
-# Option B: Inject Bearer token
-node inject-auth.js --url https://example.com --token "Bearer eyJhbGciOi..." --header Authorization --token-key access_token
-
-# Option C: Inject localStorage
-node inject-auth.js --url https://example.com --local-storage '{"auth_token":"xyz","user_id":"123"}'
-
-# Combined (cookies + localStorage)
-node inject-auth.js --url https://example.com --cookies '[{"name":"session","value":"abc"}]' --local-storage '{"user":"data"}'
-```
-
-### Step 4: Run Tests
-After auth injection, the browser session persists. Run tests normally:
-
-```bash
-# Navigate and screenshot protected pages
-node navigate.js --url https://example.com/dashboard
-node screenshot.js --url https://example.com/profile --output profile.png
-
-# The auth session persists until --close true is used
-node screenshot.js --url https://example.com/settings --output settings.png --close true
-```
-
-### Auth Script Options
-- `--cookies '<json>'` - Inject cookies (JSON array)
-- `--token '<token>'` - Inject Bearer token
-- `--token-key '<key>'` - localStorage key for token (default: access_token)
-- `--header '<name>'` - Set HTTP header with token (e.g., Authorization)
-- `--local-storage '<json>'` - Inject localStorage items
-- `--session-storage '<json>'` - Inject sessionStorage items
-- `--reload true` - Reload page after injection
-- `--clear true` - Clear saved auth session
-
-## Workflow
-- All the screenshots should be saved in the same report directory.
-- Browse $URL with the specified $OPTIONS, discover all pages, components, and endpoints.
-- Create a test plan based on the discovered structure
-- Use multiple s or tool calls  to test all pages, forms, navigation, user flows, accessibility, functionalities, usability, responsive layouts, cross-browser compatibility, performance, security, seo, etc.
-- Use `ai-multimodal` to analyze all screenshots and visual elements.
-- Generate a comprehensive report in Markdown format, embedding all screenshots directly in the report.
-- Finally respond to the user with a concise summary of findings and recommendations.
-- Ask if user wants to preview the report with `/preview` .
-
-## Output Requirements
-How to write reports:
-- Format: Use clear, structured Markdown with headers, lists, and code blocks where appropriate
-- Include the test results summary, key findings, and screenshot references
-- **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.
-
-**IMPORTANT**: **Do not** start implementing the fixes.
-**IMPORTANT:** 

package/prompts/ck-use-mcp.prompt.md

@@ -1,27 +0,0 @@
----
-agent: 'agent'
-description: 'Utilize tools of Model Context Protocol (MCP) servers'
-tools: ['search/codebase', 'read/terminalLastCommand']
----
-
-Execute MCP operations via **Gemini CLI** to preserve context budget.
-
-## Execution Steps
-
-1. **Execute task via Gemini CLI** (using stdin pipe for MCP support):
-   ```bash
-   # IMPORTANT: Use stdin piping, NOT -p flag (deprecated, skips MCP init)
-   echo "${input}. Return JSON only per GEMINI.md instructions." | gemini -y -m gemini-2.5-flash
-   ```
-
-2. **Fallback to mcp-manager ** (if Gemini CLI unavailable):
-   - discover and execute tools
-   - If the  got issues with the scripts of `mcp-management` skill, md auto-loaded**: Gemini CLI automatically loads `GEMINI.md` from project root, enforcing JSON-only response format
-- **Parseable output**: Responses are structured JSON: `{"server":"name","tool":"name","success":true,"result":<data>,"error":null}`
-
-## Anti-Pattern (DO NOT USE)
-
-```bash
-# BROKEN - deprecated -p flag skips MCP server connections!
-gemini -y -m gemini-2.5-flash -p "..."
-```

package/prompts/ck-worktree.prompt.md

@@ -1,127 +0,0 @@
----
-agent: 'agent'
-description: 'Create isolated git worktree for parallel development'
-tools: ['search/codebase', 'read/terminalLastCommand']
----
-
-Create an isolated git worktree for parallel feature development.
-
-## Workflow
-
-### Step 1: Get Repository Info
-
-```bash
-node  info --json
-```
-
-**Response fields:**
-- `repoType`: "monorepo" or "standalone"
-- `baseBranch`: detected base branch
-- `projects`: array of {name, path} for monorepo
-- `envFiles`: array of .env* files found
-- `dirtyState`: boolean
-
-### Step 2: Gather Info
-
-**Detect branch prefix from user's description:**
-- Keywords "fix", "bug", "error", "issue" → prefix = `fix`
-- Keywords "refactor", "restructure", "rewrite" → prefix = `refactor`
-- Keywords "docs", "documentation", "readme" → prefix = `docs`
-- Keywords "test", "spec", "coverage" → prefix = `test`
-- Keywords "chore", "cleanup", "deps" → prefix = `chore`
-- Keywords "perf", "performance", "optimize" → prefix = `perf`
-- Everything else → prefix = `feat`
-
-**For MONOREPO:** Ask user if project not specified:
-```javascript
-// If user said "/worktree add auth" but multiple projects exist
-// Ask user with questions like:
-  questions: [{
-    header: "Project",
-    question: "Which project should the worktree be created for?",
-    options: projects.map(p => ({ label: p.name, description: p.path })),
-    multiSelect: false
-  }]
-})
-```
-
-**For env files:** Always ask which to copy:
-```javascript
-// Ask user with questions like:
-  questions: [{
-    header: "Env files",
-    question: "Which environment files should be copied to the worktree?",
-    options: envFiles.map(f => ({ label: f, description: "Copy to worktree" })),
-    multiSelect: true
-  }]
-})
-```
-
-### Step 3: Convert Description to Slug
-
-- "add authentication system" → `add-auth`
-- "fix login bug" → `login-bug`
-- Remove filler words, kebab-case, max 50 chars
-
-### Step 4: Execute Command
-
-**Monorepo:**
-```bash
-node  create "<PROJECT>" "<SLUG>" --prefix <TYPE> --env "<FILES>"
-```
-
-**Standalone:**
-```bash
-node  create "<SLUG>" --prefix <TYPE> --env "<FILES>"
-```
-
-**Options:**
-- `--prefix` - Branch type: feat|fix|refactor|docs|test|chore|perf
-- `--env` - Comma-separated .env files to copy
-- `--json` - Output JSON for parsing
-- `--dry-run` - Preview without executing
-
-## Commands
-
-| Command | Usage | Description |
-|---------|-------|-------------|
-| `create` | `create [project] <feature>` | Create new worktree |
-| `remove` | `remove <name-or-path>` | Remove worktree and branch |
-| `info` | `info` | Get repo info |
-| `list` | `list` | List existing worktrees |
-
-## Error Codes
-
-| Code | Meaning | Action |
-|------|---------|--------|
-| `MISSING_ARGS` | Missing project/feature for monorepo | Ask for both |
-| `MISSING_FEATURE` | No feature name (standalone) | Ask for feature |
-| `PROJECT_NOT_FOUND` | Project not in .gitmodules | Show available projects |
-| `MULTIPLE_PROJECTS_MATCH` | Ambiguous project name | Ask user |
-| `MULTIPLE_WORKTREES_MATCH` | Ambiguous worktree for remove | Ask user |
-| `BRANCH_CHECKED_OUT` | Branch in use elsewhere | Suggest different name |
-| `WORKTREE_EXISTS` | Path already exists | Suggest use or remove |
-| `WORKTREE_CREATE_FAILED` | Git command failed | Show git error |
-| `WORKTREE_REMOVE_FAILED` | Cannot remove worktree | Check uncommitted changes |
-
-## Example Session
-
-```
-User: /worktree fix the login validation bug
-
-Claude: [Runs: node  info --json]
-        [Detects: standalone repo, envFiles: [".env.example"]]
-        [Detects prefix from "fix" keyword: fix]
-        [Converts slug: "login-validation-bug"]
-
-Claude: [Asks user for env files]
-        "Which environment files should be copied?"
-        Options: .env.example
-
-User: .env.example
-
-Claude: [Runs: node  create "login-validation-bug" --prefix fix --env ".env.example"]
-
-Output: Worktree created at ../worktrees/myrepo-login-validation-bug
-        Branch: fix/login-validation-bug
-```