claudetools/.claude/memory/feedback_rmm_dev_is_mike.md at a8ee927db0ca8b2285ea6b8b0f52750087f18cfb

Files

Mike Swanson ac47f51a2b sync: auto-sync from GURU-5070 at 2026-05-26 19:32:05

Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-05-26 19:32:05

2026-05-26 19:32:09 -07:00

1.5 KiB

Raw Blame History

name, description, type

name	description	type
GuruRMM development is Mike's, not Howard's	GuruRMM code/bugs/dev are Mike's domain — never route RMM dev or bug coord notes to Howard. Howard only SUBMITS RMM feature requests; GuruScan is Howard's project, not RMM	feedback

GuruRMM development — code, bugs, the roadmap, architecture — is Mike's domain. Do NOT route RMM dev/bug coord messages to Howard. Howard does zero RMM coding.

Why: Mike, 2026-05-26. I escalated a stale GuruRMM roadmap bug (BUG-001) to Howard via a coord note; Mike corrected me — "Howard hasn't done ANY code work on RMM." Verified: users.json machine lists don't overlap (mike: GURU-5070/Mikes-MacBook-Air/GURU-BEAST-ROG/GURU-KALI; howard: ACG-TECH03L/Howard-Home), and the GuruRMM repo has 368 commits by Mike and 0 by Howard. The /feature-request skill encodes the real model: Howard submits RMM feature requests → Mike does the dev. I had inverted it.

How to apply:

RMM bug/dev/roadmap item → it's Mike's. Since Mike is usually the user, just surface it to him directly; don't send a coord note to anyone (a note to yourself is pointless, and Howard isn't the owner).
GuruScan (projects/msp-tools/guru-scan/) IS Howard's project — coord notes about GuruScan correctly go to Howard. Don't conflate GuruScan with GuruRMM just because the names rhyme or GuruScan may integrate with RMM.
Before sending any coord note to a teammate, check whose domain the work actually sits in. See user_howard.

1.5 KiB Raw Blame History

1.5 KiB

Raw Blame History