pragmatic-guardlisted

# Pragmatic Guard Mode Enables and configures the Pragmatic Guard Mode to actively challenge over-engineering. ## Process ### 1. Check Current Configuration - Read `.architecture/config.yml` to check current settings - If config.yml doesn't exist, offer to create it from `.architecture/templates/config.yml` - Check if `pragmatic_mode.enabled` is true - Note the intensity level (strict/balanced/lenient) - Review exemption categories and triggers ### 2. Enable Pragmatic Mode (if requested) If user wants to enable: - If config.yml doesn't exist: ```bash cp .architecture/templates/config.yml .architecture/config.yml ``` - Set `pragmatic_mode.enabled: true` - Confirm intensity level with user or use default (balanced) - Create `.architecture/deferrals.md` from template if it doesn't exist: ```bash cp .architecture/templates/deferrals.md .architecture/deferrals.md ``` - Inform user about mode activation and current settings ### 3. Configure Intensity Level Ask user which intensity they prefer if not specified: **Strict Mode**: - Challenges aggressively, requires strong justification for any complexity - Questions every "should" and "could" - Pushes for absolute minimal implementation - Best for: New projects, MVPs, startups with limited resources **Balanced Mode** (RECOMMENDED): - Challenges thoughtfully, accepts justified complexity - Seeks middle ground between simplicity and best practices - Questions "should" but accepts reasonable "must" - Best for: Most pro