cook
Feature implementation orchestrator. ALWAYS use this skill for ANY code change — implement, build, add feature, create, fix bug, or any task that modifies source code. This is the default route for 70% of all requests. Runs full TDD cycle: understand → plan → test → implement → quality → verify → commit.
Rune-kit · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Rune-kit/rune --skill cookAbout this skill
name: cook description: "Feature implementation orchestrator. ALWAYS use this skill for ANY code change — implement, build, add feature, create, fix bug, or any task that modifies source code. This is the default route for 70% of all requests. Runs full TDD cycle: understand → plan → test → implement → quality → verify → commit." context: fork background: false agent: general-purpose metadata: author: runedev version: "2.7.0" layer: L1 model: sonnet group: orchestrator tools: "Read, Write, Edit, Bash, Glob, Grep" emit: phase.complete, checkpoint.request listen: plan.ready, review.complete, ideas.ready, preflight.passed, verification.complete, convergence.gaps, convergence.clean
cook
Purpose
The primary orchestrator for feature implementation. Coordinates the entire L2 mesh in a phased TDD workflow. Handles 70% of all user requests — any task that modifies source code routes through cook.
Workflow Chains (Predefined)
Cook supports predefined workflow chains for common task types. Use these as shortcuts instead of manually determining phases:
/rune cook feature → Full TDD pipeline (all phases)
/rune cook bugfix → Diagnose → fix → verify (Phase 1 → 4 → 6 → 7)
/rune cook refactor → Understand → plan → implement → quality (Phase 1 → 2 → 4 → 5 → 6 → 7)
/rune cook security → Full pipeline + sentinel@opus + sast (all phases, security-escalated)
/rune cook hotfix → Production Hotfix Protocol: contain → fix → verify → deploy → watchdog → postmortem (see below)
/rune cook nano → Trivial: do → verify → done (no phases, ≤3 steps)
/rune cook --template <name> → Load pre-built workflow template from installed Pro/Business packs
Production Hotfix Protocol
When hotfix chain is active AND triggered from a live incident (not a dev-time fix), follow the full orchestrated chain — not just fix → verify → commit.
FULL HOTFIX CHAIN (when incident is active):
1. CONTAIN → `rune:incident` (if not already running): triage + contain blast radius first
2. BRANCH → create hotfix branch via worktree (isolate from main)
3. FIX → `rune:fix` (minimal change only — no refactoring, no scope creep)
4. VERIFY → `rune:verification` (full test suite on hotfix branch)
5. SENTINEL → `rune:sentinel` (security check — fix may introduce new surface)
6. DEPLOY → `rune:deploy` (deploy hotfix to production)
7. WATCHDOG → `rune:watchdog` (confirm health check passes post-deploy)
8. POSTMORTEM → `rune:journal` + `rune:neural-memory` (capture root cause + fix pattern)
HARD-GATES:
- Do NOT skip CONTAIN if users are actively affected
- Do NOT skip SENTINEL on hotfix — rushed fixes frequently introduce new vulnerabilities
- Do NOT merge hotfix to main without VERIFY passing
- Do NOT skip POSTMORTEM — hotfix without learning = same incident next month
Minimal hotfix chain (non-incident, dev-time): Phase 4 → 6 → 7 (fix → verify → commit). User provides context, skip scout.
Template Workflows (Pro/Business)
When --template <name> is provided, cook loads a pre-built workflow template instead of auto-detecting:
/rune cook --template product-discovery → Pro: stakeholder interviews → problem framing → competitive → spec → validation
/rune cook --template product-launch → Pro: spec lock → implement → quality gates → staged rollout → announcement
/rune cook --template product-iteration → Pro: metrics review → feedback synthesis → re-prioritize → implement → measure
/rune cook --template data-exploration → Pro: data profiling → hypotheses → statistical testing → visualization → report
/rune cook --template data-pipeline → Pro: schema design → ETL → quality gates → deploy → monitoring
/rune cook --template sales-outreach-campaign → Pro: prospect research → messaging → sequence → A/B test → launch
/rune cook --template sales-deal-review → Pro: account deep-dive → risk assessment → competitive strategy → action plan
/rune cook --template support-incident-response → Pro: triage → diagnose → fix → verify → postmortem → KB update
/rune cook --template support-kb-refresh → Pro: audit → gap analysis → draft → review → publish
Template resolution: Templates are .md files in extensions/pro-*/templates/ or extensions/business-*/templates/. Each template defines: phases, skill connections, mesh signals, and acceptance criteria. The compiler includes templates in pack output during build.
When --template is used:
- Skip Phase 1.5 (auto-detection) — template pre-selects domain and pack
- Skip Phase 1.7 (workflow matching) — template IS the workflow
- Load template phases as the master plan (Phase 2 becomes "review template plan" not "create plan")
- Execute each template phase in order, invoking declared skills
- Emit template's declared signals on completion
Chain selection: If user invokes /rune cook without a chain type, auto-detect from the task description:
- Contains "bug", "fix", "broken", "error" →
bugfix - Contains "refactor", "clean", "restructure" →
refactor - Contains "security", "auth", "vulnerability", "CVE" →
security - Contains "urgent", "hotfix", "production" →
hotfix - Contains "quick", "just", "chỉ cần", "copy", "move", "rename", "bump" →
nano - Contains "graft", "port from", "copy from repo", "clone feature from" → delegate to
rune:graft(not a cook chain — hand off entirely) - Contains
--template→ load template workflow (see above) - Default →
feature
Phase Skip Rules
Not every task needs every phase:
Nano task: DO → VERIFY → DONE (no phases, auto-detected)
Simple bug fix: Phase 1 → 4 → 6 → 7
Small refacto
Read the complete source ↗