python-plan-optimization

Analyze Python code blocks in Markdown planning documents for design debt.

9|2|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/it-bens/claude-code-plugins --skill python-plan-optimization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python-plan-optimization
Source: https://github.com/it-bens/claude-code-plugins/tree/main/plugins/python-plan-optimizer/skills/python-plan-optimization
Command: npx skills add https://github.com/it-bens/claude-code-plugins --skill python-plan-optimization

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill performs a non-destructive 6-phase analysis of Python code described in planning Markdown documents. It identifies design-principle violations, code smells, and opportunities for modern Python improvements, while respecting the document's stated architecture and toolchain.

Core Features & Use Cases

  • Read-only analysis: Scans code blocks and documents without modifying source.
  • Principle & smell detection: Flags SOLID, DRY, KISS, YAGNI violations and common code smells.
  • Modernization suggestions: Recommends type hints, dataclasses, and modern Python idioms aligned with project type.
  • Context-aware considerations: Preserves explicit architectural decisions and tooling choices.
  • Deliverable: A structured analysis report with actionable recommendations per document.

Quick Start

Activate the skill on your planning Markdown documents containing Python code blocks. The skill will generate a read-only analysis report and will not modify any source files.

Frequently Asked Questions about python-plan-optimization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect code smells and design issues in Python planning documents?

This skill analyzes Python code blocks embedded in Markdown planning files to identify design-principle violations, code smells, and modernization opportunities. It performs a read-only 6-phase analysis that flags SOLID, DRY, KISS, and YAGNI violations without modifying source files, delivering actionable recommendations per document.

Can I analyze design debt in my Python project without modifying code?

Yes. This skill scans planning Markdown documents containing Python code blocks and produces a non-destructive analysis report. It respects your stated architecture and tooling choices, providing recommendations for design improvements while keeping all source files untouched.

What Python modernization issues does this analysis cover?

The skill identifies opportunities for type hints, dataclasses, and modern Python idioms aligned with your project type—POC, MVP, Private, Enterprise, or Open Source. It also detects common code smells and design-principle violations specific to your project's context and constraints.

How does this skill handle different project stages and constraints?

The analysis applies project-type thresholds (POC through Open Source) and respects explicit architectural decisions documented in your planning files. Recommendations are calibrated to your project's maturity level and toolchain, not imposed uniformly across all contexts.

What input format do I need for this analysis?

Provide planning Markdown documents with embedded Python code blocks. The skill reads these files to detect design opportunities and generate per-document analyses with a summary report. No additional setup or source code files are required.

When should I use design analysis versus direct code refactoring?

Use this skill during planning phases to surface design-debt opportunities before implementation, or to validate architectural decisions in existing documentation. It's a read-only analysis tool best suited for identifying patterns and gathering data to inform future refactoring decisions.