---

name: line-cook description: AI-supervised development workflow. Use when running prep, cook, serve, tidy, or work commands, managing beads issues during sessions, or following prep→cook→serve→tidy cycle. Covers workflow orchestration, guardrails, and session management.

Line Cook

Structured AI workflow execution for disciplined development.

When to Use

• Starting a work session with "work" or "/work"
• Running individual workflow steps: "mise", "prep", "cook", "serve", "tidy", "plate"
• Managing beads issues during execution
• Understanding workflow guardrails

Quick Reference

Core Workflow

Quick cycle (most common):

Copyprep → cook → serve → tidy

Full service (feature delivery):

Copymise → prep → cook → serve → tidy → plate

Step-by-Step

1. Mise: Plan work breakdown (interactive)
2. Prep: Sync state, identify available work
3. Cook: Claim task, execute with guardrails, verify completion
4. Serve: AI reviews changes
5. Tidy: File discovered issues, commit, push
6. Plate: Validate feature completion (when applicable)

Guardrails

Line Cook enforces these disciplines:

• Sync before work - Always start with current state
• One task at a time - Focus prevents scope creep
• Verify before done - Tests pass, code compiles
• File, don't block - Discovered issues become new beads
• Push before stop - Work isn't done until it's pushed

TDD Cycle with Quality Gates

Cook phase follows Red-Green-Refactor with automatic quality checks:

RED: Write failing test

• Write test for the feature
• Verify test fails
• Taster agent reviews test quality
• Address critical issues before proceeding

GREEN: Implement minimal code

• Write simplest code to make test pass
• Verify tests pass
• No refactoring yet

REFACTOR: Clean up code

• Improve structure while tests pass
• Ensure tests still pass after refactoring

Quality Gates (must pass before completion):

• Tests pass (project-specific test command)
• Code builds (project-specific build command)
• Test quality approved by taster agent
• Code quality approved by sous-chef agent (serve phase)

Beads Integration

Line Cook uses beads for task management:

Copybd ready                              # Find unblocked tasks
bd update <id> --status in_progress   # Claim task
bd show <id>                          # Get task context
bd close <id>                         # Complete task
bd sync                               # Sync with git

Parking Lot Pattern

Tasks under "Retrospective" or "Backlog" epics are excluded from auto-selection. Explicit selection still works:

Copybd update <parked-task-id> --status in_progress

Error Handling

If a step fails:

• Prep fails: Fix sync issues, retry
• Cook fails: Continue to tidy to save progress
• Serve fails: Review skipped, continue to tidy
• Tidy fails: Create bead for follow-up
• Plate fails: Note incomplete, create follow-up bead

Reference

For full documentation, see:

• README.md in project root - Philosophy and installation
• steering/*.md files - Workflow instructions