Have been fiddling with ICM, Hermes, GSD, BMAD, taskMaster etc. They all sound perfect and logical on their own but feel "out of control" somehow so put it inside of ICM. I tried to make sense of them all and cook up an ICM here: .icm/ ├── CLAUDE.md # Upgrade safety gates, rollback hooks, and CLI routines ├── .icm.env # NEW: Central environment vars feeding variables to scripts │ ├── 00-gsd-wave-governor/ # CONTEXT & SPREAD CONTROL │ ├── contract.md # Rules: Blast-radius mitigation, branch naming, strict file locks │ └── active_wave.md # Tracks the current migration delta and target files │ ├── 01-discovery-and-party/ # LEGACY ANALYSES & DEBATE │ ├── contract.md # Rules: Analysis must document side-effects before code editing │ ├── codebase_discovery.md # Static analysis logs, dependency graphs, and tech debt maps │ ├── 00-party-room/ # BMAD Party Mode: "Refactor vs. Wrap" architectural battles │ │ ├── system_prompt.md # Personas (Winston/Arch, John/PM, Safety-QA Specialist) │ │ └── migration_consensus.md # Binding agreement on the upgrade strategy & fallback path │ └── 01-feedback-loops/ # Regression and breaking change post-mortems │ ├── 02-taskmaster-decomp/ # MIGRATION STEP DECOMPOSITION │ └── todo/ # Micro-tasks focused on localized refactoring steps │ └── 03-bmad-assembly-line/ # IMPLEMENTATION & REGRESSION TESTING │ ├── 01-architect-spec/ # BMAD Role: Designing code deltas & backward compatibility │ ├── 02-dev-workspace/ # BMAD Role: Executing precise, isolated modifications │ └── 03-qa-sandbox/ # BMAD Role: Core regression suite, smoke tests, validation