groove-work-brainstorm

groove-work-brainstorm is a skill for Claude Code from andreadellacorte/groove. It costs 24 tokens per session (316 once invoked), scanned A, original, MIT.

A guided conversation process for defining the scope of a work request before planning its implementation. It records important decisions, reasons, and unanswered questions, while applying YAGNI—the practice of avoiding work that is not yet needed.

In plain words
What is it for?
Use it to clarify goals, constraints, decisions, and open questions before creating an implementation plan or recording the result in the configured task system.
Why use it?
It helps turn a broad or unclear request into a deliberately limited piece of work. This reduces scope creep and keeps unresolved questions visible for the planning stage.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Good fit Use it to clarify goals, constraints, decisions, and open questions before creating an implementation plan or recording the result in the configured task system.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/andreadellacorte/groove/groove-work-brainstorm
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add andreadellacorte/groove --skill groove-work-brainstorm
Clone the repo
git clone --depth 1 https://github.com/andreadellacorte/groove

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for groove-work-brainstorm

README.md
[![agentmods](https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-work-brainstorm/github.svg)](https://agentmods.dev/skills/andreadellacorte/groove/groove-work-brainstorm)
Your own site
<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-work-brainstorm"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-work-brainstorm/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for groove-work-brainstorm

Your own site · 80×15
<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-work-brainstorm"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-work-brainstorm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 316 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 4 Nov 2026
  • Snyk pass 4 Nov 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00316
Opus 5.5 $0.00010 $0.00126
Sonnet 5.5 $0.00005 $0.00063
Haiku 4.5 $0.00002 $0.00032

Measured 2mo ago against content hash a3ba2560ef10, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

groove-work-brainstorm scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/groove-work-brainstorm/SKILL.md · 33 lines

What it actually says

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)
Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 33 lines · 24 tokens per session scan A a3ba2560ef10

Subscribe to this mod's changes

groove-work-brainstorm is a skill published in the GitHub repository andreadellacorte/groove (6 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 316 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

groove-work-brainstorm compared with skills from other repositories

groove-work-brainstorm next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
groove-work-brainstormandreadellacorte/grooveSkill63mo agoMITA24Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code