My workflow is pretty simple:
I have a Macro Group named "[Test]". Starting the name with a bracket [
sorts the group near the top.
- Most new macros start in the "[Test]" Group, and I also add a pseudo tag of "@TEST" at the end of the Macro name (this allows me to quickly identify it as a test macro, and also to quickly search for all test macros).
- Initially I do NOT assign any triggers. Instead I make use of @DanThomas' very cool macro that uses F1 to trigger whatever macro is the current macro in the KM editor. See MACRO: Run Current Macro.
- After initial testing is complete, I move the macro (drag/drop) to the appropriate Macro Group, and do some final testing with the Group and actual trigger.
- When everything seems to work OK, I remove the "@TEST" tag.
BTW, I also have lots of Groups, and find drag/drop to move macros to work very fast. I really don't think triggering another macro to move it, and doing all of the manual keyboard stuff to find and select the target group would be faster. In fact, I think it would be slower. But that's just me.