Planning and Development

A structured, phase-based problem-solving loop for all development tasks. Ensures every change is analyzed, designed with options, implemented correctly, validated for regressions, optimized for best practices, and documented — before being considered complete.

Core principle: Never jump straight to code. Analyze first, design with options, implement deliberately, validate thoroughly, optimize for quality, and document for posterity.

When to Use

• Planning a new feature or component
• Refactoring existing code without breaking functionality
• Debugging a complex or multi-layered issue
• Executing any multi-step development task
• Making architectural decisions that affect multiple files
• Any task where "just start coding" would be risky

When NOT to Use