architecture-patternslisted

# Architecture Patterns Enforcement Skill Ensures every architecture plan is thorough, actionable, and testable. Used by the planner agent. ## Decision Framework Every architectural decision MUST follow this structure: ### 1. Problem Statement - What problem are we solving? - What are the constraints (performance, compatibility, timeline)? - What does PROJECT.md say about scope? ### 2. Options Analysis - Minimum 2 alternatives considered - Each option has explicit pros and cons - Effort estimate for each (low/medium/high) ### 3. Recommendation - Which option and why - What tradeoffs are we accepting - What risks remain --- ## Plan Structure Requirements Every architecture plan MUST include: ### File-by-File Breakdown ``` ## Files to Create/Modify ### 1. lib/new_module.py (CREATE) - Purpose: [what this file does] - Key classes/functions: [list] - Dependencies: [what it imports] - Tests: tests/unit/test_new_module.py ### 2. lib/existing_module.py (MODIFY) - Changes: [what changes and why] - Lines affected: ~[range] - Risk: [low/medium/high] ``` ### Ordered Steps with Dependencies ``` ## Implementation Order 1. Create lib/new_module.py (no dependencies) 2. Create tests/unit/test_new_module.py (depends on step 1) 3. Modify lib/existing_module.py (depends on step 1) 4. Update integration tests (depends on steps 1-3) ``` Steps MUST be ordered so each step can be tested independently before proceeding. ### Testing Strategy - Unit tests for each new module - Integrati