plans▌

Execute a written implementation plan with critical review and task checkpoints. \n \n Requires loading and critically reviewing the plan before execution; raises concerns with the human partner if issues are identified \n Executes tasks sequentially, marking progress and running verifications as specified in the plan \n Stops immediately on blockers (missing dependencies, test failures, unclear instructions) rather than guessing; asks for clarification \n Integrates with git-worktrees for isola

Load plan, review critically, execute tasks in batches, report for review between batches.

Comprehensive implementation plans for multi-step tasks, breaking down specs into bite-sized, testable steps. \n \n Decomposes requirements into focused tasks (2–5 minutes each) following TDD: write failing test, verify failure, implement, verify pass, commit \n Maps file structure upfront with clear boundaries and responsibilities, ensuring each file has one purpose and files that change together stay together \n Includes exact file paths, complete code samples, and specific commands with expec

symfony:writing-plans

symfony:executing-plans

Treatment plan writing is the systematic documentation of clinical care strategies designed to address patient health conditions through evidence-based interventions, measurable goals, and structured follow-up. This skill provides comprehensive LaTeX templates and validation tools for creating concise, focused treatment plans (3-4 pages standard) across all medical specialties with full regulatory compliance.

Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.

Structured plan execution with batch processing and architect review checkpoints. \n \n Loads and critically reviews implementation plans before execution, raising concerns with human partners upfront rather than proceeding blindly \n Executes tasks in batches (default: first 3 tasks) with verification steps and completion marking between each batch \n Reports results and verification output after each batch, pausing for feedback before continuing to the next batch \n Stops immediately on blocke

Detailed implementation planning for multi-step engineering tasks with bite-sized, test-driven steps. \n \n Generates comprehensive plans assuming zero codebase context, breaking work into 2–5 minute tasks following TDD principles (failing test, minimal implementation, passing test, commit) \n Produces structured markdown documents with exact file paths, complete code snippets, and specific shell commands with expected outputs \n Designed for handoff to either subagent-driven execution (fresh ag