Line Cook
Think big, execute small.
Use the Mise Cycle to brainstorm freely — explore possibilities, ask hard questions, and plan ambitious work in a single creative session. Then hand off to the Run Cycle, where strong guardrails keep execution disciplined: small context windows prevent scope creep, and acceptance criteria at every level (task, feature, epic) ensure quality gates are met before work ships.
The result: you stay in deep work while AI handles structured execution with built-in checkpoints.
The Two Cycles
Mise Cycle Run Cycle
┌──────────────────┐ ┌──────────────────┐
│ │ │ │
│ /brainstorm │ │ /prep ◄────┐ │
│ ↓ │ │ ↓ │ │
│ /sample │ │ /cook │ │
│ ↓ │ │ ↓ │ │
│ /scope │ │ /serve │ │
│ ↓ │ │ ↓ │ │
│ /finalize ─────┼─────► │ /tidy ─────┘ │
│ │ │ next task │
└──────────────────┘ └──────────────────┘Mise: Ideas → Tasks
Brainstorm → Sample → Scope → Finalize. Turn unstructured ideas into well-scoped, dependency-ordered tasks with test specs.
Run: Tasks → Shipped Code
Prep → Cook → Serve → Tidy. Execute one task at a time with TDD, AI peer review, and automatic commit/push.
Loop: Autonomous Execution (Advanced)
Repeat Run Cycles hands-free until no ready tasks remain. Same quality gates, no supervision needed. Supports Claude Code and Kiro via --cli kiro.
Quick Start
/line:init # Verify your setup
bd init # Initialize beads in your project
/line:mise # Plan your work (brainstorm → sample → scope → finalize)
# Clear context
/line:run # Execute (prep → cook → serve → tidy)> New here? Run /line:init to verify your setup, then see the Getting Started walkthrough.
When to Use / Skip
Use Line Cook when:
- Work spans multiple sessions
- Tasks have dependencies
- You want automated code review
- You're building trust in AI workflows
Skip it when:
- Quick one-off fixes
- Exploratory coding or prototyping
- Active pair programming
- Setup takes longer than the work
Installation
1. Install beads
Beads provides git-native issue tracking with memory between sessions.
brew install beads> See beads repo for npm/go options.
2. Install Line Cook
Claude Code:
/plugin marketplace add smileynet/line-cook
/plugin install line@line-cookOpenCode:
git clone https://github.com/smileynet/line-cook.git ~/line-cook
cd ~/line-cook/plugins/opencode && ./install.shKiro:
git clone https://github.com/smileynet/line-cook.git ~/line-cook
python3 ~/line-cook/plugins/kiro/install.pyLearn More
- Getting Started — Walkthrough from install to first shipped task
- Command Reference — All commands and options
- AGENTS.md — Technical reference for contributors
FAQ
What if all my tasks are blocked? Run /line:plan-audit to check your dependency graph. Common causes: circular dependencies, a blocker that was never created, or a task that's done but wasn't closed (bd close <id>).
> More questions answered in the full FAQ.
Spice Rack
Domain-specific addons that enhance planning. Spices load automatically during /mise when relevant project context is detected.
| Spice | What it adds | |-------|-------------| | game-spice | Interactive game design workflow — brainstorm, simulate, and build-plan commands plus 14 knowledge skills covering MLP scoping, core loops, economy design, mechanics palette, playtesting, and architecture review | | code-spice | Code quality foundations — readability, naming, refactoring, error handling, antipatterns, tradeoff analysis, testing guidance, and an automated code-quality critic for /line:serve |
game-spice is for game projects (design sessions, balance checks, walkthroughs). code-spice is for any software project (code quality, review prep, smell detection). Both can be installed together.
/plugin install game@line-cook # game design workflow
/plugin install code@line-cook # code quality toolkitLicense
MIT
