python-plan-optimizer

Analyzes Python code examples in planning documents (PLAN.md, design.md, architecture.md). Use when requests involve optimizing, reviewing, or analyzing Python code quality in planning documents. Supports single files, directories, and file lists. Applies project-type-aware thresholds (POC, MVP, Private, Enterprise, Open Source). <example> Context: User wants code review for a planning document user: "Review the Python code in my PLAN.md" assistant: "I'll use the python-plan-optimizer agent to analyze the code and identify improvement opportunities." <commentary>Single file triggers read-only analysis.</commentary> </example> <example> Context: User wants to check design principles user: "Check if the code in design.md follows SOLID principles" assistant: "I'll use the python-plan-optimizer agent to analyze the code against SOLID principles." <commentary>Principle check triggers analysis with recommendations.</commentary> </example> <example> Context: User wants code smell detection user: "Are there any code smells in my architecture doc?" assistant: "I'll use the python-plan-optimizer agent to detect code smells and suggest improvements." <commentary>Code smell detection triggers read-only review.</commentary> </example> <example> Context: User wants to understand modernization opportunities user: "What Python improvements could be made in my design doc?" assistant: "I'll use the python-plan-optimizer agent to identify modernization opportunities." <commentary>Improvement inquiry triggers analysis with suggestions.</commentary> </example> <example> Context: User wants to analyze all planning docs in a directory user: "Analyze all the Python code in my ./plan/ directory" assistant: "I'll use the python-plan-optimizer agent to analyze all markdown files in the directory." <commentary>Directory triggers file discovery and analysis of all Python-containing docs.</commentary> </example> <example> Context: User wants to analyze multiple specific files user: "Review PLAN.md, design.md, and architecture.md" assistant: "I'll use the python-plan-optimizer agent to analyze all three documents." <commentary>Multiple files are analyzed and results aggregated.</commentary> </example> <example> Context: User wants to optimize Python code in planning documents user: "Optimize the Python code in my plan directory" assistant: "I'll use the python-plan-optimizer agent to analyze and suggest optimizations." <commentary>Optimize triggers read-only analysis with improvement suggestions.</commentary> </example> <example> Context: User specifies project type explicitly user: "Analyze my enterprise project's PLAN.md" assistant: "I'll use the python-plan-optimizer agent with enterprise-level analysis (all issues, verification required)." <commentary>Project type in prompt skips type determination question.</commentary> </example> <example> Context: User wants POC-level analysis user: "Quick review of this POC code in design.md" assistant: "I'll use the python-plan-optimizer agent with POC-level analysis (critical issues only)." <commentary>POC triggers minimal analysis - only critical blockers.</commentary> </example> Read-only analysis - does NOT modify any files.

Determines project type from context to configure analysis thresholds. Checks prompt, scans documents, or asks user if type cannot be inferred. Outputs project_type for use by python-plan-optimization skill.

6-phase read-only analysis workflow for Python code in markdown documents. Detects design principle violations, code smells, and suggests modern Python improvements. Applies project-type-aware thresholds (POC, MVP, Private, Enterprise, Open Source). Processes one or more documents, generating per-document analysis with summary.