| name | brainstorm |
| description | Ideation, option generation, and feature exploration. Use when the user wants to brainstorm ideas, explore options, compare approaches, or generate creative solutions. Triggers: brainstorm, ideate, options, ý tưởng, so sánh phương án. |
| encoding | UTF-8 |
| agents | ["project-planner","orchestrator"] |
| related-skills | ["plan","create","orchestrate"] |
Memory Protocol
START: Read .ai-memory.md from project root. Use its context to understand project history, tech stack, past decisions, and constraints. If missing, note this and create it after completing this task.
END: Update .ai-memory.md using Memory Compaction Rules with: problem, options considered, chosen direction, constraints, and new project understanding.
Goal
Help the user explore many realistic options before implementation.
Agent Routing
- If brainstorm involves system architecture → read
.kiro/skills/agents/agents/project-planner.md and apply its knowledge
- If brainstorm spans multiple domains → read
.kiro/skills/agents/agents/orchestrator.md and apply its knowledge
- If brainstorm is about UI/UX → read
.kiro/skills/agents/agents/frontend-specialist.md and apply its knowledge
- If brainstorm is about APIs/backend → read
.kiro/skills/agents/agents/backend-specialist.md and apply its knowledge
Socratic Gate
Before generating options, verify:
- What problem are we solving? (clarity check)
- What constraints exist? (budget, time, tech stack, team)
- Who are the users/stakeholders?
If any answer is unclear, ASK before proceeding.
Workflow
- Read Memory — Load
.ai-memory.md for project context.
- Restate the problem in one or two sentences.
- Identify constraints, assumptions, and success criteria from the repository and the prompt.
- Produce 3-7 strong options with pros, cons, complexity, and risks.
- Call out the most practical option and the boldest option.
- End with a recommended next step or implementation path.
- Update Memory — Save new understanding to
.ai-memory.md.
Output format
- Problem framing
- Constraints
- Options (3-7 with pros/cons/complexity/risk for each)
- Recommendation (most practical + boldest)
- Next step
Checklist
Rules
- Prefer practical ideas grounded in the current project.
- Avoid pretending uncertain assumptions are facts.
- If code context matters, inspect the repo structure first.
- If an option implies broad code changes, call it out explicitly and suggest a minimal path first.
- Always read and update the memory file.
Quality Gate
After completing, read .kiro/skills/_scripts/checklist.md for cross-cutting quality checks.
Encoding
All code snippets and example files referenced or produced by this skill must be UTF-8 encoded. When applicable, include encoding: "UTF-8" in SKILL.md front-matter and ensure saved files use UTF-8 (no BOM).
Related Skills
/plan → read .kiro/skills/plan/SKILL.md — Turn chosen option into actionable plan
/create → read .kiro/skills/create/SKILL.md — Implement the chosen option
/orchestrate → read .kiro/skills/orchestrate/SKILL.md — Coordinate multi-domain brainstorm results