cokit-cli 1.0.7 → 1.0.9

package/docs/copilot-processing-flow.md

@@ -1,128 +1,212 @@
-# Copilot Processing Flow
-
-How Copilot processes user input through resources to produce output.
-
-> **Flow diagrams:** See [README.FLOW.md](README.FLOW.md) for visual diagrams.
-
----
-
-## Resource Types Overview
-
-| Resource | Trigger | Purpose | File |
-|----------|---------|---------|------|
-| **Prompt** | User calls `/prompt-name` | Workflow/task template | `*.prompt.md` |
-| **Agent** | Referenced by prompt | Execute specific tasks | `*.agent.md` |
-| **Instruction** | Auto (by file pattern) | Coding rules/standards | `*.instructions.md` |
-| **Skill** | User/Agent activates | Specialized knowledge | `skills/*/SKILL.md` |
-| **Collection** | User selects | Bundle related resources | `*.collection.yml` |
-
----
-
-## Component Details
-
-### 1. Prompt (`*.prompt.md`)
-
-**Role:** Entry point - Defines workflow/task
-
-```yaml
----
-mode: agent                    # Mode: agent, ask, edit
-description: 'Task description'
-tools: ['search/codebase']     # Allowed tools
----
-
-# Prompt content
-Your task is: ${input}
-Follow these steps...
-```
-
-**When to use:** User wants to execute a specific task
-
----
-
-### 2. Agent (`*.agent.md`)
-
-**Role:** Executor - Executes tasks per prompt
-
-```yaml
----
-description: 'Agent specialization'
-model: GPT-4.1
-tools: ['codebase', 'terminal']
----
-
-# Agent persona & capabilities
-You are a code reviewer...
-```
-
-**When to use:** Referenced by prompt, not called directly
-
----
-
-### 3. Instruction (`*.instructions.md`)
-
-**Role:** Rules - Auto-applied coding standards
-
-```yaml
----
-applyTo: '**/*.tsx'            # Glob pattern
-description: 'React rules'
----
-
-# Rules for React files
-- Use functional components
-- Props interface required
-```
-
-**When to use:** Auto-applied when editing files matching pattern
-
----
-
-### 4. Skill (`skills/*/SKILL.md`)
-
-**Role:** Knowledge - Deep specialized expertise
-
-```
-skills/
-└── frontend-design/
-    ├── SKILL.md              # Main instructions
-    ├── templates/            # Code templates
-    └── examples/             # Reference examples
-```
-
-**When to use:** Activated when specific expertise needed
-
----
-
-### 5. Collection (`*.collection.yml`)
-
-**Role:** Bundle - Groups related resources
-
-```yaml
-id: web-development
-name: Web Development Kit
-items:
-  - path: agents/frontend.agent.md
-  - path: prompts/ck-design.prompt.md
-  - path: skills/react/
-```
-
-**When to use:** Install/share resource bundles by topic
-
----
-
-## Quick Reference
-
-| Resource | Trigger | Scope | Persistence | Purpose |
-|----------|---------|-------|-------------|---------|
-| Prompt | `/prompt-name` | Single task | Per invocation | Workflow |
-| Agent | Prompt refs | Task exec | Per invocation | Execution |
-| Instruction | Auto (glob) | File-based | Always active | Rules/Style |
-| Skill | On-demand | Knowledge | When activated | Expertise |
-| Collection | User install | Resource set | Permanent | Bundling |
-
----
-
-## One-liner
-
-> User calls **Prompt** → Prompt uses **Agent** → Agent auto-receives **Instructions** by file pattern → Agent activates **Skills** when needed → All can be bundled in **Collection**.
+# Copilot Processing Flow
+
+How Copilot processes user input through CoKit resources to produce output.
+
+> **CoKit Resources:** See [README.md](../README.md) for complete resource listing.
+
+---
+
+## CoKit Resource Types Overview
+
+| Resource | Trigger | Purpose | File |
+|----------|---------|---------|------|
+| **Prompt** | User calls `/ck-prompt-name` | Workflow/task template | `prompts/ck-*.prompt.md` |
+| **Agent** | Referenced by prompt | Execute specific tasks | `agents/*.agent.md` |
+| **Instruction** | Auto (by file pattern) | Coding rules/standards | `instructions/ck-*.instructions.md` |
+| **Skill** | Auto by context | Specialized knowledge | `skills/ck-*/SKILL.md` |
+| **Collection** | User selects | Bundle related resources | `collections/ck-*.collection.yml` |
+
+### CoKit Examples
+
+**Prompts:** `/ck-fix`, `/ck-plan`, `/ck-code`, `/ck-cook`, `/ck-test`, `/ck-review-codebase`, `/ck-docs`, `/ck-bootstrap`, `/ck-brainstorm`, `/ck-debug`, `/ck-scout`, `/ck-ask`, `/ck-git`, `/ck-ck-help`
+
+**Agents:** planner, code-reviewer, debugger, tester, researcher, scout, git-manager, brainstormer, docs-manager
+
+**Skills:** ck-debugging, ck-code-review, ck-planning, ck-problem-solving, ck-sequential-thinking, ck-backend-development, ck-frontend-development
+
+**Instructions:** ck-backend, ck-frontend, ck-testing, ck-development, ck-research
+
+**Collections:** ck-core, ck-development-rules, ck-documentation, ck-git-workflow, ck-orchestration
+
+---
+
+## Component Details
+
+### 1. Prompt (`prompts/ck-*.prompt.md`)
+
+**Role:** Entry point - Defines workflow/task
+
+**Example: ck-fix.prompt.md**
+```yaml
+---
+mode: agent
+description: 'Debug and fix issues systematically'
+---
+
+# Fix Issues
+
+You are debugging an issue. Follow systematic troubleshooting...
+
+1. Read the error message
+2. Search for root cause
+3. Implement fix
+4. Test the solution
+```
+
+**CoKit Examples:**
+- `/ck-fix` - Debug and fix
+- `/ck-plan` - Create implementation plan
+- `/ck-cook` - Step-by-step feature implementation
+- `/ck-review-codebase` - Scan and analyze code
+
+**When to use:** User wants to execute a specific workflow
+
+---
+
+### 2. Agent (`agents/*.agent.md`)
+
+**Role:** Executor - Specialized persona for specific tasks
+
+**Example: planner.agent.md**
+```yaml
+---
+description: 'Research, analyze, and create implementation plans'
+---
+
+# Planner Agent
+
+You are a research-first planner...
+- Conduct comprehensive research
+- Design system architecture
+- Create detailed implementation plans
+```
+
+**CoKit Agents:**
+- `planner` - Creates implementation plans
+- `code-reviewer` - Provides comprehensive code review
+- `debugger` - Investigates and diagnoses issues
+- `tester` - Writes and validates tests
+- `researcher` - Finds and synthesizes documentation
+- `scout` - Locates files in codebase
+- `git-manager` - Handles commits and workflows
+- `brainstormer` - Ideates solutions
+- `docs-manager` - Creates and updates documentation
+
+**When to use:** Referenced by prompts to specialize execution
+
+---
+
+### 3. Instruction (`instructions/ck-*.instructions.md`)
+
+**Role:** Rules - Auto-applied coding standards
+
+**Example: ck-frontend.instructions.md**
+```yaml
+---
+applyTo: '**/*.tsx, **/*.jsx, components/**'
+description: 'Frontend component guidelines'
+---
+
+# Frontend Guidelines
+
+When editing React files:
+- Use functional components
+- Props interface required
+- Use hooks instead of class methods
+```
+
+**CoKit Instructions:**
+- `ck-backend` - Backend patterns (Node.js, Python, Go, Rust)
+- `ck-frontend` - Frontend patterns (React, TypeScript)
+- `ck-testing` - Testing standards and patterns
+- `ck-development` - YAGNI/KISS/DRY principles
+- `ck-research` - Research methodology guidelines
+
+**When to use:** Auto-applied based on file patterns while editing
+
+---
+
+### 4. Skill (`skills/ck-*/SKILL.md`)
+
+**Role:** Knowledge - Deep specialized expertise with supporting resources
+
+**Example: ck-debugging/SKILL.md**
+```
+skills/ck-debugging/
+├── SKILL.md                  # Main methodology
+├── references/               # Case studies, patterns
+└── examples/                 # Real debugging examples
+```
+
+**CoKit Skills:**
+- `ck-debugging` - Systematic root cause analysis
+- `ck-code-review` - Comprehensive review gates
+- `ck-planning` - Research → design → implementation
+- `ck-problem-solving` - Complexity spirals, innovation blocks
+- `ck-sequential-thinking` - Multi-step problem solving
+- `ck-backend-development` - Backend framework patterns
+- `ck-frontend-development` - Frontend framework patterns
+
+**When to use:** Activated automatically based on task context
+
+---
+
+### 5. Collection (`collections/ck-*.collection.yml`)
+
+**Role:** Bundle - Groups related resources by workflow
+
+**Example: ck-core.collection.yml**
+```yaml
+id: ck-core
+name: CoKit Core Workflows
+description: Essential agents, prompts, and skills
+items:
+  - path: agents/planner.agent.md
+  - path: agents/code-reviewer.agent.md
+  - path: prompts/ck-plan.prompt.md
+  - path: prompts/ck-code.prompt.md
+  - path: skills/ck-planning/
+```
+
+**CoKit Collections:**
+- `ck-core` - Core workflows for full-stack development
+- `ck-development-rules` - YAGNI/KISS/DRY principles
+- `ck-documentation` - Documentation management workflows
+- `ck-git-workflow` - Git commit, push, merge workflows
+- `ck-orchestration` - Task delegation and workflow orchestration
+
+**When to use:** Install/share resource bundles for specific workflows
+
+---
+
+## Quick Reference
+
+| Resource | Trigger | Scope | Persistence | Purpose |
+|----------|---------|-------|-------------|---------|
+| Prompt | `/prompt-name` | Single task | Per invocation | Workflow |
+| Agent | Prompt refs | Task exec | Per invocation | Execution |
+| Instruction | Auto (glob) | File-based | Always active | Rules/Style |
+| Skill | On-demand | Knowledge | When activated | Expertise |
+| Collection | User install | Resource set | Permanent | Bundling |
+
+---
+
+## CoKit Processing Example
+
+```
+User types: /ck-fix
+    ↓
+Prompt (ck-fix.prompt.md) activates
+    ↓
+Agent (debugger.agent.md) executes
+    ↓
+Instructions (ck-*.instructions.md) auto-apply by file pattern
+    ↓
+Skills (ck-debugging, etc.) activate by context
+    ↓
+Output: Systematic debugging solution
+```
+
+## One-liner
+
+> User calls **Prompt** (e.g., `/ck-fix`) → Prompt references **Agent** (e.g., `debugger`) → Agent auto-receives **Instructions** by file pattern → Agent activates **Skills** when needed → All can be bundled in **Collection** (e.g., `ck-core`).

