Best use case
ck:cook is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
ALWAYS activate this skill before implementing EVERY feature, plan, or fix.
Teams using ck:cook should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cook/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ck:cook Compares
| Feature / Agent | ck:cook | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
ALWAYS activate this skill before implementing EVERY feature, plan, or fix.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Cook - Smart Feature Implementation End-to-end implementation with automatic workflow detection. **Principles:** YAGNI, KISS, DRY | Token efficiency | Concise reports ## Usage ``` /cook <natural language task OR plan path> ``` **IMPORTANT:** If no flag is provided, the skill will use the `interactive` mode by default for the workflow. **Optional flags to select the workflow mode:** - `--interactive`: Full workflow with user input (**default**) - `--fast`: Skip research, scout→plan→code - `--parallel`: Multi-agent execution - `--no-test`: Skip testing step - `--auto`: Auto-approve all steps **Example:** ``` /cook "Add user authentication to the app" --fast /cook path/to/plan.md --auto ``` ## Smart Intent Detection | Input Pattern | Detected Mode | Behavior | |---------------|---------------|----------| | Path to `plan.md` or `phase-*.md` | code | Execute existing plan | | Contains "fast", "quick" | fast | Skip research, scout→plan→code | | Contains "trust me", "auto" | auto | Auto-approve all steps | | Lists 3+ features OR "parallel" | parallel | Multi-agent execution | | Contains "no test", "skip test" | no-test | Skip testing step | | Default | interactive | Full workflow with user input | See `references/intent-detection.md` for detection logic. ## Workflow Overview ``` [Intent Detection] → [Research?] → [Review] → [Plan] → [Review] → [Implement] → [Review] → [Test?] → [Review] → [Finalize] ``` **Default (non-auto):** Stops at `[Review]` gates for human approval before each major step. **Auto mode (`--auto`):** Skips human review gates, implements all phases continuously. **Claude Tasks:** Utilize all these tools `TaskCreate`, `TaskUpdate`, `TaskGet` and `TaskList` during implementation step. | Mode | Research | Testing | Review Gates | Phase Progression | |------|----------|---------|--------------|-------------------| | interactive | ✓ | ✓ | **User approval at each step** | One at a time | | auto | ✓ | ✓ | Auto if score≥9.5 | All at once (no stops) | | fast | ✗ | ✓ | **User approval at each step** | One at a time | | parallel | Optional | ✓ | **User approval at each step** | Parallel groups | | no-test | ✓ | ✗ | **User approval at each step** | One at a time | | code | ✗ | ✓ | **User approval at each step** | Per plan | ## Step Output Format ``` ✓ Step [N]: [Brief status] - [Key metrics] ``` ## Blocking Gates (Non-Auto Mode) Human review required at these checkpoints (skipped with `--auto`): - **Post-Research:** Review findings before planning - **Post-Plan:** Approve plan before implementation - **Post-Implementation:** Approve code before testing - **Post-Testing:** 100% pass + approve before finalize **Always enforced (all modes):** - **Testing:** 100% pass required (unless no-test mode) - **Code Review:** User approval OR auto-approve (score≥9.5, 0 critical) - **Finalize (MANDATORY - never skip):** 1. `project-manager` subagent → run full plan sync-back (all completed tasks/steps across all `phase-XX-*.md`, not only current phase), then update `plan.md` status/progress 2. `docs-manager` subagent → update `./docs` if changes warrant 3. `TaskUpdate` → mark all Claude Tasks complete after sync-back verification 4. Ask user if they want to commit via `git-manager` subagent ## Required Subagents (MANDATORY) | Phase | Subagent | Requirement | |-------|----------|-------------| | Research | `researcher` | Optional in fast/code | | Scout | `ck:scout` | Optional in code | | Plan | `planner` | Optional in code | | UI Work | `ui-ux-designer` | If frontend work | | Testing | `tester`, `debugger` | **MUST** spawn | | Review | `code-reviewer` | **MUST** spawn | | Finalize | `project-manager`, `docs-manager`, `git-manager` | **MUST** spawn all 3 | **CRITICAL ENFORCEMENT:** - Steps 4, 5, 6 **MUST** use Task tool to spawn subagents - DO NOT implement testing, review, or finalization yourself - DELEGATE - If workflow ends with 0 Task tool calls, it is INCOMPLETE - Pattern: `Task(subagent_type="[type]", prompt="[task]", description="[brief]")` ## References - `references/intent-detection.md` - Detection rules and routing logic - `references/workflow-steps.md` - Detailed step definitions for all modes - `references/review-cycle.md` - Interactive and auto review processes - `references/subagent-patterns.md` - Subagent invocation patterns
Related Skills
ck:worktree
Create isolated git worktree for parallel development in monorepos.
ck:web-testing
Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
ck:web-frameworks
Build with Next.js (App Router, RSC, SSR, ISR), Turborepo monorepos. Use for React apps, server rendering, build optimization, caching strategies, shared dependencies.
ck:web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
ck:watzup
Review recent changes and wrap up the current work session.
ck:use-mcp
Utilize MCP server tools with intelligent discovery and execution.
ck:ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
ck:ui-styling
Style UIs with shadcn/ui components (Radix UI + Tailwind CSS). Use for accessible components, themes, dark mode, responsive layouts, design systems, color customization.
ck:threejs
Build 3D web apps with Three.js (WebGL/WebGPU). 556 searchable examples, 60 API classes, 20 use cases. Actions: create 3D scene, load model, add animation, implement physics, build VR/XR. Topics: GLTF loader, PBR materials, particle effects, shadows, post-processing, compute shaders, TSL. Integrations: WebGPU, physics engines, spatial audio.
ck:test
Run unit, integration, e2e, and UI tests. Use for test execution, coverage analysis, build verification, visual regression, and QA reports.
ck:template-skill
Replace with description of the skill and when Claude should use it.
ck:team
Orchestrate Agent Teams for parallel multi-session collaboration. Use for research, implementation, review, and debug workflows requiring independent teammates.