cokit-cli 1.2.0 → 1.2.3

package/prompts/ck-spec-taskstoissues.prompt.md

@@ -1,48 +0,0 @@
----
-agent: 'agent'
-description: 'Convert tasks into GitHub issues for project tracking'
-tools:
-  - github/github-mcp-server/issue_write
-scripts:
-  sh: spec-kit/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks
-  ps: spec-kit/scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks
----
-
-## User Input
-
-```text
-${input}
-```
-
-You **MUST** consider the user input before proceeding (if not empty).
-
-## Outline
-
-1. Run `{SCRIPT}` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").
-
-2. From the executed script, extract the path to **tasks**.
-
-3. **Verify Git repository and GitHub remote**:
-   - Check if this is a git repository: `git rev-parse --git-dir 2>/dev/null`
-   - If NOT a git repo: **STOP** and inform user "This command requires a git repository with a GitHub remote. Initialize git first or use `/ck.spec.implement` instead."
-   - Get the Git remote: `git config --get remote.origin.url`
-
-> [!CAUTION]
-> ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL (contains github.com)
-
-4. For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote.
-
-> [!CAUTION]
-> UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL
-
----
-
-## Suggested Next Steps
-
-| Command | Description | When to Use |
-|---------|-------------|-------------|
-| `/ck.spec.implement` | Start implementation | Issues created, ready to code |
-| `/ck.spec.tasks` | Regenerate tasks | Need to update task list |
-| `/ck.kanban` | View project board | Track progress on created issues |
-
-**Usage:** Run after `/ck.spec.tasks` to sync tasks with GitHub Issues for team tracking

package/skills/cook/references/subagent-patterns.md

@@ -1,75 +0,0 @@
-# Subagent Patterns
-
-Standard patterns for spawning and using subagents in cook workflows.
-
-## Task Tool Pattern
-```
-Task(subagent_type="[type]", prompt="[task description]", description="[brief]")
-```
-
-## Research Phase
-```
-Task(subagent_type="researcher", prompt="Research [topic]. Report ≤150 lines.", description="Research [topic]")
-```
-- Use multiple researchers in parallel for different topics
-- Keep reports ≤150 lines with citations
-
-## Scout Phase
-```
-Task(subagent_type="scout", prompt="Find files related to [feature] in codebase", description="Scout [feature]")
-```
-- Use `/scout:ext` (preferred) or `/scout` (fallback)
-
-## Planning Phase
-```
-Task(subagent_type="planner", prompt="Create implementation plan based on reports: [reports]. Save to [path]", description="Plan [feature]")
-```
-- Input: researcher and scout reports
-- Output: `plan.md` + `phase-XX-*.md` files
-
-## UI Implementation
-```
-Task(subagent_type="ui-ux-designer", prompt="Implement [feature] UI per ./docs/design-guidelines.md", description="UI [feature]")
-```
-- For frontend work
-- Follow design guidelines
-
-## Testing
-```
-Task(subagent_type="tester", prompt="Run test suite for plan phase [phase-name]", description="Test [phase]")
-```
-- Must achieve 100% pass rate
-
-## Debugging
-```
-Task(subagent_type="debugger", prompt="Analyze failures: [details]", description="Debug [issue]")
-```
-- Use when tests fail
-- Provides root cause analysis
-
-## Code Review
-```
-Task(subagent_type="code-reviewer", prompt="Review changes for [phase]. Check security, performance, YAGNI/KISS/DRY. Return score (X/10), critical, warnings, suggestions.", description="Review [phase]")
-```
-
-## Project Management
-```
-Task(subagent_type="project-manager", prompt="Update plan status in [path]. Mark [phase] as DONE. Update roadmap.", description="Update plan")
-```
-
-## Documentation
-```
-Task(subagent_type="docs-manager", prompt="Update docs for [phase]. Changed files: [list]", description="Update docs")
-```
-
-## Git Operations
-```
-Task(subagent_type="git-manager", prompt="Stage and commit changes with conventional commit message", description="Commit changes")
-```
-
-## Parallel Execution
-```
-Task(subagent_type="fullstack-developer", prompt="Implement [phase-file] with file ownership: [files]", description="Implement phase [N]")
-```
-- Launch multiple for parallel phases
-- Include file ownership boundaries

