By smileynet
Orchestrate structured dev workflows for Claude Code: plan epics/features/tasks from brainstorms into YAML breakdowns and beads, execute prioritized tasks with code/test reviews and guardrails, commit via git with triage, validate completions, and generate docs/ADRs/CHANGELOGs.
Audit codebase architecture, code smells, and quality metrics
Explore problem space before planning (divergent thinking)
Validate completed epic and create acceptance documentation
Select and execute a task with completion guardrails
Record, list, or supersede architecture decisions (ADRs)
Reviews epic-level E2E and smoke test coverage - validates user journeys and cross-feature integration before epic completion
Automated issue triage agent triggered by GitHub Actions. Analyzes new issues, searches the codebase for context, classifies type, applies labels, and responds with structured analysis. Not invoked directly — runs via the issue-agent workflow.
Reviews feature acceptance and BDD test quality - verifies acceptance criteria coverage and Given-When-Then structure
Simplify and refine recently modified code for clarity, consistency, and maintainability. Use this agent after sous-chef review to polish code and apply auto-fixable findings. This is an action agent that edits code. Examples: <example> Context: Sous-chef review returned APPROVED with auto-fixable findings. assistant: "Now let me polish the code and apply the auto-fixable review findings." <Task tool call to launch polisher agent with list of modified files and auto-fixable findings> </example> <example> Context: Sous-chef review returned APPROVED with no auto-fixable findings. assistant: "Let me polish these changes for clarity before tidy." <Task tool call to launch polisher agent> </example>
Use this agent when a logical chunk of code has been written or modified and needs review before proceeding. This includes after implementing a feature, fixing a bug, refactoring code, or completing any task that involves code changes. The agent should be called proactively after significant code changes to catch issues early. Examples: <example> Context: User asked to implement a new feature and the code has been written. user: "Add a function to validate email addresses" assistant: "Here is the email validation function I've implemented:" <function implementation completed> assistant: "Now let me use the sous-chef agent to review this code for correctness, security, and style before we proceed." <Task tool call to launch sous-chef agent> </example> <example> Context: User asked to fix a bug and the fix has been applied. user: "Fix the null pointer exception in the user service" assistant: "I've identified and fixed the null pointer exception by adding proper null checks:" <bug fix completed> assistant: "Let me have the sous-chef agent review this fix to ensure it's complete and doesn't introduce new issues." <Task tool call to launch sous-chef agent> </example> <example> Context: User completed a refactoring task. user: "Refactor the authentication module to use the new token service" assistant: "I've refactored the authentication module. Here are the changes:" <refactoring completed> assistant: "Before we consider this complete, I'll use the sous-chef agent to review the refactored code for any issues." <Task tool call to launch sous-chef agent> </example>
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
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.
Mise Cycle Run Cycle
┌──────────────────┐ ┌──────────────────┐
│ │ │ │
│ /brainstorm │ │ /prep ◄────┐ │
│ ↓ │ │ ↓ │ │
│ /sample │ │ /cook │ │
│ ↓ │ │ ↓ │ │
│ /scope │ │ /serve │ │
│ ↓ │ │ ↓ │ │
│ /finalize ─────┼─────► │ /tidy ─────┘ │
│ │ │ next task │
└──────────────────┘ └──────────────────┘
Brainstorm → Sample → Scope → Finalize. Turn unstructured ideas into well-scoped, dependency-ordered tasks with test specs.
Prep → Cook → Serve → Tidy. Execute one task at a time with TDD, AI peer review, and automatic commit/push.
Repeat Run Cycles hands-free until no ready tasks remain. Same quality gates, no supervision needed. Supports Claude Code and Kiro via --cli kiro.
/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:initto verify your setup, then see the Getting Started walkthrough.
Use Line Cook when:
Skip it when:
Beads provides git-native issue tracking with memory between sessions.
brew install beads
See beads repo for npm/go options.
Claude Code:
/plugin marketplace add smileynet/line-cook
/plugin install line@line-cook
OpenCode:
git clone https://github.com/smileynet/line-cook.git ~/line-cook
cd ~/line-cook/plugins/opencode && ./install.sh
Kiro:
git clone https://github.com/smileynet/line-cook.git ~/line-cook
python3 ~/line-cook/plugins/kiro/install.py
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.
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 toolkit
MIT
npx claudepluginhub smileynet/line-cook --plugin lineCode quality spice for Line Cook — decision frameworks, antipattern detection, refactoring patterns, tradeoff analysis, YAGNI guidance, dead code pruning, and plan auditing
Real-world concepts from programming, education, and design — packaged as AI commands
Game design spice for Line Cook — MLP scoping, core loop frameworks, economy design, difficulty curves, content planning, mechanics palette, playtesting, scenario walkthroughs, anti-patterns, architecture auditing, with interactive commands, code review agent, and implementation guidance
Persistent file-based planning for AI coding agents. Crash-proof markdown plans (task_plan.md, findings.md, progress.md) that survive context loss and /clear, with an opt-in completion gate and multi-agent shared state. Manus-style. Works with Claude Code, Codex CLI, Cursor, Kiro, OpenCode and 60+ agents via the SKILL.md standard. Includes Arabic, German, Spanish, and Chinese (Simplified and Traditional).
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Comprehensive C4 architecture documentation workflow with bottom-up code analysis, component synthesis, container mapping, and context diagram generation
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
Superpowers Plus core skills library for Claude Code: planning, execution routing, TDD, debugging, and collaboration workflows