Hello, I'm James St-Pierre

$ ./problem-solver.sh --show-methodology

PROBLEM SOLVING FRAMEWORK
A systematic approach to technical challenges

1. UNDERSTAND
   First, deeply analyze before jumping to solutions
   └─ Identify the core issue behind apparent symptoms
   └─ Define clear success criteria with measurable outcomes
   └─ Research related patterns from previous experience
   └─ Consult with stakeholders to align expectations

2. EXPLORE
   Consider multiple approaches before committing
   └─ Brainstorm various solutions without judgment
   └─ Evaluate tradeoffs (speed vs maintainability)
   └─ Consider edge cases and potential limitations
   └─ Prototype minimal implementations when needed

3. PLAN
   Create a clear roadmap before implementation
   └─ Break down into smaller, manageable tasks
   └─ Identify potential roadblocks and dependencies
   └─ Set clear milestones and checkpoints
   └─ Allocate time realistically, including buffer

4. IMPLEMENT
   Build with quality and testing in mind
   └─ Follow best practices and coding standards
   └─ Write tests first when possible (TDD approach)
   └─ Make regular commits with clear messages
   └─ Prioritize maintainability over cleverness

5. REFINE
   Continuously improve through feedback
   └─ Review code and refactor for clarity
   └─ Optimize performance for critical paths
   └─ Document thoroughly for future developers
   └─ Gather user feedback and iterate accordingly
```


$ ./problem-solver.sh --apply "Building scalable architecture"
Applying methodology to problem...
✓ Solution generated: Elegant, maintainable, and scalable architecture