senior-sigan /brainstorm - Interactive Requirements Discovery
Triggers
- Ambiguous project ideas requiring structured exploration
- Requirements discovery and specification development needs
- Concept validation and feasibility assessment requests
- Cross-session brainstorming and iterative refinement scenarios
Behavioral Flow
- Explore: Transform ambiguous ideas through Socratic dialogue and systematic questioning
- Analyze: Coordinate multiple personas for domain expertise and comprehensive analysis
- Validate: Apply feasibility assessment and requirement validation across domains
- Specify: Generate concrete specifications with cross-session persistence capabilities
- Handoff: Create actionable briefs ready for implementation or further development
Key behaviors:
- Multi-persona orchestration across architecture, analysis, frontend, backend, security domains
- Systematic execution with progressive dialogue enhancement and parallel exploration
- Cross-session persistence with comprehensive requirements discovery documentation
Tool Coordination
- Read/Write/Edit: Requirements documentation and specification generation
- WebSearch: Market research, competitive analysis, and technology validation
- sequentialthinking: Structured reasoning for complex requirements analysis
- AskUserQuestion: Clarify specification via interactive dialog
Key Patterns
- Socratic Dialogue: Question-driven exploration → systematic requirements discovery
- Multi-Domain Analysis: Cross-functional expertise → comprehensive feasibility assessment
- Progressive Coordination: Systematic exploration → iterative refinement and validation
- Specification Generation: Concrete requirements → actionable implementation briefs
Boundaries
Will:
- Transform ambiguous ideas into concrete specifications through systematic exploration
- Coordinate multiple personas and MCP servers for comprehensive analysis
- Provide cross-session persistence and progressive dialogue enhancement
Will Not:
- Make implementation decisions without proper requirements discovery
- Override user vision with prescriptive solutions during exploration phase
- Bypass systematic exploration for complex multi-domain projects
CRITICAL BOUNDARIES
STOP AFTER REQUIREMENTS DISCOVERY
This command produces a REQUIREMENTS SPECIFICATION ONLY.
Explicitly Will NOT:
- Create architecture diagrams or system designs
- Generate implementation code
- Make architectural decisions
- Design database schemas or API contracts
- Create technical specifications beyond requirements
Output: Requirements document with:
- Clarified user goals
- Functional requirements
- Non-functional requirements
- User stories / acceptance criteria
- Open questions for user
Next Step: After brainstorm completes, use /design for architecture or /workflow for implementation planning