Groove Work Brainstorm

This is a structured brainstorming step that lives before you start planning or coding. It walks you through a dialogue to define scope, makes you list key decisions with rationale, and surfaces open questions without trying to answer them yet. The real discipline here is YAGNI enforcement: it actively pushes back on scope creep and keeps you from jumping into implementation details. Output gets saved either as a markdown doc using a template or directly into your task backend (Linear, Jira, whatever you've configured in .groove/index.md). It's opinionated about staying in discovery mode, which is honestly refreshing if you tend to solution too early.

skills.sh installs: 551
GitHub stars: 6
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add andreadellacorte/groove --skill groove-work-brainstorm --agent claude-code

Installs into .claude/skills of the current project.

Files

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.backend from .groove/index.md to determine backend
Use template at skills/groove-work-brainstorm/templates/brainstorm-doc.md for 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-create if tasks != none (title YYYY-MM-DD, Brainstorm)