cokit-cli 1.2.6 → 1.3.0

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

@@ -139,4 +139,3 @@ Never replace or summarize the script output. Always show it fully, then enhance
 | `/ck-brainstorm` | Explore ideas |
 | `/ck-plan` | Create plan |
 | `/ck-cook` | Implement feature |
-| `/ck-spec-specify` | Write detailed feature spec |

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

@@ -89,7 +89,6 @@ This reminder is **NON-NEGOTIABLE** - always output it after presenting the plan
 
 ## Important Notes
 - **IMPORTANT:** Ensure token consumption efficiency while maintaining high quality.
-- **IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
 - **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
 - **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
 - **IMPORTANT**: **Do not** start implementing.
@@ -100,8 +99,6 @@ This reminder is **NON-NEGOTIABLE** - always output it after presenting the plan
 
 | Command | Description |
 |---------|-------------|
-| `/ck-spec-tasks` | Break plan into actionable tasks |
 | `/ck-cook` | Implement plan |
 | `/ck-test` | Run tests and analyze results |
 | `/ck-fix` | Analyze and fix issues |
-| `/ck-spec-specify` | Too complex? Switch to spec-driven flow |

package/templates/repo/.github/prompts/ck-plan-hard.prompt.md

@@ -115,7 +115,6 @@ This reminder is **NON-NEGOTIABLE** when validation is skipped.
 - For each phase, create `{plan-dir}/phase-XX-phase-name-here.md` containing the following sections in order: Context links (reference parent plan, dependencies, docs), Overview (date, description, priority, implementation status, review status), Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps.
 
 ## Important Notes
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
 **IMPORTANT:** Ensure token efficiency while maintaining high quality.
 **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
 **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
@@ -127,8 +126,6 @@ This reminder is **NON-NEGOTIABLE** when validation is skipped.
 
 | Command | Description |
 |---------|-------------|
-| `/ck-spec-tasks` | Break plan into actionable tasks |
 | `/ck-cook` | Implement plan |
 | `/ck-test` | Run tests and analyze results |
 | `/ck-fix` | Analyze and fix issues |
-| `/ck-spec-specify` | Need formal spec? Switch to spec-driven flow |

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

