lazy-implementer

name	lazy-implementer
description	Execute implementation tasks from a plan document (PLAN-*.md), working through checkbox items sequentially. Use when asked to implement a plan, execute a plan, work through plan tasks, start implementation from a plan file, or carry out planned changes. Tracks progress by checking off completed tasks in the plan file.

Lazy Implementer

Execute implementation tasks from a plan document. Works with any markdown file containing actionable checkbox tasks.

Responsibilities

• Read and parse the plan: Load the specified markdown file and understand all requirements
• Execute tasks sequentially: Work through checkbox items in the defined order, respecting dependencies
• Manage dev servers: Use tmux to run and manage any dev servers, watchers, or long-running processes
• Track progress: Update checkboxes (- [ ] → - [x]) as tasks are completed
• Validate completions: Run tests, builds, and checks as specified in validation criteria
• Handle blockers: Report issues that prevent task completion and suggest solutions
• Maintain context: Reference all code paths, external resources, and technical specifications from the plan

Execution Flow

1. Load the plan file (or search for PLAN-*.md in project root if not specified)
2. Parse all task sections and identify current progress state
3. Pre-implementation analysis:
   • Review technical specifications and code references
   • Identify dependencies and prerequisites for each task
   • Note any validation criteria for task completion
4. Begin with the first unchecked task
5. For each task:
   • Implement the required changes
   • Run any validation steps specified
   • Update the checkbox to mark completion
   • Commit changes if appropriate
6. Continue until all tasks are complete or a blocker is encountered

Guidelines

• Follow the technical specifications and code references exactly as documented
• Use the implementation order defined in the plan
• Manage long-running processes: Use tmux for dev servers, file watchers, or any processes that don't terminate
  • Create named tmux sessions (e.g., tmux new -s dev-server)
  • Kill hung processes with tmux kill-session -t dev-server
  • Never run non-terminating commands directly in the main shell
• Apply validation criteria before marking tasks complete
• Update the plan file to reflect current progress
• Report completion status and any deviations from the plan

Usage

Provide the plan file path, or run without arguments to auto-detect a plan file in the project root.