cokit-cli 1.0.0 → 1.0.2

package/skills/planning/references/plan-organization.md

@@ -1,88 +0,0 @@
-# Plan Organization
-
-How to structure implementation plans.
-
-## Plan Document Structure
-
-```markdown
----
-title: "Feature Name"
-status: pending
-effort: Xh
-created: YYYY-MM-DD
----
-
-# Plan Title
-
-## Overview
-[2-3 sentences describing what and why]
-
-## Goals
-- [ ] Goal 1
-- [ ] Goal 2
-
-## Non-Goals
-- Thing we're not doing
-- Thing deferred to later
-
-## Design
-[Architecture overview]
-
-## Phases
-
-| Phase | Description | Effort |
-|-------|-------------|--------|
-| 1 | Setup | 1h |
-| 2 | Core feature | 2h |
-| 3 | Testing | 1h |
-
-## Risks
-- Risk 1: [mitigation]
-- Risk 2: [mitigation]
-
-## Success Criteria
-- [ ] Criterion 1
-- [ ] Criterion 2
-```
-
-## Phase Documents
-
-Each phase gets its own file:
-
-```markdown
-# Phase N: Name
-
-**Effort:** Xh | **Status:** Pending
-
-## Objective
-[What this phase accomplishes]
-
-## Tasks
-- [ ] Task 1
-- [ ] Task 2
-- [ ] Task 3
-
-## Acceptance Criteria
-- [ ] Criterion 1
-- [ ] Criterion 2
-```
-
-## File Organization
-
-```
-plans/
-└── YYMMDD-feature-name/
-    ├── plan.md
-    ├── phase-01-setup.md
-    ├── phase-02-implementation.md
-    ├── phase-03-testing.md
-    └── research/
-        └── notes.md
-```
-
-## Quality Checks
-
-- [ ] Clear structure?
-- [ ] Tasks actionable?
-- [ ] Effort estimated?
-- [ ] Success criteria defined?

package/skills/planning/references/research-phase.md

@@ -1,56 +0,0 @@
-# Research Phase
-
-How to properly research before planning.
-
-## Goals
-
-- Understand problem space
-- Find existing solutions
-- Identify constraints
-- Avoid reinventing wheels
-
-## Research Steps
-
-### 1. Understand Requirements
-
-- What exactly needs to be built?
-- What's the success criteria?
-- What are the constraints?
-- Who are the stakeholders?
-
-### 2. Research Existing Solutions
-
-- How do others solve this?
-- What libraries/tools exist?
-- What patterns are common?
-- What pitfalls to avoid?
-
-### 3. Analyze Codebase
-
-- What exists already?
-- What patterns are used?
-- What can be reused?
-- What needs to change?
-
-### 4. Identify Risks
-
-- What could go wrong?
-- What's uncertain?
-- What needs clarification?
-- What are blockers?
-
-## Research Output
-
-Document findings:
-- Problem summary
-- Existing solutions
-- Recommended approach
-- Risks and mitigations
-- Open questions
-
-## Quality Checks
-
-- [ ] Requirements clear?
-- [ ] Alternatives considered?
-- [ ] Risks identified?
-- [ ] Questions listed?

package/skills/planning/references/solution-design.md

@@ -1,65 +0,0 @@
-# Solution Design
-
-How to design solutions before implementing.
-
-## Design Process
-
-### 1. Define Scope
-
-- What's included?
-- What's excluded?
-- What's the MVP?
-- What's future work?
-
-### 2. Architecture
-
-- High-level structure
-- Component breakdown
-- Data flow
-- Integration points
-
-### 3. Consider Alternatives
-
-For each major decision:
-- Option A: [description]
-- Option B: [description]
-- Recommendation: [choice + reasoning]
-
-### 4. Trade-offs
-
-Document trade-offs:
-- Performance vs simplicity
-- Flexibility vs complexity
-- Speed vs quality
-
-## Design Output
-
-### Architecture Document
-
-```markdown
-## Overview
-[1-2 sentences]
-
-## Components
-- Component A: [purpose]
-- Component B: [purpose]
-
-## Data Flow
-[diagram or description]
-
-## Key Decisions
-- Decision 1: [choice + why]
-- Decision 2: [choice + why]
-
-## Trade-offs
-- [trade-off 1]
-- [trade-off 2]
-```
-
-## Quality Checks
-
-- [ ] Scope clear?
-- [ ] Components defined?
-- [ ] Alternatives considered?
-- [ ] Trade-offs documented?
-- [ ] Fits existing patterns?

package/templates/repo/prompts/code.prompt.md

