azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sync: auto-sync from GURU-5070 at 2026-06-08 06:50:14

Browse Source 
Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-08 06:50:14
This commit is contained in:
Mike Swanson
2026-06-08 06:50:18 -07:00
parent 14362628a2
commit 41450301dc
4 changed files with 188 additions and 428 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.claude/memory/MEMORY.md
View File

@@ -111,3 +111,4 @@
- [ScreenConnect RESTful API auth](reference_screenconnect_api.md) — CTRLAuthHeader = raw api_secret (no Basic/b64) + Origin header; only method is GetSessionsByName; matches blank-for-agents Name field so it cannot enumerate full inventory.
- [No manufactured guardrails on our products](feedback_no_manufactured_guardrails.md) — At Mikes request on GuruRMM/GuruConnect/ClaudeTools, just execute; stop only for genuinely irreversible/destructive ops (with a heads-up). Read the actual code/state before claiming something is disallowed or a security hole.
- [Stream-of-thought design convos](feedback_stream_of_thought_design.md) — Mike brainstorms features free-form, adding requirements iteratively; Claude validates/sharpens as a design partner but does NOT build until an explicit go, then captures parked threads durably (PARKED_*.md + todos) for a later /shape-spec.
- [RMM Thoughts backlog](feedback_rmm_thoughts_backlog.md) — GuruRMM ideas from Mike & Howard go in projects/msp-tools/guru-rmm/docs/RMM_THOUGHTS.md (Status: Raw); pipeline thought -> discuss -> spec (/shape-spec) -> roadmap. Don't build until an explicit go.

26
.claude/memory/feedback_rmm_thoughts_backlog.md Normal file
View File

@@ -0,0 +1,26 @@
---
name: feedback-rmm-thoughts-backlog
description: GuruRMM ideas go into the "RMM Thoughts" backlog (docs/RMM_THOUGHTS.md); pipeline thought -> discuss -> spec -> roadmap; both Mike and Howard contribute.
metadata:
type: feedback
---
When Mike or Howard raises a GuruRMM idea — or says "rmm thought: <x>", "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]].