{ "_template_description": "Template for fix planning output. Planning agent reads this template and generates actual fix-plan.json", "_usage": "Planning agent should follow this structure when analyzing findings and creating fix plan", "plan_id": "", "created_at": "", "total_findings": "", "execution_strategy": { "approach": "", "parallel_limit": "", "total_stages": "", "rationale": "" }, "groups": [ { "group_id": "", "group_name": "", "findings": [""], "fix_strategy": { "approach": "", "rationale": "", "complexity": "", "estimated_duration_minutes": "", "test_pattern": "", "rollback_plan": "" }, "risk_assessment": { "level": "", "concerns": [""], "mitigation": "" } } ], "timeline": [ { "stage": "", "groups": [""], "execution_mode": "", "depends_on": [""], "rationale": "" } ], "_instructions": { "grouping_principles": [ "Group findings in the same file with same dimension", "Group findings with similar root causes (high semantic similarity)", "Consider file dependencies and execution order", "Balance group sizes for efficient parallel execution" ], "execution_strategy_guidelines": [ "Use parallel for independent groups in different files", "Use serial for dependent changes (e.g., shared utilities)", "Limit parallelism to 3 concurrent agents to avoid resource contention", "High-risk groups should be isolated for careful monitoring" ], "test_strategy_guidelines": [ "Identify test files related to changed code", "Use specific patterns for faster test execution", "Ensure test coverage captures all fix impacts", "Define clear pass criteria (usually 100% pass rate)" ], "risk_assessment_guidelines": [ "Low: Simple fixes with comprehensive test coverage", "Medium: Moderate changes affecting multiple components", "High: Core logic changes or security-critical fixes", "Critical: Database schema changes or breaking API changes" ] } }