andreadellacorte/groove-work-brainstorm
skills/groove-work-brainstorm/SKILL.md
Clarify scope through dialogue, surface key decisions and open questions. Use before planning.
$ install --global
skillsauthnpx skillsauth add andreadellacorte/groove groove-work-brainstormInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:33 PM0.4s1 file scanned
SKILL.md
- name:
- groove-work-brainstorm
- description:
- Clarify scope through dialogue, surface key decisions and open questions. Use before planning.
- license:
- MIT
- allowed-tools:
- Read Write Edit Glob Grep Bash(git:*) AskUserQuestion
- author:
- andreadellacorte
groove-work-brainstorm
Outcome
Scope is clarified through dialogue. Key decisions and open questions are surfaced. Output is captured as a brainstorm doc or task in the configured backend.
Acceptance Criteria
- Scope is clearly defined and deliberately constrained (YAGNI applied)
- Key decisions are listed with rationale
- Open questions are listed (not resolved — resolution happens in plan)
- Output exists either as a brainstorm doc or as a task body in the backend
- Stage task created in backend:
YYYY-MM-DD, Brainstorm
Constraints
- Read
tasks.backendfrom.groove/index.mdto determine backend - Use template at
skills/groove-work-brainstorm/templates/brainstorm-doc.mdfor doc output - Enforce YAGNI — scope is deliberately constrained at this stage; push back on scope creep
- Do not start planning implementation here — that belongs in
/groove-work-plan - Ask clarifying questions before finalising scope; do not assume
- If user provides $ARGUMENTS, use as the topic/title for the brainstorm
- Create stage task via
/groove-utilities-task-createiftasks != none(titleYYYY-MM-DD, Brainstorm)
Related Skills
andreadellacorte/groove-utilities-stats
testing
VerifiedTrustedCommunity
Quantified compound-loop dashboard: lessons captured vs graduated, adherence streaks, and task velocity. Use to see whether the workflow is actually compounding.
5SKILL.mdUpdated Jun 5, 2026
andreadellacorte/groove
data-ai
VerifiedTrustedCommunity
Groove engineering workflow system. Top-level entry point. Use groove-daily-*, groove-work-*, groove-utilities-*, groove-admin-* for all workflow and admin commands.
5SKILL.mdUpdated Apr 24, 2026
andreadellacorte/groove-work-compound
documentation
VerifiedTrustedCommunity
Document lessons, update rules/templates/docs. Use to capture learnings after review.
5SKILL.mdUpdated Apr 24, 2026
andreadellacorte/groove-utilities-prime
tools
VerifiedTrustedCommunity
Load groove workflow context into the conversation. Run at the start of every session.
5SKILL.mdUpdated Apr 24, 2026