1.4 KiB
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| feedback-rmm-thoughts-backlog | GuruRMM ideas go into the "RMM Thoughts" backlog (docs/RMM_THOUGHTS.md); pipeline thought -> discuss -> spec -> roadmap; both Mike and Howard contribute. |
|
When Mike or Howard raises a GuruRMM idea — or says "rmm thought: ", "add to rmm
thoughts", or "park this (as an rmm thought)" — append it to
projects/msp-tools/guru-rmm/docs/RMM_THOUGHTS.md with who/when and Status: Raw.
Do NOT start building; ideas advance only by an explicit decision through the pipeline:
Raw -> Discussed -> Spec'd (/shape-spec -> specs/<slug>/) -> Roadmapped
(docs/FEATURE_ROADMAP.md) -> Done.
Howard's /feature-request items should land here too. As a thought advances, update
its Status line and link the spec folder / roadmap entry.
Why: Mike wants ONE shared backlog to collect RMM ideas from both techs, then chat them through, turn them into specs, and add them to the roadmap — rather than ideas getting lost in chat or scattered across todos.
How to apply: the doc is the canonical home (commit changes to the gururmm repo).
Pair a new thought with a coord todo tagged "PARKED (design)" / project gururmm for
fleet visibility, like the existing ones. Established 2026-06-08 (renamed from the
PARKED_alert-lifecycle... notes). Related: feedback-stream-of-thought-design.