andreadellacorte/groove

groove-work-brainstorm

Clarify scope through dialogue, surface key decisions and open questions. Use before planning.

First seen Mar 3, 2026

Installation

$ npx skills add andreadellacorte/groove --skill groove-work-brainstorm

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from andreadellacorte/groove · top by installs.

npx skills add andreadellacorte/groove

Browse all from andreadellacorte/groove

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 5
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT
Allowed toolsRead Write Edit Glob Grep Bash(git:*) AskUserQuestion
More metadata
author
andreadellacorte

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,413 B
  • docs SUMMARY.md 121 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 544 installs

SKILL.md

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)