npm - cokit-cli - Versions diffs - 1.0.8 → 1.2.0 - Mend

cokit-cli 1.0.8 → 1.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1507) hide show

package/plans/reports/project-manager-260106-1734-phase3-to-phase4-transition.md DELETED Viewed

@@ -1,274 +0,0 @@
-# Phase 3 → Phase 4 Transition Checklist
-**Date:** 2026-01-06 | **Transition:** User-Level Skills → Prompt Files | **Est. Time:** 15 min
----
-## Phase 3 Closure Verification
-### Documentation Complete
-- [x] debugging SKILL.md + 3 references (283 lines)
-- [x] code-review SKILL.md + 2 references (248 lines)
-- [x] planning SKILL.md + 3 references (291 lines)
-- [x] docs-seeker SKILL.md + 2 references (261 lines)
-- [x] sequential-thinking SKILL.md + 2 references (255 lines)
-- [x] Total: 1,338 lines across 17 files
-### Quality Gates Passed
-- [x] 0 security issues found
-- [x] 0 critical defects
-- [x] 100% Copilot compatibility verified
-- [x] YAGNI/KISS/DRY compliance: Excellent
-- [x] All tests passing
-- [x] Code review completed
-- [x] Progressive disclosure pattern validated
-### Deliverables Location Verified
-- [x] Skills directory: `skills/` (repo-level)
-- [x] Structure: Each skill has SKILL.md + references/
-- [x] Relative paths tested and working
-- [x] No Claude-specific references remain
-- [x] Cross-linking validated
-### Phase 3 Documentation Updated
-- [x] phase-03-user-level-skills.md marked COMPLETE
-- [x] Timestamp recorded: 2026-01-06
-- [x] Review notes included
-- [x] Quality metrics documented
-- [x] Deliverables listed
-### Main Plan Updated
-- [x] Status: in_progress (continuing to Phase 4)
-- [x] Effort: Reduced to 12h (4 phases remain)
-- [x] Metadata: completed_phases: [1, 2, 3]
-- [x] Metadata: phase3_completed: 2026-01-06
----
-## Project Status Verification
-### Overall Progress
-- [x] 11h of 16h effort completed (69%)
-- [x] 3 of 5 phases complete
-- [x] 2 phases remaining (4-5)
-- [x] Remaining effort: 5h (Phase 4: 2h, Phase 5: 3h)
-- [x] Timeline: On track for same-day completion
-### No Blockers
-- [x] All dependencies satisfied
-- [x] No critical risks
-- [x] Resource capacity available
-- [x] Clear execution path forward
----
-## Phase 4 Preparation
-### Directory Structure Ready
-- [x] Verify `templates/repo/prompts/` directory exists
-- [x] Phase 2 repo templates in place
-- [x] No conflicts with existing files
-- [x] Path structure: `templates/repo/prompts/{name}.prompt.md`
-### Documentation Prepared
-- [x] Phase 4 Kickoff document created
-- [x] Prompt specifications detailed (all 6 prompts)
-- [x] Conversion rules documented
-- [x] Validation checklist prepared
-- [x] Effort breakdown provided
-### Source Files Identified
-- [x] /Users/admin/.claude/commands/ck/fix.md (fix.prompt.md)
-- [x] /Users/admin/.claude/commands/ck/plan.md (plan.prompt.md)
-- [x] /Users/admin/.claude/commands/ck/code.md (code.prompt.md)
-- [x] /Users/admin/.claude/commands/ck/test.md (test.prompt.md)
-- [x] /Users/admin/.claude/commands/ck/review/codebase.md (review.prompt.md)
-- [x] /Users/admin/.claude/commands/ck/docs/update.md (docs.prompt.md)
-### Conversion Rules Clear
-- [x] Remove `$ARGUMENTS` variable
-- [x] Add `mode: agent` frontmatter
-- [x] Convert routing to steps
-- [x] Remove subagent delegation
-- [x] Keep <50 lines per prompt
-- [x] Validate Copilot compatibility
----
-## Team Readiness
-### Knowledge Transfer
-- [x] Phase 4 objectives understood
-- [x] Conversion patterns clear
-- [x] Copilot constraints documented
-- [x] Success criteria defined
-- [x] Effort breakdown realistic
-### Resources Allocated
-- [x] Developer assigned to Phase 4
-- [x] 2-hour time block reserved
-- [x] Testing environment ready (GitHub Copilot)
-- [x] Documentation resources available
-- [x] Support channel available if needed
-### Execution Plan Clear
-- [x] Start with simplest prompt (test.prompt.md)
-- [x] Completion order: test → docs → plan → review → fix → code
-- [x] Validation after each prompt
-- [x] Integration testing at end
-- [x] Checkpoint after 1h (3 prompts complete)
----
-## Sign-Off
-### Phase 3 Officially Complete
-**Status:** ✓ APPROVED FOR CLOSURE
-Phase 3 meets all acceptance criteria:
-- 5 user-level skills successfully ported
-- 17 files total (5 SKILL.md + 12 reference files)
-- 1,338 lines of documentation
-- All tests passed, 0 critical issues
-- 100% Copilot compatibility verified
-**Authority:** Project Manager
-**Date:** 2026-01-06
-**Confidence:** HIGH
-### Phase 4 Approved to Start
-**Status:** ✓ READY TO BEGIN
-All preconditions satisfied:
-- Phase 3 complete and verified
-- Phase 4 plan documented
-- Resources allocated
-- No blockers identified
-- Success criteria clear
-**Authority:** Project Manager
-**Date:** 2026-01-06
-**Target Start:** Immediately
-**Estimated Duration:** 2 hours
----
-## Phase 4 Immediate Tasks
-### First 10 Minutes
-1. [ ] Review Phase 4 Kickoff document
-2. [ ] Verify prompt directory structure created
-3. [ ] Read all 6 source command files
-4. [ ] Understand conversion rules thoroughly
-### First 30 Minutes
-1. [ ] Create test.prompt.md (simplest first)
-2. [ ] Test in Copilot agent mode
-3. [ ] Validate output matches expectations
-4. [ ] Checkpoint: 1/6 prompts complete
-### Next Hour
-1. [ ] Create docs.prompt.md
-2. [ ] Create plan.prompt.md
-3. [ ] Test both in Copilot
-4. [ ] Checkpoint: 3/6 prompts complete
-### Final Hour
-1. [ ] Create review.prompt.md
-2. [ ] Create fix.prompt.md (high complexity)
-3. [ ] Create code.prompt.md (highest complexity)
-4. [ ] Full validation of all 6 prompts
-5. [ ] Integration testing with Phase 2 templates
-### Completion Checklist
-- [ ] All 6 prompts created
-- [ ] Each prompt <50 lines
-- [ ] No $ARGUMENTS references
-- [ ] No subagent references
-- [ ] Each prompt tested in Copilot
-- [ ] All validation criteria passed
-- [ ] Ready for Phase 5
----
-## Handoff Document Summary
-### For Developers
-- Phase 3 is complete and verified
-- All skills available for reference
-- Phase 4 is clearly scoped with 2h effort
-- Conversion patterns documented
-- Testing approach defined
-### For Quality Assurance
-- Phase 3 validation complete (0 issues)
-- Phase 4 success criteria prepared
-- Testing approach documented
-- No regressions expected
-- Integration points clear
-### For Project Manager
-- 69% project completion confirmed
-- 5h remaining effort (Phases 4-5)
-- Same-day completion possible
-- No critical risks identified
-- All metrics on track
----
-## References
-### Phase 3 Completion Report
-`plans/reports/project-manager-260106-1734-phase3-completion.md`
-- Detailed metrics and analysis
-- Quality verification
-- Risk assessment
-- Timeline health
-### Phase 4 Kickoff Document
-`plans/reports/project-manager-260106-1734-phase4-kickoff.md`
-- Complete Phase 4 specification
-- Conversion framework
-- Individual prompt specs
-- Validation checklist
-- Effort breakdown
-### Project Status Report
-`plans/reports/project-manager-260106-1734-project-status.md`
-- Overall project health
-- Success criteria progress
-- Risk assessment
-- Resource planning
-- Recommendations
-### Main Implementation Plan
-`plans/260106-1102-cokit-implementation/plan.md`
-- Original project overview
-- Architecture documentation
-- All phase links
-- Success criteria
-### Phase 4 Plan Document
-`plans/260106-1102-cokit-implementation/phases/phase-04-prompt-files.md`
-- Detailed specifications
-- Task breakdown
-- Validation checklist
-- Integration points
----
-## Transition Complete
-**Phase 3 officially closed.** All deliverables verified, documented, and ready for deployment.
-**Phase 4 ready to begin.** All prerequisites met, resources allocated, clear path forward.
-**Next checkpoint:** Phase 4 completion assessment (target: 2 hours)
----
-**Transition approved and ready to proceed.**
-Date: 2026-01-06
-Authority: Project Manager
-Status: ✓ READY FOR PHASE 4