package/docs/migration-guide.md

@@ -1,120 +1,133 @@
-# Migration Guide: Claude Code to CoKit
-
-This guide helps Claude Code users adapt to GitHub Copilot with CoKit.
-
-## Key Differences
-
-| Feature | Claude Code | CoKit/Copilot |
-|---------|-------------|---------------|
-| Commands | `/fix:types`, `/plan:auto` | `/ck-fix`, `/ck-plan` |
-| Arguments | `$ARGUMENTS` variable | User provides in chat |
-| Subagents | Task tool with agents | Single Copilot agent |
-| Hooks | Pre/post execution | Not supported |
-| Skills | `~/.claude/skills/` | `~/.copilot/skills/ck-*/` |
-| Prompts | `~/.claude/commands/` | `.github/prompts/ck-*.prompt.md` |
-
-## What's Different
-
-### No Sub-Commands
-
-**Claude Code:**
-```
-/fix:types     # Fix type errors
-/fix:tests     # Fix test failures
-```
-
-**Copilot:**
-```
-/ck-fix the type errors in auth.ts
-/ck-fix the failing tests in user.test.ts
-```
-
-Provide context directly in your message.
-
-### No $ARGUMENTS Variable
-
-**Claude Code prompt:**
-```markdown
-Fix the issue: $ARGUMENTS
-```
-
-**Copilot prompt:**
-```markdown
-Fix the issue described by the user.
-```
-
-Users describe the issue in chat naturally.
-
-### No Subagent Delegation
-
-**Claude Code:**
-```
-Use Task tool to launch tester agent
-```
-
-**Copilot:**
-```
-Run tests and analyze results
-```
-
-Copilot handles everything in one agent.
-
-### No Hooks
-
-Claude Code hooks (pre/post commands) don't exist in Copilot.
-
-**Workaround:** Include instructions in the prompt itself:
-```markdown
-Before fixing:
-1. Read the error message
-2. Find the root cause
-
-After fixing:
-1. Run tests
-2. Verify the fix works
-```
-
-## Mapping Claude Skills to CoKit
-
-| Claude Skill | CoKit Skill | Notes |
-|--------------|-------------|-------|
-| debugging | ck-debugging | Same methodology |
-| code-review | ck-code-review | Same principles |
-| planning | ck-planning | Simplified workflow |
-| docs-seeker | ck-docs-seeker | Same search patterns |
-| sequential-thinking | ck-sequential-thinking | Same approach |
-
-## What Works the Same
-
-- **Core methodology** - Debugging, planning, review processes
-- **YAGNI/KISS/DRY** - Same principles apply
-- **Quality standards** - Same expectations
-- **File structure** - Similar organization
-
-## Quick Migration
-
-1. Install CoKit:
-   ```bash
-   npx cokit init --all
-   ```
-
-2. Use prompts directly:
-   ```
-   /ck-fix (describe your issue)
-   /ck-plan (describe your feature)
-   ```
-
-3. Skills work automatically - no changes needed.
-
-## Tips for Claude Users
-
-1. **Be descriptive** - Without $ARGUMENTS, include context in chat
-2. **One step at a time** - No multi-agent orchestration
-3. **Explicit instructions** - Put everything in the prompt
-4. **Manual verification** - No automatic hooks
-
-## Getting Help
-
-- [FAQ](../FAQ.md) - Common questions
-- [README](../README.md) - Full documentation
-- Run `npx cokit doctor` for setup issues
+# Migration Guide: Claude Code to CoKit
+
+This guide helps Claude Code users adapt to GitHub Copilot with CoKit.
+
+## Key Differences
+
+| Feature | Claude Code | CoKit/Copilot |
+|---------|-------------|---------------|
+| Commands | `/fix:types`, `/plan:auto` | `/ck-fix`, `/ck-plan`, `/ck-cook`, etc. |
+| Arguments | `$ARGUMENTS` variable | User provides in chat |
+| Subagents | Task tool delegates to agents | Referenced in prompts |
+| Hooks | Pre/post execution | Not supported |
+| Skills | `~/.claude/skills/` | `~/.copilot/skills/ck-*/` |
+| Prompts | `~/.claude/commands/` | `.github/prompts/ck-*.prompt.md` |
+| Instructions | `.claude/instructions/` | `.github/instructions/ck-*.instructions.md` |
+| Collections | Manual management | `.github/collections/ck-*.collection.yml` |
+
+## What's Different
+
+### No Sub-Commands
+
+**Claude Code:**
+```
+/fix:types     # Fix type errors
+/fix:tests     # Fix test failures
+```
+
+**Copilot:**
+```
+/ck-fix the type errors in auth.ts
+/ck-fix the failing tests in user.test.ts
+```
+
+Provide context directly in your message.
+
+### No $ARGUMENTS Variable
+
+**Claude Code prompt:**
+```markdown
+Fix the issue: $ARGUMENTS
+```
+
+**Copilot prompt:**
+```markdown
+Fix the issue described by the user.
+```
+
+Users describe the issue in chat naturally.
+
+### No Subagent Delegation
+
+**Claude Code:**
+```
+Use Task tool to launch tester agent
+```
+
+**Copilot:**
+```
+Run tests and analyze results
+```
+
+Copilot handles everything in one agent.
+
+### No Hooks
+
+Claude Code hooks (pre/post commands) don't exist in Copilot.
+
+**Workaround:** Include instructions in the prompt itself:
+```markdown
+Before fixing:
+1. Read the error message
+2. Find the root cause
+
+After fixing:
+1. Run tests
+2. Verify the fix works
+```
+
+## Mapping Claude Skills & Agents to CoKit
+
+| Claude Feature | CoKit Equivalent | Notes |
+|---|---|---|
+| debugging skill | ck-debugging + debugger agent | Same root cause methodology |
+| code-review skill | ck-code-review + code-reviewer agent | Same verification principles |
+| planning skill | ck-planning + planner agent | Structured workflow |
+| docs-seeker skill | researcher agent | Documentation discovery |
+| sequential-thinking skill | ck-sequential-thinking | Same step-by-step approach |
+| N/A | ck-backend-development | NEW: Backend patterns |
+| N/A | ck-frontend-development | NEW: Frontend patterns |
+| N/A | ck-problem-solving | NEW: Systematic solutions |
+| N/A | tester agent | NEW: Test validation |
+| N/A | scout agent | NEW: Codebase navigation |
+
+## What Works the Same
+
+- **Core methodology** - Debugging, planning, review processes
+- **YAGNI/KISS/DRY** - Same principles apply
+- **Quality standards** - Same expectations
+- **File structure** - Similar organization
+
+## Quick Migration
+
+1. Install CoKit:
+   ```bash
+   npx cokit-cli init -a
+   ```
+
+2. Use prompts directly:
+   ```
+   /ck-fix (describe your issue)
+   /ck-plan (describe your feature)
+   /ck-cook (implement a feature)
+   /ck-bootstrap (setup new project)
+   ```
+
+3. Skills and agents work automatically:
+   - Agents are referenced by prompts
+   - Skills auto-activate based on context
+
+## Tips for Claude Users
+
+1. **Be descriptive** - Without $ARGUMENTS, include context in chat
+2. **Use specialized prompts** - `/ck-cook` for implementation, `/ck-bootstrap` for setup
+3. **Explicit instructions** - Put everything in the prompt
+4. **Manual verification** - No automatic hooks
+5. **Chain workflows** - Use `/ck-plan` → `/ck-code` → `/ck-test` → `/ck-review-codebase`
+
+## Getting Help
+
+- [README](../README.md) - Full documentation
+- [Team Presentation](./cokit-team-presentation.md) - Detailed overview
+- Run `npx cokit-cli doctor` for setup issues
+- Check [Project Roadmap](./project-roadmap.md) for version history