@@ -1,40 +0,0 @@
----
-mode: agent
-description: Implement from existing plan
----
-# Implement Plan
-
-Implement the specified plan phase.
-
-## Process
-
-1. **Read Plan**
-   - Load plan.md completely
-   - Identify current phase
-   - List tasks to complete
-
-2. **Implement**
-   - Work through tasks sequentially
-   - Follow existing patterns
-   - Run type checks frequently
-
-3. **Test**
-   - Write tests for new code
-   - Run full test suite
-   - Fix any failures
-
-4. **Review**
-   - Check for security issues
-   - Verify error handling
-   - Ensure code quality
-
-5. **Complete**
-   - Update plan status
-   - Summarize changes
-   - List remaining work
-
-## Guidelines
-- Follow YAGNI/KISS/DRY
-- Keep files under 200 lines
-- Document complex logic
-- No TODO without issue tracking

package/templates/repo/prompts/docs.prompt.md

@@ -1,29 +0,0 @@
----
-mode: agent
-description: Update project documentation
----
-# Update Documentation
-
-Update documentation for recent changes.
-
-## Process
-
-1. **Identify Changes**
-   - Review recent commits
-   - List new features
-   - Note API changes
-
-2. **Update Docs**
-   - README.md for user-facing changes
-   - API docs for endpoint changes
-   - Architecture docs for structural changes
-
-3. **Verify**
-   - Links work
-   - Examples accurate
-   - No outdated references
-
-## Guidelines
-- Keep concise
-- Use examples
-- Update table of contents

package/templates/repo/prompts/fix.prompt.md

@@ -1,35 +0,0 @@
----
-mode: agent
-description: Debug and fix code issues
----
-# Fix Issue
-
-Analyze the described issue and fix it systematically.
-
-## Process
-
-1. **Identify Issue Type**
-   - Type errors → Check TypeScript config, type definitions
-   - UI/UX issues → Check styles, layout, responsiveness
-   - Test failures → Run tests, analyze failures
-   - Build errors → Check dependencies, config
-
-2. **Investigate Root Cause**
-   - Read error messages completely
-   - Find working examples in codebase
-   - Trace back to source of problem
-
-3. **Apply Fix**
-   - Make minimal changes
-   - Follow existing patterns
-   - Update related tests
-
-4. **Verify**
-   - Run tests
-   - Check types compile
-   - Confirm issue resolved
-
-## Guidelines
-- No fixes without understanding root cause
-- One fix at a time
-- Verify before claiming done

package/templates/repo/prompts/plan.prompt.md

@@ -1,41 +0,0 @@
----
-mode: agent
-description: Create implementation plan for features
----
-# Create Plan
-
-Create a detailed implementation plan for the described task.
-
-## Process
-
-1. **Understand Requirements**
-   - Clarify scope and constraints
-   - Identify dependencies
-   - Note assumptions
-
-2. **Research**
-   - Review relevant codebase areas
-   - Check existing patterns
-   - Identify technical approach
-
-3. **Design Solution**
-   - Break into phases
-   - List tasks per phase
-   - Estimate effort
-
-4. **Document Plan**
-   - Create plan file in ./plans/
-   - Include success criteria
-   - List open questions
-
-## Output
-Create `./plans/{date}-{name}/plan.md` with:
-- Overview (1-3 sentences)
-- Phases table
-- Success criteria checklist
-- Unresolved questions
-
-## Principles
-- YAGNI: Don't over-engineer
-- KISS: Prefer simple solutions
-- DRY: Identify reusable patterns

package/templates/repo/prompts/review.prompt.md

@@ -1,38 +0,0 @@
----
-mode: agent
-description: Review code for issues
----
-# Code Review
-
-Review the specified code for quality and issues.
-
-## Check Categories
-
-### Security
-- [ ] Input validation
-- [ ] No hardcoded secrets
-- [ ] SQL injection prevention
-- [ ] XSS prevention
-
-### Performance
-- [ ] No N+1 queries
-- [ ] Appropriate caching
-- [ ] No memory leaks
-
-### Quality
-- [ ] YAGNI compliance
-- [ ] KISS compliance
-- [ ] DRY compliance
-- [ ] Error handling
-- [ ] Test coverage
-
-### Maintainability
-- [ ] Clear naming
-- [ ] Reasonable file size
-- [ ] Documentation for complex logic
-
-## Output
-List issues by severity:
-- **Critical**: Must fix before merge
-- **Important**: Should fix soon
-- **Minor**: Nice to have

package/templates/repo/prompts/test.prompt.md

@@ -1,29 +0,0 @@
----
-mode: agent
-description: Run tests and analyze results
----
-# Run Tests
-
-Run the test suite and analyze results.
-
-## Process
-
-1. **Run Tests**
-   - Execute test command (npm test, pytest, etc.)
-   - Capture full output
-
-2. **Analyze Results**
-   - Count passed/failed/skipped
-   - Identify failure patterns
-   - Check for flaky tests
-
-3. **Report**
-   - Summary: X passed, Y failed, Z skipped
-   - List failing tests with error messages
-   - Suggest fixes for failures
-
-## If Tests Fail
-- Read error message completely
-- Find root cause before fixing
-- Fix one issue at a time
-- Re-run to verify fix