package/plans/reports/project-manager-260106-1734-phase4-kickoff.md DELETED Viewed

@@ -1,343 +0,0 @@
-# Phase 4 Kickoff: Prompt Files
-**Date:** 2026-01-06 | **Phase:** 4 of 5 | **Effort:** 2h | **Status:** Ready to Start
----
-## Phase Overview
-Convert 6 core Claude Code commands to Copilot-compatible prompt files.
-**Deliverables:**
-- fix.prompt.md - Debug & fix code issues
-- plan.prompt.md - Create implementation plans
-- code.prompt.md - Implement from plans
-- test.prompt.md - Run tests & analyze
-- review.prompt.md - Review code quality
-- docs.prompt.md - Update documentation
-**Target Location:** `templates/repo/prompts/` (repo-level templates)
-**Success Criteria:** 6 prompts created, tested, <50 lines each, 100% Copilot compatible
----
-## Conversion Framework
-### Prompt Frontmatter Template
-```yaml
----
-mode: agent
-description: [One-line description]
----
-# [Prompt Title]
-[Brief intro paragraph]
-## Process
-1. **Step One**
-   - Sub-point
-   - Sub-point
-2. **Step Two**
-   - Sub-point
-   - Sub-point
-## Guidelines
-- Key principle 1
-- Key principle 2
-```
-### Key Conversion Rules
-| Claude Code | Copilot | Action |
-|------------|---------|--------|
-| `/command` | `command.prompt.md` | Rename with `.prompt.md` suffix |
-| `argument-hint` | Remove | Copilot users provide context in chat |
-| `$ARGUMENTS` | User input | Reference "in the chat" or "you provided" |
-| Sub-commands (`/fix:types`) | Inline instructions | Move to conditional sections |
-| Subagent delegation | Direct instructions | User performs steps manually |
-| Hooks/dynamic config | Removed | N/A - static config only |
-| Copilot routing | Removed | Single agent limitation |
-### Content Guidelines
-- **Length:** <50 lines (fits in view without scrolling)
-- **Structure:** 4-5 main steps max
-- **Clarity:** Active voice, clear imperative mood
-- **Context:** No assumptions about user knowledge
-- **Examples:** Use 1-2 concrete examples per prompt
----
-## Individual Prompt Specifications
-### 4.1 fix.prompt.md
-**Source:** `/Users/admin/.claude/commands/ck/fix.md`
-**Purpose:** Debug and fix code issues systematically
-**Complexity:** Medium (remove routing logic)
-**Key Conversions:**
-- Remove `$ARGUMENTS` (user describes issue in chat)
-- Remove `/fix:types`, `/fix:tests`, `/fix:build` routing (use conditional steps)
-- Remove "delegate to debugger" (user runs steps manually)
-- Keep: "NO FIXES WITHOUT ROOT CAUSE" principle
-**Outline:**
-1. Identify Issue Type (error type, test failure, build error, etc.)
-2. Investigate Root Cause (read errors, find examples, trace source)
-3. Apply Fix (minimal changes, follow patterns)
-4. Verify (run tests, check types, confirm resolution)
-**Estimated Lines:** 35-40
----
-### 4.2 plan.prompt.md
-**Source:** `/Users/admin/.claude/commands/ck/plan.md`
-**Purpose:** Create detailed implementation plans
-**Complexity:** Medium (remove hooks/config injection)
-**Key Conversions:**
-- Remove `$ARGUMENTS` (user describes task in chat)
-- Remove "Plan Context injection" hook references
-- Remove `set-active-plan.cjs` references
-- Simplify to static planning workflow
-- Keep: YAGNI/KISS/DRY principles
-**Outline:**
-1. Understand Requirements (clarify scope, dependencies, assumptions)
-2. Research (review codebase, check patterns, identify approach)
-3. Design Solution (break into phases, list tasks, estimate effort)
-4. Document Plan (create ./plans/{date}-{name}/plan.md with success criteria)
-**Output Format:**
-```
-./plans/{YYYYMMDD}-{slug}/plan.md
-```
-**Estimated Lines:** 40-45
----
-### 4.3 code.prompt.md
-**Source:** `/Users/admin/.claude/commands/ck/code.md`
-**Purpose:** Implement from existing plan
-**Complexity:** High (remove subagent routing, agent delegation)
-**Key Conversions:**
-- Remove subagent delegation (`delegate to backend-developer`)
-- Remove Task tool references
-- Convert routing logic to sequential steps
-- Remove report generation expectations (manual task)
-- Keep: YAGNI/KISS/DRY, testing discipline
-**Outline:**
-1. Read Plan (load plan.md, identify current phase, list tasks)
-2. Implement (work sequentially, follow patterns, check types)
-3. Test (write tests, run suite, fix failures)
-4. Review (check security, error handling, code quality)
-5. Complete (update plan status, summarize changes, list remaining)
-**Estimated Lines:** 45-50
----
-### 4.4 test.prompt.md
-**Source:** `/Users/admin/.claude/commands/ck/test.md`
-**Purpose:** Run tests and analyze results
-**Complexity:** Low (straightforward workflow)
-**Key Conversions:**
-- Keep command structure (test framework agnostic)
-- Add flexibility for different test runners (npm test, pytest, etc.)
-- Keep failure analysis process
-**Outline:**
-1. Run Tests (execute test command, capture output)
-2. Analyze Results (count passed/failed/skipped, identify patterns)
-3. Report (summary, failing tests with messages, suggested fixes)
-4. If Tests Fail (read errors, find root cause, fix one at a time, re-run)
-**Estimated Lines:** 30-35
----
-### 4.5 review.prompt.md
-**Source:** `/Users/admin/.claude/commands/ck/review/codebase.md` (adapted)
-**Purpose:** Review code for quality and security issues
-**Complexity:** Medium (categorized checklist)
-**Key Conversions:**
-- Simplify from multi-agent review to single review pass
-- Remove reviewer role assignment
-- Keep: Category-based checking (Security, Performance, Quality, Maintainability)
-**Check Categories:**
-- Security (input validation, no secrets, injection prevention, XSS prevention)
-- Performance (no N+1 queries, caching, no memory leaks)
-- Quality (YAGNI, KISS, DRY compliance, error handling, test coverage)
-- Maintainability (clear naming, reasonable file size, complex logic documented)
-**Output:** Issues listed by severity (Critical, Important, Minor)
-**Estimated Lines:** 40-45
----
-### 4.6 docs.prompt.md
-**Source:** `/Users/admin/.claude/commands/ck/docs/update.md` (adapted)
-**Purpose:** Update project documentation
-**Complexity:** Low (straightforward workflow)
-**Key Conversions:**
-- Keep basic update workflow
-- Add flexibility for different doc types (README, API docs, architecture)
-- Remove expectation of automated doc generation
-**Outline:**
-1. Identify Changes (review commits, list new features, note API changes)
-2. Update Docs (README for user changes, API docs for endpoints, architecture docs for structure)
-3. Verify (check links, verify examples, check for outdated refs)
-**Guidelines:**
-- Keep concise
-- Use examples
-- Update table of contents
-**Estimated Lines:** 30-35
----
-## Validation Checklist
-Before considering Phase 4 complete:
-- [ ] All 6 prompts created in `templates/repo/prompts/`
-- [ ] Each prompt has correct frontmatter: `mode: agent` + description
-- [ ] No `$ARGUMENTS` variable references remain
-- [ ] No subagent or Task tool references remain
-- [ ] No hook-based patterns (static config only)
-- [ ] Each prompt clearly lists steps 1-N
-- [ ] Each prompt under 50 lines
-- [ ] Decision logic converted to conditional text (not routing)
-- [ ] All prompts tested in Copilot agent mode
-- [ ] Examples added where helpful
-- [ ] Language is clear and imperative
----
-## Integration Points
-### With Repo Templates (Phase 2)
-- Prompts live in `templates/repo/.github/prompts/` (per architecture)
-- CLI will copy these to new repos during `npx cokit init`
-- Users can customize per repo if needed
-### With Skills (Phase 3)
-- Prompts reference skills but don't require them
-- Skills provide methodology, prompts provide task automation
-- No circular dependencies
-### With Documentation (Phase 5)
-- Phase 5 will include usage examples for each prompt
-- Phase 5 will document how to customize prompts
-- Phase 5 will explain when to use which prompt
----
-## Effort Breakdown
-| Task | Estimate | Notes |
-|------|----------|-------|
-| Create fix.prompt.md | 20min | Medium complexity, routing logic |
-| Create plan.prompt.md | 20min | Medium complexity, simplify hooks |
-| Create code.prompt.md | 25min | High complexity, most routing |
-| Create test.prompt.md | 15min | Low complexity, straightforward |
-| Create review.prompt.md | 20min | Medium complexity, checklist |
-| Create docs.prompt.md | 15min | Low complexity, straightforward |
-| Testing & validation | 15min | Run each in Copilot, verify output |
-| **Total** | **2h** | Tight timeline, focused execution |
----
-## Success Indicators
-**Phase 4 is complete when:**
-1. ✓ 6 prompt files created and committed
-2. ✓ Each prompt tested in GitHub Copilot agent mode
-3. ✓ All validation checklist items verified
-4. ✓ No issues identified during testing
-5. ✓ Each prompt clearly guides users through task
-6. ✓ Prompts integrate seamlessly with Phase 2 templates
-7. ✓ Ready for Phase 5 documentation work
----
-## Known Constraints
-- **Copilot Limitations:** Single agent, no hooks, no dynamic context injection
-- **File Size:** Tight 2h timeline - focus on essentials
-- **Testing:** Must test in actual GitHub Copilot, not simulation
-- **Customization:** Minimize - keep templates simple, let users customize
----
-## Kickoff Checklist
-Before starting implementation:
-- [ ] Review Phase 3 completion (already done ✓)
-- [ ] Read this kickoff document completely
-- [ ] Understand conversion rules and constraints
-- [ ] Identify Copilot test environment
-- [ ] Create `templates/repo/prompts/` directory structure
-- [ ] Start with simplest prompt (test.prompt.md) for momentum
-- [ ] Complete in order: test → docs → plan → review → fix → code
-- [ ] Validate after each prompt in Copilot
----
-## Next Steps After Phase 4
-**Phase 5 (Documentation & README):** 3h
-- Create simple README with screenshots
-- Document each prompt with examples
-- Add setup instructions for non-technical users
-- Include troubleshooting guide
-- Create Getting Started guide
-**Expected Completion:** Same day (aggressive 16h sprint) or next business day
----
-## Questions for Implementation Team
-1. Should prompts be tested in VS Code Copilot or all supported IDEs?
-2. If testing reveals Copilot limitations, how should we adapt?
-3. Should we create prompt variants for different project types?
-4. How much customization guidance should we include in Phase 5 docs?
-5. Should we reserve time for prompt refinement after Phase 5 feedback?
----
-## Resources
-- **Prompt template location:** `templates/repo/prompts/`
-- **Source files reference:** `/Users/admin/.claude/commands/ck/`
-- **Architecture guide:** Phase 2 documentation
-- **Copilot docs:** https://docs.github.com/en/copilot/
-- **Phase 3 completion report:** `plans/reports/project-manager-260106-1734-phase3-completion.md`
----
-**Ready to start Phase 4. Good luck!**