Hs:cook

Cook - Smart Feature Implementation

End-to-end implementation with automatic workflow detection.

Principles: YAGNI, KISS, DRY | Token efficiency | Concise reports

Usage

/hs: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

Composable flags (combine with any mode):

• --tdd: Tests-first per phase — write tests for current behavior before refactoring, then verify they still pass after the implementation step

Example:

/hs:cook "Add user authentication to the app" --fast
/hs:cook path/to/plan.md --auto
/hs:cook "Refactor auth middleware" --tdd

State a 3-6 bullet codebase-context summary to the user before asking questions. Skip ONLY when input is a plan.md/phase-*.md path (the plan already encodes scout output).

Shared pattern/rationale: ../_shared/scout-first.md.

Delta: skip this gate ONLY when input is a plan.md/phase-*.md path (the plan already encodes these answers).

Delta: if user invoked --no-test, item 2 (tests pass) is downgraded to a warning — surfaced at finalize ask_user capability, not silently skipped. Items 1, 3, 4, 5 remain enforceable via the mandatory code-reviewer subagent.

Anti-Rationalization

Smart Intent Detection

See references/intent-detection.md for detection logic.

If the task needs a cross-skill workflow sequence decision after intent detection, load references/workflow-routing.md.

Process Flow (Authoritative)

flowchart TD
    A[Intent Detection] --> B{Has plan path?}
    B -->|Yes| F[Load Plan]
    B -->|No| C{Mode?}
    C -->|fast| D[Scout → Plan → Code]
    C -->|interactive/auto| SC[Scout Codebase MANDATORY]
    SC --> SR[Summarize Findings to User]
    SR --> RQ{Exact requirements captured?<br/>output, acceptance, scope, constraints, touchpoints}
    RQ -->|No| SR
    RQ -->|Yes| E[Research → Review → Plan]
    E --> F
    D --> F
    F --> G[Review Gate]
    G -->|approved| H[Implement]
    G -->|rejected| E
    H --> H1{Simplify signal?}
    H1 -->|Yes| H2[Conditional Simplify]
    H1 -->|No| I[Review Gate]
    H2 --> I
    I -->|approved| J{--no-test?}
    J -->|No| K[Test]
    J -->|Yes| L[Finalize]
    K --> L
    L --> M[Report + Journal]

This diagram is the authoritative workflow. Prose sections below provide detail for each node. If prose conflicts with this flow, follow the diagram.

Workflow Overview

[Intent Detection] → [Research?] → [Review] → [Plan] → [Review] → [Implement] → [Conditional Simplify?] → [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 the manage_plan task-management tool (create/update/read/list operations) during the implementation step. Fallback: It is CLI-only — unavailable in the VSCode extension. If it errors, track progress in the plan files directly. Full hydrate/sync-back doctrine: ../_shared/task-hydration.md.

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 (MANDATORY): Spawn code-reviewer subagent using the canonical (a)-(e) delegation prompt and loop logic in ../_shared/review-cycle.md. Pass scout summary + acceptance criteria as context. If reviewer flags side effects → trigger HARD-GATE-NO-SIDE-EFFECTS (ask_user capability with 2-4 options). Then: User approval OR auto-approve (score≥9.5, 0 critical).
• Finalize (MANDATORY - never skip):
  1. Activate the engineer project-management skill skill (MANDATORY) → run full plan sync-back across ALL phase-XX-*.md (not only current phase), update plan.md status/progress, hydrate Claude Tasks, generate progress report
  2. docs-manager subagent → update ./docs if changes warrant
  3. manage_plan capability → mark all Claude Tasks complete after sync-back verification (skip if Task tools unavailable)
  4. Ask user if they want to commit via git-manager subagent
  5. Run /hs:journal to write a concise technical journal entry upon completion

Required Subagents (MANDATORY)

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: delegate_agent capability(subagent_type="[type]", prompt="[task]", description="[brief]")

References

• references/intent-detection.md - Detection rules and routing logic
• references/workflow-routing.md - Cross-skill sequence routing for ambiguous workflows
• references/workflow-steps.md - Detailed step definitions for all modes
• ../_shared/review-cycle.md - Interactive and auto review processes, canonical delegation prompt
• references/subagent-patterns.md - Subagent invocation patterns

Workflow Position

Typically follows: hs:plan (execute a plan), /hs:brainstorm (implement agreed solution) Typically precedes: hs:code-review (review after implementation), hs:test (validate changes) Related: /hs:fix (alternative for bug fixes), hs:plan (create plan before cooking)