| name | ideate |
| tier | opt-in |
| description | Feature brainstorming and ideation - value/effort matrix, feature briefs |
| disable-model-invocation | false |
| allowed-tools | ["Read","Grep","Glob","mcp__igris-brain__igris_brief_create"] |
| triggers | ["IDEATE","ORACLE","suggest features","brainstorm","what could we add","feature ideas","suggest improvements"] |
Ideate Skill
Feature brainstorming and ideation workflow. Generates ideas, assesses value vs effort, and creates FR-XXX briefs for promising concepts.
Arguments
$ARGUMENTS can specify focus area:
- Empty: General brainstorming for the project
- Topic: Focus brainstorming on specific area (e.g., "UX", "performance", "API")
Capabilities
- Feature Brainstorming - Generate new feature ideas
- Improvement Suggestions - Enhance existing features
- UX Analysis - Identify user experience gaps
- Integration Ideas - Suggest useful integrations
- Value Assessment - Estimate idea impact vs effort
- Feature Ideation Audit - Systematic feature generation with FR-XXX briefs
Value/Effort Matrix
Use this matrix to prioritize ideas:
| Low Effort | Med Effort | High Effort
---------+------------+------------+-------------
High Val | DO NOW | PLAN | CONSIDER
Med Val | QUICK WIN | BACKLOG | MAYBE
Low Val | IF TIME | SKIP | SKIP
Workflow
Step 1: Understand Context
- Read project structure and purpose
- Understand existing features
- Identify target users
- Review existing briefs for prior ideas
Step 2: Generate Ideas
- Brainstorm features aligned with project goals
- Consider user pain points
- Look for integration opportunities
- Think about automation possibilities
Step 3: Assess Each Idea
For each promising idea:
- Value: How much does this help users? (High/Med/Low)
- Effort: How hard to implement? (Low/Med/High)
- Feasibility: Can we build this with current architecture?
- Matrix Position: DO NOW / QUICK WIN / PLAN / etc.
Step 4: Create FR Briefs
For ideas rated DO NOW or QUICK WIN:
- Create via
igris_brief_create MCP tool, fallback to cache write at ~/.igris/projects/{project}/briefs/FR-XXX-{name}.md
- Include value assessment and effort estimate
- Reference related existing features
Constraints
- NEVER implement ideas - Ideation only, create briefs
- ALWAYS assess feasibility - Don't suggest impossible features
- ALWAYS consider existing patterns - Build on what exists
- ALWAYS estimate effort honestly - No fantasy sizing
- ALWAYS tie to user value - No tech for tech's sake
Output Format
# Feature Ideation: {focus area}
## Ideas
### 1. {Idea Name}
- **Value:** High | **Effort:** Low | **Matrix:** DO NOW
- **Description:** {what it does}
- **User Benefit:** {why it matters}
- **Brief:** FR-XXX created
### 2. {Idea Name}
- **Value:** Med | **Effort:** Med | **Matrix:** BACKLOG
- **Description:** {what it does}
- ...
## Summary
- DO NOW: {count} ideas
- QUICK WIN: {count} ideas
- PLAN: {count} ideas
- BACKLOG: {count} ideas