package/templates/repo/.github/prompts/ck-spec-taskstoissues.prompt.md

@@ -1,48 +0,0 @@
----
-agent: 'agent'
-description: 'Convert tasks into GitHub issues for project tracking'
-tools:
-  - github/github-mcp-server/issue_write
-scripts:
-  sh: spec-kit/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks
-  ps: spec-kit/scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks
----
-
-## User Input
-
-```text
-${input}
-```
-
-You **MUST** consider the user input before proceeding (if not empty).
-
-## Outline
-
-1. Run `{SCRIPT}` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").
-
-2. From the executed script, extract the path to **tasks**.
-
-3. **Verify Git repository and GitHub remote**:
-   - Check if this is a git repository: `git rev-parse --git-dir 2>/dev/null`
-   - If NOT a git repo: **STOP** and inform user "This command requires a git repository with a GitHub remote. Initialize git first or use `/ck.spec.implement` instead."
-   - Get the Git remote: `git config --get remote.origin.url`
-
-> [!CAUTION]
-> ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL (contains github.com)
-
-4. For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote.
-
-> [!CAUTION]
-> UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL
-
----
-
-## Suggested Next Steps
-
-| Command | Description | When to Use |
-|---------|-------------|-------------|
-| `/ck.spec.implement` | Start implementation | Issues created, ready to code |
-| `/ck.spec.tasks` | Regenerate tasks | Need to update task list |
-| `/ck.kanban` | View project board | Track progress on created issues |
-
-**Usage:** Run after `/ck.spec.tasks` to sync tasks with GitHub Issues for team tracking

package/templates/repo/.github/skills/cook/references/subagent-patterns.md

@@ -1,75 +0,0 @@
-# Subagent Patterns
-
-Standard patterns for spawning and using subagents in cook workflows.
-
-## Task Tool Pattern
-```
-Task(subagent_type="[type]", prompt="[task description]", description="[brief]")
-```
-
-## Research Phase
-```
-Task(subagent_type="researcher", prompt="Research [topic]. Report ≤150 lines.", description="Research [topic]")
-```
-- Use multiple researchers in parallel for different topics
-- Keep reports ≤150 lines with citations
-
-## Scout Phase
-```
-Task(subagent_type="scout", prompt="Find files related to [feature] in codebase", description="Scout [feature]")
-```
-- Use `/scout:ext` (preferred) or `/scout` (fallback)
-
-## Planning Phase
-```
-Task(subagent_type="planner", prompt="Create implementation plan based on reports: [reports]. Save to [path]", description="Plan [feature]")
-```
-- Input: researcher and scout reports
-- Output: `plan.md` + `phase-XX-*.md` files
-
-## UI Implementation
-```
-Task(subagent_type="ui-ux-designer", prompt="Implement [feature] UI per ./docs/design-guidelines.md", description="UI [feature]")
-```
-- For frontend work
-- Follow design guidelines
-
-## Testing
-```
-Task(subagent_type="tester", prompt="Run test suite for plan phase [phase-name]", description="Test [phase]")
-```
-- Must achieve 100% pass rate
-
-## Debugging
-```
-Task(subagent_type="debugger", prompt="Analyze failures: [details]", description="Debug [issue]")
-```
-- Use when tests fail
-- Provides root cause analysis
-
-## Code Review
-```
-Task(subagent_type="code-reviewer", prompt="Review changes for [phase]. Check security, performance, YAGNI/KISS/DRY. Return score (X/10), critical, warnings, suggestions.", description="Review [phase]")
-```
-
-## Project Management
-```
-Task(subagent_type="project-manager", prompt="Update plan status in [path]. Mark [phase] as DONE. Update roadmap.", description="Update plan")
-```
-
-## Documentation
-```
-Task(subagent_type="docs-manager", prompt="Update docs for [phase]. Changed files: [list]", description="Update docs")
-```
-
-## Git Operations
-```
-Task(subagent_type="git-manager", prompt="Stage and commit changes with conventional commit message", description="Commit changes")
-```
-
-## Parallel Execution
-```
-Task(subagent_type="fullstack-developer", prompt="Implement [phase-file] with file ownership: [files]", description="Implement phase [N]")
-```
-- Launch multiple for parallel phases
-- Include file ownership boundaries