cokit-cli 1.0.8 → 1.2.0

package/templates/repo/.github/prompts/ck-bootstrap-auto-fast.prompt.md

@@ -1,108 +0,0 @@
----
-agent: 'agent'
-description: 'Quickly bootstrap a new project automatically'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
----
-
-**Think hard** to plan & bootstrap a new project follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules in your `CLAUDE.md` file:
-
----
-
-## User's Objectives & Requirements
-
-<user-requirements>${input}</user-requirements>
-
----
-
-## Role Responsibilities
-
-- You are an elite software engineering expert who specializes in system architecture design and technical decision-making. 
-- Your core mission is to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs, then collaborate with your  implement the plan.
-- You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
-
-- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-
----
-
-## Your Approach
-
-1. **Brutal Honesty**: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.
-2. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
-
----
-
-## Workflow:
-
-Follow strictly these following steps:
-
-**First thing first:** check if Git has been initialized, if not, quickly initialize it (use `main` branch).
-
-**IMPORTANT:** 
-
-### Research & Planning: Tech Stack, Wireframe & Design
-
-1. **Research (do these following tasks ):**
-* explore the user's request, idea validation, challenges, and find the best possible solutions.
-* find a best fit tech stack for this project.
-* create a design plan that follows the progressive disclosure structure:
-  - Create a directory using naming pattern from `## Naming` section.
-  - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
-  - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
-* Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
-   - **Research** about design style, trends, fonts, colors, border, spacing, elements' positions, etc.
-   - Describe details of the assets in the design so they can be generated with `ai-multimodal` skill later on.
-   - **IMPORTANT:** Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use **Inter** or **Poppins** fonts.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-2. **Planning (do these following tasks one after another):**
-* analyze the research results and create the design guidelines at `./docs/design-guidelines.md` file & generate wireframes in HTML at `./docs/wireframe` directory, make sure it's clear for developers to implement later on.
-* If there are no logo provided, 
-* /docs/wireframes/` directory.
-* analyze all reports and create the detailed step by step implementation plan at `.s` directory following the progressive disclosure structure above.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-### Implementation
-
-* Use `general agent (main agent)` to implement the plan step by step, follow the implementation plan in `.s` directory.
-* implement the frontend part follow the design guidelines at `./docs/design-guidelines.md` file.
-  * Use `ai-multimodal` (`video-analysis`, or `document-extraction`) skills to analyze the generated assets based on their format.
-  * Use `Background Removal Tool` to remove background from the assets if needed.
-  * Use `ai-multimodal` (`image-generation`) skill to edit the assets if needed.
-* Run type checking and compile the code command to make sure there are no syntax errors.
-
-### Testing
-
-* Write the tests for the plan, make sure you don't use fake data just to pass the tests, tests should be real and cover all possible cases.
-* run the tests, make sure all tests pass and the app is working, .
-* If there are issues or failed tests, find the root cause of the issues, then ask main agent to fix all of them. 
-* Repeat the process until all tests pass or no more issues are reported. 
-* **Again, do not ignore failed tests or use fake data just to pass the build or github actions.**
-
-### Code Review
-
-* After finishing, review code. If there are critical issues, ask main agent to improve the code and tell `tester` agent to run the tests again. Repeat the process until all tests pass.
-* When all tests pass, code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-### Documentation
-
-* update the docs if needed.
-  * Create/update `./docs/README.md` file (keep it concise and under 300 lines).
-  * Create/update `./docs/project-overview.-pdr.md` (Product Development Requirements) file.
-  * Create/update `./` file.
-  * Create/update `./docs/system-architecture.md` file.
-  * **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-* create a project roadmap at `./docs/project-roadmap.md` file.
-
-### Final Report
-* Report back to user with a summary of the changes and explain everything briefly.
-* create commits for the implemented changes (DO NOT push to remote repository).
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-
-### Onboarding
-
-* Instruct the user to get started with the project:
-  * Help the user to configure the project step by step, ask 1 question at a time, wait for the user to answer before moving to the next question.
-  * For example: instruct the user to obtain the API key from the provider, then ask the user to provide the API key to add it to the environment variables.
-* If user requests to change the configuration, repeat the previous step until the user approves the configuration.

package/templates/repo/.github/prompts/ck-bootstrap-auto-parallel.prompt.md

@@ -1,66 +0,0 @@
----
-agent: 'agent'
-description: 'Bootstrap project with parallel execution'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
----
-
-**Ultrathink parallel** to bootstrap: <user-requirements>${input}</user-requirements>
-
-**IMPORTANT:** Activate needed skills. Ensure token efficiency. Sacrifice grammar for concision.
-**YAGNI, KISS, DRY** principles apply.
-
-## Workflow
-
-### 1. Git Init
-- Check if Git initialized, if not: use `git-manager` (main branch)
-
-### 2. Research
-- Use max 2 `researcher` agents 
-- Explore requirements, validation, challenges, solutions
-- Keep reports ≤150 lines
-
-### 3. Tech Stack
-- Use `planner` + multiple `researcher` agents  for best fit tech stack
-- Write to `./docs` directory (≤150 lines)
-
-### 4. Wireframe & Design
-- Use `ui-ux-designer` + `researcher` agents 
-- Research: style, trends, fonts, colors, spacing, positions
-- Describe assets for `ai-multimodal` generation
-- Create design guidelines at `./docs/design-guidelines.md`
-- Generate wireframes HTML at `./docs/wireframe`
-- Generate logo with `ai-multimodal` if needed
-- Screenshot with `chrome-devtools` → save to `./docs/wireframes/`
-- Ask user to approve (repeat if rejected)
-
-### 5. Parallel Planning & Implementation
-- Trigger :parallel <detailed-instruction>` for parallel-executable plan
-- Read `plan.md` for dependency graph and execution strategy
-- Launch multiple `fullstack-developer` agents  for concurrent phases
-  - Pass: phase file path, environment info
-- Use `ui-ux-designer` for frontend (generate/analyze assets with `ai-multimodal`, edit with `imagemagick`)
-- Run type checking after implementation
-
-### 6. Testing
-- Write real tests (NO fake data/mocks)
-- If fail: `debugger` → fix → repeat
-
-### 7. Code Review
-- Use `code-reviewer`
-- If critical: fix → retest → repeat
-
-### 8. Documentation
-- Use `docs-manager` to create/update:
-  - `./docs/README.md` (≤300 lines)
-  - `./docs/project-overview-pdr.md`
-  - `./`
-  - `./docs/system-architecture.md`
-- Use `project-manager` for `./docs/project-roadmap.md`
-
-### 9. Onboarding
-- Guide user to get started (1 question at a time)
-- Help configure (API keys, env vars, etc.)
-
-### 10. Final Report
-- Summary, guide, next steps
-- Ask to commit (use `git-manager` if yes)

package/templates/repo/.github/prompts/ck-bootstrap-auto.prompt.md

@@ -1,114 +0,0 @@
----
-agent: 'agent'
-description: 'Bootstrap a new project automatically'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
----
-
-**Ultrathink** to plan & bootstrap a new project follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules in your `CLAUDE.md` file:
-
-**IMPORTANT:** Activate needed skills automatically.
-
----
-
-## User's Objectives & Requirements
-
-<user-requirements>${input}</user-requirements>
-
----
-
-## Role Responsibilities
-
-- You are an elite software engineering expert who specializes in system architecture design and technical decision-making. 
-- Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs, then collaborate with your  implement the plan.
-- You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
-
-- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-
----
-
-## Your Approach
-
-1. **Brutal Honesty**: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.
-
-2. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
-
----
-
-## Workflow:
-
-Follow strictly these following steps:
-
-**First thing first:** check if Git has been initialized, if not, initialize it .
-
-### Research
-
-* explore the user's request, idea validation, challenges, and find the best possible solutions.
-* Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-### Tech Stack
-
-1. find a best fit tech stack for this project, keeping research reports within the ≤150 lines limit.
-2. Write the tech stack down in `./docs` directory
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-### Wireframe & Design
-
-* create a design plan that follows the progressive disclosure structure:
-  - Create a directory using naming pattern from `## Naming` section.
-  - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
-  - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
-* Keep related research reports within the ≤150 lines limit.
-   - **Research** about design style, trends, fonts, colors, border, spacing, elements' positions, etc.
-   - Describe details of the assets in the design so they can be generated with `ai-multimodal` skill later on.
-   - **IMPORTANT:** Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use **Inter** or **Poppins** fonts.
-* Then create the design guidelines at `./docs/design-guidelines.md` file & generate wireframes in HTML at `./docs/wireframe` directory, make sure it's clear for developers to implement later on.
-* If there are no logo provided, 
-* /docs/wireframes/` directory.
-* Ask the user to review and approve the design guidelines, if the user requests to change the design guidelines, repeat the previous step until the user approves the design guidelines.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-### Implementation
-
-* Use `general agent (main agent)` to implement the plan step by step, follow the implementation plan in `.s` directory.
-* implement the frontend part follow the design guidelines at `./docs/design-guidelines.md` file.
-  * Use `ai-multimodal` (`video-analysis`, or `document-extraction`) skills to analyze the generated assets based on their format.
-  * Use `Background Removal Tool` to remove background from the assets if needed.
-  * Use `ai-multimodal` (`image-generation`) skill to edit the assets if needed.
-* Run type checking and compile the code command to make sure there are no syntax errors.
-
-### Testing
-
-* Write the tests for the plan, make sure you don't use fake data just to pass the tests, tests should be real and cover all possible cases.
-* run the tests, make sure it works, .
-* If there are issues or failed tests, find the root cause of the issues, then ask main agent to fix all of them and 
-* Repeat the process until all tests pass or no more issues are reported. Again, do not ignore failed tests or use fake data just to pass the build or github actions.
-
-### Code Review
-
-* After finishing, review code. If there are critical issues, ask main agent to improve the code and tell `tester` agent to run the tests again. Repeat the process until all tests pass.
-* When all tests pass, code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-### Documentation
-
-* update the docs if needed.
-  * Create/update `./docs/README.md` file (keep it concise and under 300 lines).
-  * Create/update `./docs/project-overview.-pdr.md` (Product Development Requirements) file.
-  * Create/update `./` file.
-  * Create/update `./docs/system-architecture.md` file.
-* create a project roadmap at `./docs/project-roadmap.md` file.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-### Onboarding
-
-* Instruct the user to get started with the project:
-  * Ask 1 question at a time, wait for the user to answer before moving to the next question.
-  * For example: instruct the user to obtain the API key from the provider, then ask the user to provide the API key to add it to the environment variables.
-* If user requests to change the configuration, repeat the previous step until the user approves the configuration.
-
-### Final Report
-* Report back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.
-* Ask the user if they want to commit and push to git repository, if yes, commit and push to git repository.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.

package/templates/repo/.github/prompts/ck-ck-help.prompt.md

@@ -1,114 +0,0 @@
----
-agent: 'agent'
-description: 'ClaudeKit usage guide - just type naturally'
-tools: ['search/codebase']
----
-
-Think harder.
-All-in-one ClaudeKit guide. Run the script and present output based on type markers.
-
-## Pre-Processing
-
-**IMPORTANT: Always translate `${input}` to English before passing to script.**
-
-The Python script only understands English keywords. If `${input}` is in another language:
-1. Translate `${input}` to English
-2. Pass the translated English string to the script
-
-## Execution
-
-```bash
-python ~/.claude/scripts/ck_help.py "${input}"
-```
-
-## Output Type Detection
-
-The script outputs a type marker on the first line: `@CK_OUTPUT_TYPE:<type>`
-
-**Read this marker and adjust your presentation accordingly:**
-
-### `@CK_OUTPUT_TYPE:comprehensive-docs`
-
-Full documentation (config, schema, setup guides).
-
-**Presentation:**
-1. Show the **COMPLETE** script output verbatim - every section, every code block
-2. **THEN ADD** helpful context:
-   - Real-world usage examples ("For example, if you're working on multiple projects...")
-   - Common gotchas and tips ("Watch out for: ...")
-   - Practical scenarios ("This is useful when...")
-3. End with a specific follow-up question
-
-**Example enhancement after showing full output:**
-```
-## Additional Tips
-
-**When to use global vs local config:**
-- Use global ( for personal preferences like language, issue prefix style
-- Use local ( for project-specific paths, naming conventions
-
-**Common setup for teams:**
-Each team member sets their locale globally, but projects share local config via git.
-
-Need help setting up a specific configuration?
-```
-
-### `@CK_OUTPUT_TYPE:category-guide`
-
-Workflow guides for command categories (fix, plan, cook, etc.).
-
-**Presentation:**
-1. Show the complete workflow and command list
-2. **ADD** practical context:
-   - When to use this workflow vs alternatives
-   - Real example: "If you encounter a bug in authentication, start with..."
-   - Transition tips between commands
-3. Offer to help with a specific task
-
-### `@CK_OUTPUT_TYPE:command-details`
-
-Single command documentation.
-
-**Presentation:**
-1. Show full command info from script
-2. **ADD**:
-   - Concrete usage example with realistic input
-   - When this command shines vs alternatives
-   - Common flags or variations
-3. Offer to run the command for them
-
-### `@CK_OUTPUT_TYPE:search-results`
-
-Search matches for a keyword.
-
-**Presentation:**
-1. Show all matches from script
-2. **HELP** user navigate:
-   - Group by relevance if many results
-   - Suggest most likely match based on context
-   - Offer to explain any specific command
-3. Ask what they're trying to accomplish
-
-### `@CK_OUTPUT_TYPE:task-recommendations`
-
-Task-based command suggestions.
-
-**Presentation:**
-1. Show recommended commands from script
-2. **EXPLAIN** the reasoning:
-   - Why these commands fit the task
-   - Suggested order of execution
-   - What each step accomplishes
-3. Offer to start with the first recommended command
-
-## Key Principle
-
-**Script output = foundation. Your additions = value-add.**
-
-Never replace or summarize the script output. Always show it fully, then enhance with your knowledge and context.
-
-## Important: Correct Workflows
-
-- ** → **: Plan first, then execute the plan
-- **`/cook`**: Standalone - plans internally, no separate  needed
-- **NEVER** suggest  → `/cook` (cook has its own planning)

package/templates/repo/.github/prompts/ck-code-auto.prompt.md

@@ -1,172 +0,0 @@
----
-agent: 'agent'
-description: '[AUTO] Start coding & testing an existing plan ("trust me bro")'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
----
-
-**MUST READ** `CLAUDE.md` then **THINK HARDER** to start working on the following plan follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules:
-<plan>${input}</plan>
-
-## Arguments
-- $PLAN: $1 (Mention specific plan or auto detected, default: latest plan)
-- $ALL_PHASES: $2 (`Yest` to finish all phases in one run or `No` to implement phase-by-phase and wait for confirmation, default is `Yes`)
-
----
-
-## 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 `$PLAN` 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 `$PLAN` 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-5 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:**
-`project-manager` agent must respond back with:
-- Initialize `TodoWrite` with `Step 0: [Plan Name] - [Phase Name]` and all command steps (Step 1 through Step 5)
-- 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 in `media-processing` skill 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: Finalize
-
-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.
-- If this is the last phase: ask if user wants to set up onboarding requirements.
-
-3. **AUTO-COMMIT (after steps 1 and 2 completes):**
-- **Call**  to handle git operation.
-- Run only if: Steps 1 and 2 successful + 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 5 complete in `TodoWrite`.
-
-**Important:**
-If $ALL_PHASES is `Yes`, proceed to the next phase automatically.
-If $ALL_PHASES is `No`, wait for user confirmation before proceeding to the next phase:
-- Ask if user wants to proceed to the next phase: "**Phase workflow finished. Ready for next plan phase.**"
-
-## Summary report
-If this is the last phase, generate a concise summary report.
-Ask these questions:
-- If user wants to preview the report with `/preview` .
-- If user wants to archive the plan with :archive` .
-
----
-
-## 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: 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 5: `project-manager` AND `docs-manager` AND `git-manager`
-
-**Blocking gates:**
-- Step 3: Tests must be 100% passing
-- Step 4: Critical issues must be 0
-
-**REMEMBER:**
-- Do not skip steps. Do not proceed if validation fails.
-- 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.