sync: auto-sync from GURU-5070 at 2026-06-02 20:40:54
Author: Mike Swanson Machine: GURU-5070 Timestamp: 2026-06-02 20:40:54
This commit is contained in:
19
.grok/skills/feature-request/SKILL.md
Normal file
19
.grok/skills/feature-request/SKILL.md
Normal file
@@ -0,0 +1,19 @@
|
||||
---
|
||||
name: feature-request
|
||||
description: >
|
||||
GuruRMM Feature Request — Comprehensive Analysis & Specification. Use when Howard (or a teammate) submits a GuruRMM feature request. Classifies it and messages Mike. Triggers on "feature request", "/feature-request", or specific RMM roadmap items.
|
||||
---
|
||||
|
||||
# /feature-request — GuruRMM Feature Request Analysis
|
||||
|
||||
This is the command for structured feature request handling in the GuruRMM project.
|
||||
|
||||
**See source:** `.claude/commands/feature-request.md` for the full workflow (classification, shape-spec generation, coord messaging to the right person, links to docs/roadmap).
|
||||
|
||||
For Grok:
|
||||
- Read the command doc.
|
||||
- It likely uses the shape-spec skill, coord messages (POST to /api/coord/messages), and analysis of the RMM codebase (via grep or deep-explore if available).
|
||||
- Use `spawn_subagent` for parts of the analysis if complex.
|
||||
- The output often produces plan.md / shape.md etc. in a specs/ folder or directly messages via the coord system.
|
||||
|
||||
This command bridges user requests to the active development process on the gururmm submodule.
|
||||
Reference in New Issue
Block a user