@@ -56,7 +56,6 @@ If user chooses validation or mode is `auto`: Execute `/ck-plan-validate {plan-p
 - Hard plans recommend validation
 
 ## Important Notes
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
 **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
 **IMPORTANT:** Ensure token efficiency while maintaining high quality.
 **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
@@ -69,8 +68,6 @@ If user chooses validation or mode is `auto`: Execute `/ck-plan-validate {plan-p
 | Command | Description |
 |---------|-------------|
 | `/ck-plan-validate` | Validate plan with critical questions |
-| `/ck-spec-tasks` | Break plan into actionable tasks |
 | `/ck-cook` | Implement plan |
 | `/ck-test` | Run tests and analyze results |
 | `/ck-fix` | Analyze and fix issues |
-| `/ck-spec-specify` | Need detailed spec first? Start spec-driven flow |

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

@@ -0,0 +1,20 @@
+---
+agent: 'agent'
+description: 'Track progress, manage tasks, generate reports'
+argument-hint: '[status|hydrate|sync|report]'
+---
+
+## Context
+Project management task:
+<task>${input}</task>
+
+Track progress, update plan statuses, generate reports, coordinate docs updates.
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck-plan` | Create implementation plan |
+| `/ck-cook` | Implement features |

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

@@ -19,8 +19,6 @@ Think harder to scan the codebase and analyze it follow the Orchestration Protoc
 
 ## Workflow:
 
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
-
 ### Research
 
 * Use 2 `researcher` agents in parallel to search up to max 5 sources for the user's request, idea validation, best practices, challenges, and find the best possible solutions.
@@ -55,4 +53,3 @@ Think harder to scan the codebase and analyze it follow the Orchestration Protoc
 |---------|-------------|
 | `/ck-fix` | Fix issues found in review |
 | `/ck-git` | Commit changes |
-| `/ck-spec-checklist` | Validate against spec requirements |

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

@@ -82,4 +82,3 @@ Search the codebase with a wide range of patterns:
 | `/ck-plan` | Create implementation plan |
 | `/ck-cook` | Implement feature |
 | `/ck-ask` | Ask technical questions |
-| `/ck-spec-analyze` | Cross-artifact consistency check |

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

@@ -0,0 +1,22 @@
+---
+agent: 'agent'
+description: 'STRIDE + OWASP security audit'
+argument-hint: '<scope glob or full> [--fix] [--iterations N]'
+---
+
+## Context
+Security audit scope:
+<scope>${input}</scope>
+
+Run a STRIDE + OWASP-based security audit. Scans code for vulnerabilities, categorizes by severity, and can iteratively fix findings.
+
+**IMPORTANT**: Report all findings with severity levels before applying fixes.
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck-fix` | Fix security issues found |
+| `/ck-review` | Review security fixes |

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

@@ -0,0 +1,22 @@
+---
+agent: 'agent'
+description: 'Ship pipeline: test, review, commit, push, PR'
+argument-hint: '[official|beta] [--skip-tests] [--skip-review] [--dry-run]'
+---
+
+## Context
+Ship target:
+<target>${input}</target>
+
+Ship pipeline: merge main, test, review, commit, push, PR. Single command from feature branch to PR URL.
+
+**IMPORTANT**: Follow the ship skill workflow steps precisely.
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck-test` | Run tests and analyze results |
+| `/ck-review` | Scan and analyze codebase |

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

@@ -7,7 +7,6 @@ tools: ['execute/runInTerminal', 'execute/getTerminalOutput', 'execute/runTests'
 Use the `tester` agent to run tests locally and analyze the summary report.
 
 **IMPORTANT**: **Do not** start implementing.
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
 
 ---
 
@@ -18,4 +17,3 @@ Use the `tester` agent to run tests locally and analyze the summary report.
 | `/ck-fix` | Analyze and fix issues |
 | `/ck-review` | Scan and analyze codebase |
 | `/ck-git` | Commit changes |
-| `/ck-spec-checklist` | Validate against spec requirements |

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

@@ -18,4 +18,3 @@ Analyze the overall impact and quality of the changes.
 | `/ck-brainstorm` | Explore ideas |
 | `/ck-plan` | Create plan |
 | `/ck-cook` | Implement feature |
-| `/ck-spec-specify` | Write detailed feature spec |

package/templates/repo/.github/skills/agent-browser/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: agent-browser
 description: AI-optimized browser automation CLI with context-efficient snapshots. Use for long autonomous sessions, self-verifying workflows, video recording, and cloud browser testing (Browserbase).
+license: Apache-2.0
+argument-hint: "[url or task]"
 ---
 
 # agent-browser Skill
@@ -43,15 +45,16 @@ agent-browser click @e1
 agent-browser snapshot -i
 ```
 
-## When to Use
+## When to Use (vs chrome-devtools)
 
-Best for:
-- Long autonomous AI sessions (context-efficient snapshots)
-- Self-verifying workflows and build loops
-- Video recording for debugging
-- Cloud browsers (Browserbase) for CI/CD
-- Multi-tab handling
-- Form automation and testing
+| Use agent-browser | Use chrome-devtools |
+|-------------------|---------------------|
+| Long autonomous AI sessions | Quick one-off screenshots |
+| Context-constrained workflows | Custom Puppeteer scripts needed |
+| Video recording for debugging | WebSocket full frame debugging |
+| Cloud browsers (Browserbase) | Existing workflow integration |
+| Multi-tab handling | Need Sharp auto-compression |
+| Self-verifying build loops | Session with auth injection |
 
 **Token efficiency:** ~280 chars/snapshot vs 8K+ for Playwright MCP.
 

package/templates/repo/.github/skills/agent-browser/references/agent-browser-vs-chrome-devtools.md

@@ -0,0 +1,112 @@
+# agent-browser vs chrome-devtools
+
+Detailed comparison guide for choosing between browser automation skills.
+
+## Feature Comparison
+
+| Feature | agent-browser | chrome-devtools |
+|---------|---------------|-----------------|
+| **Engine** | Playwright (via Rust CLI) | Puppeteer |
+| **Refs system** | `@e1` inline | `[ref=e1]` YAML |
+| **Session persistence** | Named sessions (`--session`) | `.browser-session.json` |
+| **Screenshot** | Basic | Auto-compress >5MB (Sharp) |
+| **Network intercept** | `route` command | `network.js` script |
+| **Console capture** | Basic | With filtering |
+| **WebSocket debug** | Limited | Full frames support |
+| **Video recording** | Built-in `record` | Not available |
+| **PDF export** | Built-in `pdf` | Via Puppeteer API |
+| **Auth persistence** | `state save/load` | `inject-auth.js` |
+| **Multi-tab** | Full support | Limited |
+| **Cloud browsers** | Browserbase native | Manual setup |
+| **Performance** | Rust CLI (fast) | Node.js |
+| **Custom scripts** | None (CLI only) | 20+ utilities |
+
+## Token Efficiency Benchmarks
+
+| Metric | agent-browser | chrome-devtools | Playwright MCP |
+|--------|---------------|-----------------|----------------|
+| Homepage snapshot | ~280 chars | ~300-500 chars | ~8,247 chars |
+| Context reduction | 93% vs MCP | 90% vs MCP | Baseline |
+| Tool definitions | ~2K tokens | 0 (CLI scripts) | ~17K tokens |
+
+**Conclusion:** Both agent-browser and chrome-devtools are similarly efficient. Both dramatically outperform Playwright MCP.
+
+## Use Case Decision Tree
+
+```
+Need browser automation?
+|
++-- Long autonomous AI session?
+|   +-- YES --> agent-browser (better context efficiency)
+|   +-- NO --> Continue
+|
++-- Need video recording?
+|   +-- YES --> agent-browser (built-in)
+|   +-- NO --> Continue
+|
++-- Cloud browser (CI/CD)?
+|   +-- YES --> agent-browser (Browserbase native)
+|   +-- NO --> Continue
+|
++-- Custom Puppeteer scripts?
+|   +-- YES --> chrome-devtools (20+ utilities)
+|   +-- NO --> Continue
+|
++-- WebSocket debugging?
+|   +-- YES --> chrome-devtools (full frames)
+|   +-- NO --> Continue
+|
++-- Screenshot auto-compression?
+|   +-- YES --> chrome-devtools (Sharp)
+|   +-- NO --> agent-browser OR chrome-devtools
+```
+
+## Parallel Usage Patterns
+
+Both skills can coexist - use the right tool for each task:
+
+```bash
+# Quick screenshot with compression -> chrome-devtools
+node "$SKILL_DIR/screenshot.js" --url https://example.com --output ss.png
+
+# Long autonomous session -> agent-browser
+agent-browser --session test1 open https://example.com
+agent-browser snapshot -i
+# ... many interactions ...
+agent-browser close
+```
+
+## Migration Guide
+
+### From chrome-devtools to agent-browser
+
+| chrome-devtools | agent-browser |
+|-----------------|---------------|
+| `node navigate.js --url X` | `agent-browser open X` |
+| `node aria-snapshot.js --url X` | `agent-browser open X && agent-browser snapshot -i` |
+| `node select-ref.js --ref e5 --action click` | `agent-browser click @e5` |
+| `node fill.js --selector "#email" --value "X"` | `agent-browser fill @e1 "X"` |
+| `node screenshot.js --output X.png` | `agent-browser screenshot -o X.png` |
+| `node console.js --types error` | No direct equivalent |
+| `node network.js` | No direct equivalent |
+
+### Key Differences
+
+1. **Refs format:** `[ref=e5]` vs `@e5`
+2. **Session:** File-based vs named sessions
+3. **Commands:** Node scripts vs CLI commands
+4. **Output:** JSON always vs JSON with `--json` flag
+
+## When to Switch
+
+**Switch to agent-browser when:**
+- Starting new long-running automation
+- Need video recording capability
+- Moving to cloud browsers (Browserbase)
+- Want simpler CLI syntax
+
+**Keep chrome-devtools when:**
+- Existing workflows depend on custom scripts
+- Need WebSocket full-frame debugging
+- Need automatic screenshot compression
+- Need fine-grained console log filtering

package/templates/repo/.github/skills/bootstrap/SKILL.md

@@ -0,0 +1,102 @@
+---
+name: bootstrap
+description: "Bootstrap new projects with research, tech stack, design, planning, and implementation. Modes: full (interactive), auto (default), fast (skip research), parallel (multi-agent)."
+license: MIT
+argument-hint: "[requirements] [--full|--auto|--fast|--parallel]"
+---
+
+# Bootstrap - New Project Scaffolding
+
+End-to-end project bootstrapping from idea to running code.
+
+**Principles:** YAGNI, KISS, DRY | Token efficiency | Concise reports
+
+## Usage
+
+```
+/ck-bootstrap <user-requirements>
+```
+
+**Flags** (optional, default `--auto`):
+
+| Flag | Mode | Thinking | User Gates | Planning Skill | Cook Skill |
+|------|------|----------|------------|----------------|------------|
+| `--full` | Full interactive | Ultrathink | Every phase | `--hard` | (interactive) |
+| `--auto` | Automatic | Ultrathink | Design only | `--auto` | `--auto` |
+| `--fast` | Quick | Think hard | None | `--fast` | `--auto` |
+| `--parallel` | Multi-agent | Ultrathink | Design only | `--parallel` | `--parallel` |
+
+**Example:**
+```
+/ck-bootstrap "Build a SaaS dashboard with auth" --fast
+/ck-bootstrap "E-commerce platform with Stripe" --parallel
+```
+
+## Workflow Overview
+
+```
+[Git Init] → [Research?] → [Tech Stack?] → [Design?] → [Planning] → [Implementation] → [Test] → [Review] → [Docs] → [Onboard] → [Final]
+```
+
+Each mode loads a specific workflow reference + shared phases.
+
+## Mode Detection
+
+If no flag provided, default to `--auto`.
+
+Load the appropriate workflow reference:
+- `--full`: Load `references/workflow-full.md`
+- `--auto`: Load `references/workflow-auto.md`
+- `--fast`: Load `references/workflow-fast.md`
+- `--parallel`: Load `references/workflow-parallel.md`
+
+All modes share: Load `references/shared-phases.md` for implementation through final report.
+
+## Step 0: Git Init (ALL modes)
+
+Check if Git initialized. If not:
+- `--full`: Ask user if they want to init → `git-manager` subagent (`main` branch)
+- Others: Auto-init via `git-manager` subagent (`main` branch)
+
+## Skill Triggers (MANDATORY)
+
+After early phases (research, tech stack, design), trigger downstream skills:
+
+### Planning Phase
+Activate **plan** skill with mode-appropriate flag:
+- `--full` → `/ck-plan --hard <requirements>` (thorough research + validation)
+- `--auto` → `/ck-plan --auto <requirements>` (auto-detect complexity)
+- `--fast` → `/ck-plan --fast <requirements>` (skip research)
+- `--parallel` → `/ck-plan --parallel <requirements>` (file ownership + dependency graph)
+
+Planning skill outputs a plan path. Pass this to cook.
+
+### Implementation Phase
+Activate **cook** skill with the plan path and mode-appropriate flag:
+- `--full` → `/ck-cook <plan-path>` (interactive review gates)
+- `--auto` → `/ck-cook --auto <plan-path>` (skip review gates)
+- `--fast` → `/ck-cook --auto <plan-path>` (skip review gates)
+- `--parallel` → `/ck-cook --parallel <plan-path>` (multi-agent execution)
+
+## Role
+
+Elite software engineering expert specializing in system architecture and technical decisions. Brutally honest about feasibility and trade-offs.
+
+## Critical Rules
+
+- Activate relevant skills from catalog during the process
+- Keep all research reports ≤150 lines
+- All docs written to `./docs` directory
+- Plans written to `./plans` directory using naming from `## Naming` section
+- DO NOT implement code directly — delegate through planning + cook skills
+- Sacrifice grammar for concision in reports
+- List unresolved questions at end of reports
+- Run `/ck-journal` to write a concise technical journal entry upon completion
+
+## References
+
+- `references/workflow-full.md` - Full interactive workflow
+- `references/workflow-auto.md` - Auto workflow (default)
+- `references/workflow-fast.md` - Fast workflow
+- `references/workflow-parallel.md` - Parallel workflow
+- `references/shared-phases.md` - Common phases (implementation → final report)

package/templates/repo/.github/skills/bootstrap/references/shared-phases.md

@@ -0,0 +1,59 @@
+# Shared Phases (All Modes)
+
+These phases apply after planning is complete and cook skill is activated.
+Cook skill handles most of these — this reference documents bootstrap-specific guidance.
+
+## Implementation
+
+Handled by **cook** skill. Bootstrap-specific notes:
+- Use main agent to implement step by step per plan in `./plans`
+- Use `ui-ux-designer` subagent for frontend per `./docs/design-guidelines.md`
+- Asset pipeline: `ai-multimodal` (if available) (generate/analyze) → `imagemagick` (crop/resize) → background removal if needed
+- Run type checking and compile after each phase
+
+## Testing
+
+Handled by **cook** skill. Bootstrap-specific notes:
+- Write real tests — NO fake data, mocks, cheats, tricks, temporary solutions
+- `tester` subagent runs tests → report to main agent
+- If failures: `debugger` subagent → fix → repeat until all pass
+- DO NOT ignore failed tests to pass build/CI
+
+## Code Review
+
+Handled by **cook** skill. Bootstrap-specific notes:
+- `code-reviewer` subagent reviews code
+- If critical issues: fix → retest → repeat
+- Report summary to user when all tests pass and code reviewed
+
+## Documentation
+
+After code review passes. Use `docs-manager` subagent to create/update:
+- `./docs/README.md` (≤300 lines)
+- `./docs/codebase-summary.md`
+- `./docs/project-overview-pdr.md` (Product Development Requirements)
+- `./docs/code-standards.md`
+- `./docs/system-architecture.md`
+
+Use `project-manager` subagent to create:
+- `./docs/project-roadmap.md`
+- Update plan/phase status to complete
+
+## Onboarding
+
+Guide user to get started with the project:
+- Ask 1 question at a time, wait for answer before next
+- Example: instruct user to obtain API key → ask for key → add to env vars
+- If user requests config changes, repeat until approved
+
+## Final Report
+
+1. Summary of all changes, brief explanations
+2. Guide user to get started + suggest next steps
+3. Ask user if they want to commit/push:
+   - If yes: `git-manager` subagent to commit (and push if requested)
+   - `--fast` mode: auto-commit (no push) without asking
+
+**Report rules:**
+- Sacrifice grammar for concision
+- List unresolved questions at end, if any

package/templates/repo/.github/skills/bootstrap/references/workflow-auto.md

@@ -0,0 +1,52 @@
+# Auto Workflow (`--auto`) — Default
+
+**Thinking level:** Ultrathink
+**User gates:** Design approval only. All other phases proceed automatically.
+
+## Step 1: Research
+
+Spawn multiple `researcher` subagents in parallel:
+- Explore request, idea validation, challenges, best solutions
+- Keep every report ≤150 lines
+
+No user gate — proceed automatically.
+
+## Step 2: Tech Stack
+
+1. Use `planner` + multiple `researcher` subagents in parallel for best-fit stack
+2. Write tech stack to `./docs` directory
+
+No user gate — auto-select best option.
+
+## Step 3: Wireframe & Design
+
+1. Use `ui-ux-designer` + `researcher` subagents in parallel:
+   - Research style, trends, fonts (predict Google Fonts name, NOT just Inter/Poppins), colors, spacing, positions
+   - Describe assets for `ai-multimodal` (if available) skill generation
+2. `ui-ux-designer` creates:
+   - Design guidelines at `./docs/design-guidelines.md`
+   - Wireframes in HTML at `./docs/wireframe/`
+3. If no logo provided: generate with `ai-multimodal` (if available) skill
+4. Screenshot wireframes with `chrome-devtools` (if available) → save to `./docs/wireframes/`
+
+**Gate:** Ask user to approve design. Repeat if rejected.
+
+**Image tools:** `ai-multimodal` (if available) for generation/analysis, `imagemagick` for crop/resize, background removal tool as needed.
+
+## Step 4: Planning
+
+Activate **plan** skill: `/ck-plan --auto <requirements>`
+- Planning skill auto-detects complexity and picks appropriate mode
+- Creates plan directory using `## Naming` pattern
+- Overview at `plan.md` (<80 lines) + `phase-XX-*.md` files
+
+No user gate — proceed to implementation.
+
+## Step 5: Implementation → Final Report
+
+Load `references/shared-phases.md` for remaining phases.
+
+Activate **cook** skill: `/ck-cook --auto <plan-path>`
+- Skips all review gates
+- Auto-approves if score≥9.5 and 0 critical issues
+- Continues through all phases without stopping

package/templates/repo/.github/skills/bootstrap/references/workflow-fast.md

@@ -0,0 +1,50 @@
+# Fast Workflow (`--fast`)
+
+**Thinking level:** Think hard
+**User gates:** None. Fully autonomous from start to finish.
+
+## Step 1: Combined Research & Planning
+
+All research happens in parallel, then feeds into planning:
+
+**Parallel research batch** (spawn these simultaneously):
+- 2 `researcher` subagents (max 5 sources each): explore request, validate idea, find solutions
+- 2 `researcher` subagents (max 5 sources each): find best-fit tech stack
+- 2 `researcher` subagents (max 5 sources each): research design style, trends, fonts, colors, spacing, positions
+  - Predict Google Fonts name (NOT just Inter/Poppins)
+  - Describe assets for `ai-multimodal` (if available) generation
+
+Keep all reports ≤150 lines.
+
+## Step 2: Design
+
+1. `ui-ux-designer` subagent analyzes research, creates:
+   - Design guidelines at `./docs/design-guidelines.md`
+   - Wireframes in HTML at `./docs/wireframe/`
+2. If no logo provided: generate with `ai-multimodal` (if available) skill
+3. Screenshot wireframes with `chrome-devtools` (if available) → save to `./docs/wireframes/`
+
+**Image tools:** `ai-multimodal` (if available) for generation/analysis, `imagemagick` for crop/resize, background removal tool as needed.
+
+No user gate — proceed directly.
+
+## Step 3: Planning
+
+Activate **plan** skill: `/ck-plan --fast <requirements>`
+- Skip research (already done above)
+- Read codebase docs → create plan directly
+- Plan directory using `## Naming` pattern
+- Overview at `plan.md` (<80 lines) + `phase-XX-*.md` files
+
+No user gate — proceed to implementation.
+
+## Step 4: Implementation → Final Report
+
+Load `references/shared-phases.md` for remaining phases.
+
+Activate **cook** skill: `/ck-cook --auto <plan-path>`
+- Skips all review gates (fast planning pairs with fast execution)
+- Auto-approves if score≥9.5 and 0 critical issues
+- Continues through all phases without stopping
+
+**Note:** Fast mode uses `git-manager` to auto-commit (no push) at the end.

package/templates/repo/.github/skills/bootstrap/references/workflow-full.md

@@ -0,0 +1,60 @@
+# Full Interactive Workflow (`--full`)
+
+**Thinking level:** Ultrathink
+**User gates:** Every major phase requires user approval before proceeding.
+
+## Step 1: Clarify Requirements
+
+Use asking the user to probe user's request, constraints, true objectives.
+- Ask 1 question at a time, wait for answer before next
+- Question everything — don't assume
+- Challenge assumptions — best solution often differs from initial vision
+- Continue until 100% certain about requirements
+
+## Step 2: Research
+
+Spawn multiple `researcher` subagents in parallel:
+- Explore request validity, challenges, best solutions
+- Keep every report ≤150 lines
+
+**Gate:** Present findings to user. Proceed only with approval.
+
+## Step 3: Tech Stack
+
+1. Ask user for preferred tech stack. If provided, skip to step 4.
+2. Use `planner` + multiple `researcher` subagents in parallel to find best-fit stack
+3. Present 2-3 options with pros/cons by asking the user
+4. Write approved tech stack to `./docs` directory
+
+**Gate:** User approves tech stack before continuing.
+
+## Step 4: Wireframe & Design
+
+1. Ask user if they want wireframes/design. If no → skip to Step 5.
+2. Use `ui-ux-designer` + `researcher` subagents in parallel:
+   - Research style, trends, fonts (predict Google Fonts name, NOT just Inter/Poppins), colors, spacing, positions
+   - Describe assets for `ai-multimodal` (if available) skill generation
+3. `ui-ux-designer` creates:
+   - Design guidelines at `./docs/design-guidelines.md`
+   - Wireframes in HTML at `./docs/wireframe/`
+4. If no logo provided: generate with `ai-multimodal` (if available) skill
+5. Screenshot wireframes with `chrome-devtools` (if available) → save to `./docs/wireframes/`
+
+**Gate:** User approves design. Repeat if rejected.
+
+**Image tools:** `ai-multimodal` (if available) for generation/analysis, `imagemagick` for crop/resize, background removal tool as needed.
+
+## Step 5: Planning
+
+Activate **plan** skill: `/ck-plan --hard <requirements>`
+- Planner creates directory using `## Naming` pattern
+- Overview at `plan.md` (<80 lines) + `phase-XX-*.md` files
+- Present pros/cons of plan
+
+**Gate:** User approves plan. DO NOT start implementing without approval.
+
+## Step 6: Implementation → Final Report
+
+Load `references/shared-phases.md` for remaining phases.
+
+Activate **cook** skill: `/ck-cook <plan-path>` (interactive mode — review gates at each step)