Brainstorm project ideas and requirements using Socratic questioning and ideation techniques
Guides project ideation through structured Socratic questioning to define problems, analyze constraints, and explore solutions. Use it at the start of any project to create a comprehensive project brief that captures requirements and decisions before implementation.
/plugin marketplace add athola/claude-night-market/plugin install attune@claude-night-marketFacilitate project ideation through Socratic questioning, constraint analysis, and creative exploration.
# Start interactive brainstorming session
/attune:brainstorm
# Brainstorm with specific domain
/attune:brainstorm --domain "web application"
# Resume previous brainstorm
/attune:brainstorm --resume
When superpowers plugin is available:
Skill(superpowers:brainstorming) for Socratic methodWithout superpowers:
# 1. Invoke brainstorming skill
Skill(attune:project-brainstorming)
# 2. Guide through phases:
# - Problem definition
# - Constraint identification
# - Solution exploration
# - Approach comparison
# - Decision documentation
# 3. Generate project brief
# - Saved to docs/project-brief.md
# - Includes problem, goals, constraints, approach
# 4. Transition to specification
# Next: /attune:specify (use brief as input)
Questions:
Output: Problem statement document
Questions:
Output: Constraints matrix
Techniques:
Output: Approach comparison table
Criteria:
Output: Selected approach with rationale
Sections:
Output: docs/project-brief.md
--domain <domain> - Project domain (web, cli, library, etc.)--resume - Resume previous brainstorm session--output <path> - Custom output path for brief (default: docs/project-brief.md)--skip-superpowers - Don't use superpowers integration/attune:brainstorm --domain "web application"
Session Flow:
š§ Brainstorming: Web Application Project
Problem Definition:
ā What specific problem does this web app solve?
[User input: "Help developers track technical debt"]
ā Who are the primary users?
[User input: "Development teams, tech leads"]
ā What do they currently use?
[User input: "Spreadsheets, GitHub issues, nothing systematic"]
Constraints:
ā Must integrate with existing tools (GitHub, Jira)?
[User input: "Yes, GitHub primarily"]
ā Team size and timeline?
[User input: "2 developers, 3 months MVP"]
Approaches:
1. Standalone SaaS (Django + React)
2. GitHub App integration (GitHub API + webhooks)
3. CLI tool with web dashboard (FastAPI + Vue)
...
Output: docs/project-brief.md
# Technical Debt Tracker - Project Brief
## Problem Statement
Development teams lack systematic tracking of technical debt...
## Goals
1. Centralize technical debt tracking
2. Integrate with GitHub issues
3. Provide prioritization framework
## Constraints
- 3-month timeline for MVP
- 2 developers
- Must integrate with GitHub
- No dedicated ops resources
## Selected Approach
**GitHub App integration** (Approach 2)
Rationale: Lowest friction for adoption...
## Trade-offs
- Pros: Native GitHub integration, automatic discovery
- Cons: Locked into GitHub ecosystem
/attune:brainstorm --resume
Loads previous session state from .attune/brainstorm-session.json
# [Project Name] - Project Brief
## Problem Statement
[Clear description of the problem being solved]
## Goals
1. [Primary goal]
2. [Secondary goal]
...
## Success Criteria
- [ ] [Measurable success criterion]
- [ ] [Measurable success criterion]
...
## Constraints
- **Technical**: [Technical constraints]
- **Resources**: [Time, budget, team]
- **Compliance**: [Regulatory requirements]
- **Integration**: [System dependencies]
## Approach Comparison
### Approach 1: [Name]
**Pros**: ...
**Cons**: ...
**Risk**: ...
### Approach 2: [Name] ā SELECTED
**Pros**: ...
**Cons**: ...
**Risk**: ...
## Rationale for Selection
[Explanation of why this approach was chosen]
## Trade-offs Accepted
- [Trade-off 1 with mitigation]
- [Trade-off 2 with mitigation]
## Out of Scope
- [Explicitly excluded feature]
- [Deferred capability]
## Next Steps
1. /attune:specify - Create detailed specification
2. /attune:plan - Plan architecture and implementation
3. /attune:init - Initialize project structure
Brainstorm sessions are saved to .attune/brainstorm-session.json:
{
"session_id": "20260102-143022",
"phase": "approach-selection",
"problem": "...",
"constraints": [...],
"approaches": [...],
"decisions": {},
"timestamp": "2026-01-02T14:30:22Z"
}
/attune:brainstorm ā You are here
ā
/attune:specify ā Define requirements
ā
/attune:plan ā Plan architecture
ā
/attune:init ā Initialize project
ā
/attune:execute ā Implement systematically
/attune:specify - Create detailed specification from brief/attune:plan - Plan project architecture/imbue:feature-review - Review feature worthinessSkill(attune:project-brainstorming) - Brainstorming methodologySkill(superpowers:brainstorming) - Socratic questioning (if available)Skill(imbue:scope-guard) - Anti-overengineering checksWhen superpowers is installed, this command automatically:
Skill(superpowers:brainstorming) for questioning frameworkCheck if superpowers is available:
/plugin list | grep superpowers
Install superpowers:
/plugin marketplace add obra/superpowers
/plugin install superpowers@superpowers-marketplace
/brainstormYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores requirements and design before implementation.
/brainstormUse when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes