mcpField
G
groove-work-brainstorm

groove-work-brainstorm

github.com/andreadellacorteAgent workflows6550 installsUpdated 14w ago
Repository

About groove-work-brainstorm

A Groove brainstorming skill that clarifies and constrains a topic through questions, then records decisions, rationale and open questions in a document or configured task backend. It keeps implementation planning for a later stage.

Key features

  1. 01Clarifies scope through questions
  2. 02Applies YAGNI to constrain scope
  3. 03Records decisions and open questions
  4. 04Writes a brainstorm document or task
  5. 05Creates a dated stage task when enabled

Use cases

  1. 01Defining scope before implementation planning
  2. 02Capturing rationale and unresolved questions
  3. 03Recording brainstorm results in the configured backend

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/andreadellacorte/groove --skill groove-work-brainstorm

After installing, type/groove-work-brainstormin Claude Code to confirm it loaded.

Bundled filestemplates/brainstorm-doc.md

Details

From the project README

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)

Comments

Markdown supported