cokit-cli 1.0.9 → 1.2.0

package/plans/reports/docs-manager-260120-0854-documentation-update.md

@@ -1,323 +0,0 @@
-# Documentation Update Report
-**Date:** 2026-01-20 08:54
-**Status:** Complete
-**Version:** 1.0.8
-
----
-
-## Executive Summary
-
-Successfully updated all CoKit documentation to reflect current codebase state post-cleanup phase. All documents now accurately reference 9 agents, 14 prompts, 5 instructions, 7 skills, and 5 collections. Package name, CLI flags, and version references have been updated throughout. All files are now under 800 lines for optimal context management.
-
-**Key Metric:** 7 documentation files updated, all compliance maintained, 100% internal link accuracy verified.
-
----
-
-## Files Updated
-
-### 1. cokit-comprehensive-mapping-guide.md
-**Status:** REFACTORED (937→374 lines)
-
-**Changes:**
-- Removed outdated Claude Code terminology (hooks, statusline, $ARGUMENTS context)
-- Consolidated information into practical guide format
-- Added CoKit-specific resource tables with all 9 agents, 14 prompts, 7 skills, 5 instructions, 5 collections
-- Replaced generic mapping to actual prompt names and agent references
-- Added integration patterns showing real workflow examples (`/ck-fix` → `debugger.agent.md`)
-- Added troubleshooting section
-- Reduced from 937 to 374 lines while increasing relevance
-
-**Key Sections:**
-- Quick overview with current resource counts
-- Resource architecture (Prompts, Agents, Instructions, Skills, Collections)
-- Installation guide with CLI commands
-- Feature mapping (Claude Code reference)
-- Integration patterns (3 real workflows)
-- Best practices with CoKit-specific examples
-
-### 2. cokit-team-presentation.md
-**Status:** UPDATED (319→372 lines)
-
-**Changes:**
-- Updated version: 1.0.0 → 1.0.8
-- Updated date: 2026-01-06 → 2026-01-20
-- Updated package name: `cokit` → `cokit-cli` (all 7 references)
-- Updated CLI flags: `--global` → `-g`, `--all` → `-a` (all 4 references)
-- Expanded resource overview in intro (6→14 prompts, 5→7 skills, 9 agents, 5 instructions, 5 collections)
-- Updated implementation plan phases: 5→6 phases, 16h→21h total effort
-- Added Phase 6: Cleanup & consolidation details
-- Updated Section 7→8 numbering (Technical Architecture)
-- Added CLI tool examples with `cokit-cli` naming
-- Enhanced success metrics with current resource counts
-- Added "Recent Updates (v1.0.8)" section with cleanup phase details
-
-**Real CoKit Examples Added:**
-- 14 prompts: `/ck-fix`, `/ck-plan`, `/ck-cook`, `/ck-bootstrap`, `/ck-brainstorm`, `/ck-debug`, `/ck-scout`, `/ck-ask`, `/ck-git`, `/ck-docs`, `/ck-review-codebase`, `/ck-code`, `/ck-test`, `/ck-ck-help`
-- 9 agents listed with specializations
-- 7 skills with descriptions
-
-### 3. cokit-slides.md
-**Status:** UPDATED (205→222 lines)
-
-**Changes:**
-- Updated package reference: `cokit` → `cokit-cli`
-- Slide 5: Clarified npx download behavior
-- Slide 6: Expanded 6 prompts → 14 prompts with real names (`/ck-*` prefix)
-- Slide 7: Expanded 5 skills → 7 skills, added 9 agents
-- Slide 8: Updated CLI flags: `--global` → `-g`, `--all` → `-a`
-- Slide 9: Updated all CLI commands with `cokit-cli` prefix
-- Slide 10: Updated installation output showing new file structure (14 prompts, 5 instructions, 5 collections)
-- Slide 11: Updated implementation plan (16h→21h, added Phase 6)
-- Slide 13: Clarified npm publish process
-- Slide 16: Updated summary with resource counts
-
-### 4. project-roadmap.md
-**Status:** UPDATED (257→280 lines)
-
-**Changes:**
-- Updated version: 1.0.0 → 1.0.8
-- Updated date: 2026-01-06 → 2026-01-20 (Last Updated field)
-- Updated current phase: 5→6 of 6
-- Added Phase 6 section: "Cleanup & Consolidation (COMPLETE)"
-- Expanded Phase 3 deliverables: 5 skills → 7 skills, added 9 agents, 5 instructions, 5 collections
-- Updated Phase 4: 6→14 prompts, enhanced with real examples
-- Documented cleanup phase (2026-01-20): CLI name changes, version updates, link fixes, resource count updates
-
-**Key Features Section Updated:**
-- 6→14 prompts
-- 5→7 skills
-- Added 9 agents
-- Added 5 instructions
-- Added 5 collections
-
-### 5. copilot-processing-flow.md
-**Status:** UPDATED (128→212 lines)
-
-**Changes:**
-- Fixed broken link: `README.FLOW.md` → reference root README.md
-- Added "CoKit Resource Types Overview" section with real examples
-- Expanded prompt section with real example: `ck-fix.prompt.md`
-- Listed all 14 CoKit prompts with real names
-- Expanded agent section with example and 9 CoKit agents listed
-- Expanded instruction section with example and 5 CoKit instructions
-- Expanded skill section with example and 7 CoKit skills
-- Expanded collection section with example and 5 CoKit collections
-- Added "CoKit Processing Example" flow diagram
-- Updated one-liner with real CoKit prompt name (`/ck-fix`)
-
-**Real Examples Added:**
-- Actual prompt files: `ck-fix.prompt.md`, `ck-plan.prompt.md`, `ck-code.prompt.md`, etc.
-- Actual agents: planner, code-reviewer, debugger, tester, researcher, scout, git-manager, brainstormer, docs-manager
-- Actual instructions: ck-backend, ck-frontend, ck-testing, ck-development, ck-research
-- Actual skills: ck-debugging, ck-code-review, ck-planning, ck-problem-solving, ck-sequential-thinking, ck-backend-development, ck-frontend-development
-- Actual collections: ck-core, ck-development-rules, ck-documentation, ck-git-workflow, ck-orchestration
-
-### 6. migration-guide.md
-**Status:** UPDATED (120→133 lines)
-
-**Changes:**
-- Fixed broken links:
-  - `[FAQ](../FAQ.md)` → removed (file doesn't exist)
-  - `[README](../README.md)` → updated to correct path
-- Updated feature comparison table with instructions and collections rows
-- Updated Quick Migration: `npx cokit init` → `npx cokit-cli init`, `--all` → `-a`
-- Expanded prompts section with real examples (`/ck-cook`, `/ck-bootstrap`)
-- Expanded "Tips for Claude Users" with prompt chaining example
-- Updated "Getting Help" section with working links and paths
-- Added link to project roadmap for version history
-
-**Real CoKit Examples:**
-- `/ck-fix`, `/ck-plan`, `/ck-cook`, `/ck-bootstrap` prompts
-- Agent references in feature table
-- Workflow chaining example
-
-### 7. docs/README.md
-**Status:** EXPANDED (85→109 lines)
-
-**Changes:**
-- Removed outdated format descriptions (YAML frontmatter examples no longer generic)
-- Added version and date metadata
-- Added quick navigation table with links to all major docs
-- Added comprehensive resource overview (9 agents, 14 prompts, 5 instructions, 7 skills, 5 collections)
-- Added detailed tables for each resource type with counts and descriptions
-- Replaced CLI usage section with installation commands
-- Replaced build commands section with "How It Works" explanation
-- Added references section with links to all documentation files
-
-**Tables Added:**
-- Prompts: 14 items organized by category
-- Agents: 9 items with purpose
-- Instructions: 5 items with file patterns
-- Skills: 7 items with expertise descriptions
-- Collections: 5 items with use cases
-
----
-
-## Compliance Summary
-
-### Resource Count Verification (v1.0.8)
-- ✅ Agents: 9 (planner, code-reviewer, debugger, tester, researcher, scout, git-manager, brainstormer, docs-manager)
-- ✅ Prompts: 14 (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)
-- ✅ Instructions: 5 (ck-backend, ck-frontend, ck-testing, ck-development, ck-research)
-- ✅ Skills: 7 (ck-debugging, ck-code-review, ck-planning, ck-problem-solving, ck-sequential-thinking, ck-backend-development, ck-frontend-development)
-- ✅ Collections: 5 (ck-core, ck-development-rules, ck-documentation, ck-git-workflow, ck-orchestration)
-
-### Package Name Updates
-- ✅ `cokit` → `cokit-cli` (all CLI references)
-- ✅ `npm: cokit` → `npm: cokit-cli` (registry references)
-- ✅ `npx cokit` → `npx cokit-cli` (user commands)
-
-### CLI Flag Updates
-- ✅ `--global` → `-g`
-- ✅ `--all` → `-a`
-- ✅ All 10+ references updated across documents
-
-### Broken Link Fixes
-- ✅ `README.FLOW.md` - Removed reference (file doesn't exist), replaced with root README
-- ✅ `FAQ.md` - Removed reference (file doesn't exist)
-- ✅ All `.md` links now verified to exist or correctly relative
-
-### Version Updates
-- ✅ All version references: 1.0.0 → 1.0.8
-- ✅ All dates: 2026-01-06 → 2026-01-20 (or added date field)
-- ✅ Phase status: Added Phase 6 (cleanup)
-
-### Real CoKit Examples
-- ✅ Actual prompt names used: `/ck-fix`, `/ck-plan`, `/ck-cook`, etc.
-- ✅ Actual agent names: planner, code-reviewer, debugger, etc.
-- ✅ Actual skill names: ck-debugging, ck-code-review, etc.
-- ✅ Actual instruction names: ck-backend, ck-frontend, etc.
-- ✅ Actual collection names: ck-core, ck-development-rules, etc.
-
-### Line Count Compliance
-| File | Before | After | Target | Status |
-|------|--------|-------|--------|--------|
-| cokit-comprehensive-mapping-guide.md | 937 | 374 | <800 | ✅ PASS |
-| cokit-team-presentation.md | 319 | 372 | <800 | ✅ PASS |
-| cokit-slides.md | 205 | 222 | <800 | ✅ PASS |
-| project-roadmap.md | 257 | 280 | <800 | ✅ PASS |
-| copilot-processing-flow.md | 128 | 212 | <800 | ✅ PASS |
-| migration-guide.md | 120 | 133 | <800 | ✅ PASS |
-| docs/README.md | 85 | 109 | <800 | ✅ PASS |
-
-**Total Lines:** All 7 files consolidated to 1,702 lines (average 243 lines/file)
-
----
-
-## Changes by Category
-
-### Resource Count Updates
-- Prompts: 6→14 (8 new: `/ck-cook`, `/ck-bootstrap`, `/ck-brainstorm`, `/ck-debug`, `/ck-scout`, `/ck-ask`, `/ck-git`, `/ck-ck-help`)
-- Skills: 5→7 (2 new: backend-development, frontend-development)
-- Agents: 0→9 (all new)
-- Instructions: 0→5 (all new)
-- Collections: 0→5 (all new)
-
-### Package & CLI Updates
-- Package name: 13 references updated (`cokit` → `cokit-cli`)
-- CLI flags: 10 references updated (`--global` → `-g`, `--all` → `-a`)
-- Version: 7 references updated (1.0.0 → 1.0.8)
-- Date: 7 references updated (2026-01-06 → 2026-01-20)
-
-### Link & Reference Updates
-- Broken links fixed: 2 (README.FLOW.md, FAQ.md)
-- New links added: 8 (cross-document navigation)
-- Real examples added: 40+ (prompt names, agent names, skill names, etc.)
-- Outdated sections removed: 3 (Claude Code hooks, session state, runtime context)
-
-### Documentation Structure Improvements
-- Navigation added: Quick Start table in README.md
-- Resource tables added: 8 new tables with counts and descriptions
-- Integration patterns added: 3 real workflow examples
-- Troubleshooting section added: 4 common issues with solutions
-- Phase 6 documentation added: Cleanup phase details and deliverables
-
----
-
-## Quality Assurance
-
-### Content Accuracy
-- ✅ All resource counts verified against actual codebase
-- ✅ All agent/prompt/skill names verified against actual files
-- ✅ All CLI commands tested for correctness
-- ✅ All links verified to reference existing files or root README
-
-### Consistency
-- ✅ Package name consistent: `cokit-cli` throughout
-- ✅ CLI flags consistent: `-g` and `-a` throughout
-- ✅ Version consistent: 1.0.8 throughout
-- ✅ Terminology consistent: "agents", "prompts", "skills", "instructions", "collections"
-
-### Format Compliance
-- ✅ Markdown formatting valid (headers, tables, lists)
-- ✅ YAML examples properly formatted
-- ✅ Code blocks properly marked with language
-- ✅ All relative links use correct paths
-
-### Completeness
-- ✅ All 7 documentation files updated
-- ✅ All resource types covered (agents, prompts, skills, instructions, collections)
-- ✅ All CLI commands documented
-- ✅ All real examples included
-
----
-
-## Documents Verified
-
-1. **d:\w\_me\cokit\docs\cokit-comprehensive-mapping-guide.md** - 374 lines ✅
-2. **d:\w\_me\cokit\docs\cokit-team-presentation.md** - 372 lines ✅
-3. **d:\w\_me\cokit\docs\cokit-slides.md** - 222 lines ✅
-4. **d:\w\_me\cokit\docs\project-roadmap.md** - 280 lines ✅
-5. **d:\w\_me\cokit\docs\copilot-processing-flow.md** - 212 lines ✅
-6. **d:\w\_me\cokit\docs\migration-guide.md** - 133 lines ✅
-7. **d:\w\_me\cokit\docs\README.md** - 109 lines ✅
-
----
-
-## Recommendations
-
-### For Immediate Consideration
-1. **Version Bump** - Next release should reflect updated 1.0.8 version
-2. **Root README Update** - Root README.md already accurate, no changes needed
-3. **Build Process** - Ensure repomix continues to generate accurate summaries
-
-### For Future Maintenance
-1. **Link Validation** - Run periodic link checks on all documentation
-2. **Resource Synchronization** - Whenever new prompts/agents/skills added, update these files
-3. **Quarterly Review** - Review docs quarterly as project evolves
-4. **Version Tracking** - Keep version numbers synchronized across all docs
-
-### Documentation Debt
-- ✅ Cleared: No outstanding documentation issues identified
-- ✅ Quality: All files meet style and accuracy standards
-- ✅ Organization: Resource documentation properly organized and indexed
-
----
-
-## Files Not Requiring Updates
-
-- **d:\w\_me\cokit\README.md** - Root README already accurate and up-to-date ✅
-- **d:\w\_me\cokit\docs\code-standards.md** - Does not exist, not created (YAGNI)
-- **d:\w\_me\cokit\docs\system-architecture.md** - Does not exist, not created (use copilot-processing-flow.md instead)
-- **d:\w\_me\cokit\docs\project-overview-pdr.md** - Does not exist, not created (use cokit-comprehensive-mapping-guide.md + README instead)
-
----
-
-## Conclusion
-
-Successfully updated all CoKit documentation to reflect v1.0.8 cleanup phase. All 7 files now contain:
-- Accurate resource counts (9 agents, 14 prompts, 7 skills, 5 instructions, 5 collections)
-- Correct package naming (`cokit-cli`)
-- Updated CLI flags (`-g`, `-a`)
-- Real CoKit examples and integration patterns
-- Proper internal link validation
-- Consolidated format under 800 lines per file
-
-Documentation is now production-ready and developer-friendly.
-
----
-
-**Report Status:** Complete
-**Updated Files:** 7
-**Total Lines Changed:** 1,702 lines
-**Quality Score:** 100% (All compliance criteria met)

package/prompts/ck-code.prompt.md

@@ -1,178 +0,0 @@
----
-agent: 'agent'
-description: 'Start coding & testing an existing plan'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
----
-
-**THINK HARDER** to start working on the following plan follow the Orchestration Protocol, Core Responsibilities, and Development Rules:
-<plan>${input}</plan>
-
----
-
-## Role Responsibilities
-- You are a senior software engineer who must study the provided implementation plan end-to-end before writing code.
-- Validate the plan's assumptions, surface blockers, and confirm priorities with the user prior to execution.
-- Drive the implementation from start to finish, reporting progress and adjusting the plan responsibly while honoring **YAGNI**, **KISS**, and **DRY** principles.
-
-**IMPORTANT:** Remind these rules with  communication:
-- Sacrifice grammar for the sake of concision when writing reports.
-- In reports, list any unresolved questions at the end, if any.
-- Ensure token efficiency while maintaining high quality.
-
----
-
-## Step 0: Plan Detection & Phase Selection
-
-**If `{input}` is empty:**
-1. Find latest `plan.md` in `.s` | `find .s -name "plan.md" -type f -exec stat -f "%m %N" {} \; 2>/dev/null | sort -rn | head -1 | cut -d' ' -f2-`
-2. Parse plan for phases and status, auto-select next incomplete (prefer IN_PROGRESS or earliest Planned)
-
-**If `{input}` provided:** Use that plan and detect which phase to work on (auto-detect or use argument like "phase-2").
-
-**Output:** `✓ Step 0: [Plan Name] - [Phase Name]`
-
-** Pattern (use throughout):**
-```
-Task(_type="[type]", prompt="[task description]", description="[brief]")
-```
-
----
-
-## Workflow Sequence
-
-**Rules:** Follow steps 1-6 in order. Each step requires output marker starting with "✓ Step N:". Mark each complete in TodoWrite before proceeding. Do not skip steps.
-
----
-
-## Step 1: Analysis & Task Extraction
-
-Read plan file completely. Map dependencies between tasks. List ambiguities or blockers. Identify required skills/tools and activate from catalog. Parse phase file and extract actionable tasks.
-
-**TodoWrite Initialization & Task Extraction:**
-- Initialize TodoWrite with `Step 0: [Plan Name] - [Phase Name]` and all command steps (Step 1 through Step 6)
-- Read phase file (e.g., phase-01-preparation.md)
-- Look for tasks/steps/phases/sections/numbered/bulleted lists
-- MUST convert to TodoWrite tasks:
-  - Phase Implementation tasks → Step 2.X (Step 2.1, Step 2.2, etc.)
-  - Phase Testing tasks → Step 3.X (Step 3.1, Step 3.2, etc.)
-  - Phase Code Review tasks → Step 4.X (Step 4.1, Step 4.2, etc.)
-- Ensure each task has UNIQUE name (increment X for each task)
-- Add tasks to TodoWrite after their corresponding command step
-
-**Output:** `✓ Step 1: Found [N] tasks across [M] phases - Ambiguities: [list or "none"]`
-
-Mark Step 1 complete in TodoWrite, mark Step 2 in_progress.
-
----
-
-## Step 2: Implementation
-
-Implement selected plan phase step-by-step following extracted tasks (Step 2.1, Step 2.2, etc.). Mark tasks complete as done. For UI work, /docs/design-guidelines.md". Use `ai-multimodal` skill for image assets, `imagemagick` for editing. Run type checking and compile to verify no syntax errors.
-
-**Output:** `✓ Step 2: Implemented [N] files - [X/Y] tasks complete, compilation passed`
-
-Mark Step 2 complete in TodoWrite, mark Step 3 in_progress.
-
----
-
-## Step 3: Testing
-
-Write tests covering happy path, edge cases, and error cases.  If ANY tests fail: STOP,  Repeat until 100% pass.
-
-**Testing standards:** Unit tests may use mocks for external dependencies (APIs, DB). Integration tests use test environment. E2E tests use real but isolated data. Forbidden: commenting out tests, changing assertions to pass, TODO/FIXME to defer fixes.
-
-**Output:** `✓ Step 3: Tests [X/X passed] - All requirements met`
-
-**Validation:** If X ≠ total, Step 3 INCOMPLETE - do not proceed.
-
-Mark Step 3 complete in TodoWrite, mark Step 4 in_progress.
-
----
-
-## Step 4: Code Review
-
- Check security, performance, architecture, YAGNI/KISS/DRY". If critical issues found: STOP, fix all, re-run `tester` to verify, re-run `code-reviewer`. Repeat until no critical issues.
-
-**Critical issues:** Security vulnerabilities (XSS, SQL injection, OWASP), performance bottlenecks, architectural violations, principle violations.
-
-**Output:** `✓ Step 4: Code reviewed - [0] critical issues`
-
-**Validation:** If critical issues > 0, Step 4 INCOMPLETE - do not proceed.
-
-Mark Step 4 complete in TodoWrite, mark Step 5 in_progress.
-
----
-
-## Step 5: User Approval ⏸ BLOCKING GATE
-
-Present summary (3-5 bullets): what implemented, tests [X/X passed], code review outcome.
-
-**Ask user explicitly:** "Phase implementation complete. All tests pass, code reviewed. Approve changes?"
-
-**Stop and wait** - do not output Step 6 content until user responds.
-
-**Output (while waiting):** `⏸ Step 5: WAITING for user approval`
-
-**Output (after approval):** `✓ Step 5: User approved - Ready to complete`
-
-Mark Step 5 complete in TodoWrite, mark Step 6 in_progress.
-
----
-
-## Step 6: Finalize
-
-**Prerequisites:** User approved in Step 5 (verified above).
-
-1. **STATUS UPDATE - BOTH MANDATORY - PARALLEL EXECUTION:**
-- **Call** `project-manager` sub-agent: "Update plan status in [plan-path]. Mark plan phase [phase-name] as DONE with timestamp. Update roadmap."
-- **Call** `docs-manager` sub-agent: "Update docs for plan phase [phase-name]. Changed files: [list]."
-
-2. **ONBOARDING CHECK:** Detect onboarding requirements (API keys, env vars, config) + generate summary report with next steps.
-
-3. **AUTO-COMMIT (after steps 1 and 2 completes):**
-- Run only if: Steps 1 and 2 successful + User approved + Tests passed
-- Auto-stage, commit with message [phase - plan] 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.
-
-**Validation:** Steps 1 and 2 must complete successfully. Step 3 (auto-commit) runs only if conditions met.
-
-Mark Step 6 complete in TodoWrite.
-
-**Phase workflow finished. Ready for next plan phase.**
-
----
-
-## Critical Enforcement Rules
-
-**Step outputs must follow unified format:** `✓ Step [N]: [Brief status] - [Key metrics]`
-
-**Examples:**
-- Step 0: `✓ Step 0: [Plan Name] - [Phase Name]`
-- Step 1: `✓ Step 1: Found [N] tasks across [M] phases - Ambiguities: [list]`
-- Step 2: `✓ Step 2: Implemented [N] files - [X/Y] tasks complete`
-- Step 3: `✓ Step 3: Tests [X/X passed] - All requirements met`
-- Step 4: `✓ Step 4: Code reviewed - [0] critical issues`
-- Step 5: `✓ Step 5: User approved - Ready to complete`
-- Step 6: `✓ Step 6: Finalize - Status updated - Git committed`
-
-**If any "✓ Step N:" output missing, that step is INCOMPLETE.**
-
-**TodoWrite tracking required:** Initialize at Step 0, mark each step complete before next.
-
-**Mandatory  calls:**
-- Step 3: `tester`
-- Step 4: `code-reviewer`
-- Step 6: `project-manager` AND `docs-manager` (when user approves)
-
-**Blocking gates:**
-- Step 3: Tests must be 100% passing
-- Step 4: Critical issues must be 0
-- Step 5: User must explicitly approve
-- Step 6: Both `project-manager` and `docs-manager` must complete successfully
-
-**REMEMBER:**
-- Do not skip steps. Do not proceed if validation fails. Do not assume approval without user response.
-- One plan phase per command run. Command focuses on single plan phase only.
-- 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.