chore: publish from main

skills/ai-team-orchestration/references/brainstorm-format.md

@@ -14,16 +14,16 @@ This is a creative session — no idea is too wild in Phase 1.
 - Thinks about: user delight, accessibility, "would this be fun?"
 - Tendency: pushes for features that spark joy, pushes back on anything that feels like homework
 
-### Milo (Art/Visual Director)
-- Thinks about: visual identity, cohesion, "does this look and feel right?"
-- Tendency: wants everything beautiful, sometimes at odds with engineering feasibility
+### Milo (Experience/Design Perspective)
+- Thinks about: accessibility, presentation, content, cohesion, "does this feel right?"
+- Tendency: advocates for user experience, sometimes at odds with engineering feasibility
 
-### Nova (Frontend Engineer)
-- Thinks about: component architecture, state management, "can we actually build this?"
+### Nova (Client/Interaction Perspective)
+- Thinks about: user-facing behavior, interaction, state, "can we actually build this?"
 - Tendency: pragmatic, flags scope risks, suggests simpler alternatives
 
-### Sage (Backend Engineer)
-- Thinks about: data model, API design, security, "where do secrets live?"
+### Sage (Core/Service Perspective)
+- Thinks about: domain logic, data, services, integrations, security, "where do risks live?"
 - Tendency: security-first, sometimes over-engineers, good at spotting edge cases
 
 ### Remy (Producer)
@@ -49,12 +49,7 @@ Phase 3 — Final Pitches:
 Each concept includes: name, description, pros, cons, estimated effort.
 Team vote with brief justification from each voter.
 
-Output all phases as separate files:
-- docs/brainstorm/01-free-ideation.md
-- docs/brainstorm/02-discussion.md
-- docs/brainstorm/03-concept-[A/B/C...].md (one per concept)
-- docs/brainstorm/04-team-vote.md
-- docs/brainstorm/05-summary.md
+Write the result to one concise design note unless the project needs separate artifacts.
 ```
 
 ## Tips
@@ -62,12 +57,12 @@ Output all phases as separate files:
 - **Name each agent** — "you are the full team" produces bland consensus
 - **Define tendencies** — gives the LLM permission to disagree
 - **Require disagreements** — "at least 2 genuine disagreements" prevents groupthink
-- **Separate files** — forces structured output, makes it reviewable
+- **Keep the output proportional** — one note is usually enough
 - **Customize personas** — adjust for your domain (e.g., replace Kira with a Data Scientist for ML projects)
 
 ## Mini-Brainstorm (Quick Version)
 
-For smaller decisions:
+For smaller decisions (e.g., "how should we implement the scoreboard?"):
 
 ```
 Run a team brainstorm about [TOPIC].