claudetools/.claude/commands/feature-request.md

GuruRMM Feature Request -> RMM Thoughts

When Howard (or Mike) submits a GuruRMM feature request, capture it as a raw entry in the RMM Thoughts backlog — do NOT jump straight to a full spec or the roadmap. Those are downstream, decision-gated stages.

Pipeline (see .claude/memory/feedback_rmm_thoughts_backlog.md): THOUGHT (this command, Status: Raw) -> DISCUSS -> SPEC (/shape-spec -> specs/<slug>/) -> ROADMAP (docs/FEATURE_ROADMAP.md) -> BUILD.

Backlog doc: projects/msp-tools/guru-rmm/docs/RMM_THOUGHTS.md.

---

Phase 1 — Light triage (Ollama, optional)

Read .claude/identity.json for the user (Howard/Mike) and the Ollama endpoint (.ollama.endpoint). Call Ollama qwen3.6:latest (strict JSON) for a LIGHT triage — NOT deep research, NOT a spec:

You are triaging a GuruRMM feature request into a backlog. Request: $ARGUMENTS
Respond JSON only:
{"title": "short kebab-or-title-case name", "summary": "1-2 sentence plain-English summary",
 "section_guess": "Core Agent | Server/API | Dashboard & UI | Platform | Integrations | Security | Alerting | Other",
 "priority_guess": "P1|P2|P3"}

If Ollama is unreachable, do this triage yourself. Do NOT search the codebase or write a spec at this stage.

---

Phase 2 — Append to RMM Thoughts

Append a new entry to the bottom of projects/msp-tools/guru-rmm/docs/RMM_THOUGHTS.md:

## <Title>
- Added: <Howard|Mike>, <YYYY-MM-DD> | Status: Raw | section guess: <section> | priority guess: <P?>

<the request, in the submitter's words> <one-line triage summary if it adds clarity>

Keep it short — it is a RAW thought, not a spec. Do not embellish or design it.

---

Phase 3 — Notify + track

• Coord todo (so it is visible fleet-wide), via coord skill: todo add "RMM THOUGHT (Raw): <title> — <summary>. See docs/RMM_THOUGHTS.md." --project gururmm --auto --source "feature-request by <who> <date>"
• If Howard submitted it, send a coord message so Mike sees it: msg send ALL "RMM Thought added: <title>" "<who> added a GuruRMM thought (Status: Raw) to docs/RMM_THOUGHTS.md: <summary>. Ready to discuss when you are — not spec'd or roadmapped yet."

---

Phase 4 — Commit (docs-only, gururmm repo)

cd projects/msp-tools/guru-rmm
git checkout -b docs/rmm-thought-<slug>
git add docs/RMM_THOUGHTS.md
git commit -m "docs(rmm-thoughts): add thought - <title> (requested by <who>)"   # + Co-Authored-By trailer
git fetch origin && git rebase origin/main
git push origin docs/rmm-thought-<slug>:main
git checkout main && git merge --ff-only origin/main && git branch -d docs/rmm-thought-<slug>

Do NOT touch the parent repo submodule pointer.

---

Phase 5 — Respond

Tell the user the request was added to RMM Thoughts at Status: Raw — summarize it, and say it will be discussed before any spec or roadmap entry. Do NOT claim a spec was created or that it is on the roadmap.

[OK] Added to RMM Thoughts (Status: Raw)

<Title>  (section guess: <section> | priority guess: <P?>)
<summary>

Next: we discuss it -> /shape-spec if approved -> roadmap -> build.
Tracked: coord todo <id>.<if Howard: coord message sent to Mike.>

---

Notes

• This command does NOT auto-create a SPEC-XXX doc or a roadmap entry anymore. The old behaviour (full Ollama spec generation + roadmap edit on every request) jumped past the discuss stage; spec work now happens via /shape-spec once a thought is approved.
• To advance a thought later: discuss it (-> Status: Discussed), /shape-spec it (-> Spec'd, specs/<slug>/), then add it to FEATURE_ROADMAP.md (-> Roadmapped).
• Ollama unreachable: do the triage yourself, no degradation. Coord API down: warn and continue (the doc commit is the durable record).