groove-work-brainstorm

어떤 스킬인가요?

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

설치 방법

프로젝트 폴더에서 아래 명령어를 실행하고, 설치할 에이전트를 선택하세요.

설치 명령을 직접 실행해야 적용됩니다. 지원 에이전트와 필요한 권한·라이선스는 제작자의 안내를 확인하세요.

스킬 원문 파일

---
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
metadata:
  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.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`)

# Brainstorm: [TOPIC]

## What We're Building
[scope, not implementation]

## Why This Approach
[rationale over alternatives]

## Key Decisions
- [decision]: [rationale]

## Open Questions
- [question]

## Next Steps
- [ ] Plan stage