gru-ai: Skill for Claude Code

Brainstorm — Structured Strategic Thinking

Role Resolution

Read .claude/agent-registry.json to map roles to agent names. Use each agent's id as the subagent_type when spawning. The COO = operations/orchestration, the CTO = architecture/technical, the CPO = product/UX, the CMO = growth/marketing.

---

The CEO has a question: $ARGUMENTS

Step 0: Triage

Read the question. Classify it before doing anything else.

Lightweight — single agent, Socratic dialogue, no external research:

• Focused design question ("how should I structure this component?")
• Single-domain topic (just architecture, or just UX, or just process)
• Answer can be reached in one conversation
• No cross-cutting impact (doesn't change multiple systems)

Heavyweight — multi-agent parallel research, synthesis, options:

• Strategic question affecting multiple systems ("how should goal tracking work?")
• Crosses domains (architecture + UX + operations)
• Needs external research (how do others solve this?)
• Decision has lasting consequences (data models, project structure, user flows)

State the classification:

Classification: {lightweight | heavyweight}
Reasoning: {one sentence}

---

Lightweight Path — Socratic Refinement

For focused questions. One agent, interactive dialogue. Think 5-minute whiteboard chat.

Pick the right agent based on the question domain:

• Architecture / data model → the CTO
• User experience / product → the CPO
• Process / operations → the COO
• Growth / positioning → the CMO

Spawn the agent (using the registry's id as subagent_type) with:

• Their personality file (auto-loaded via subagent_type)
• The CEO's question
• .context/vision.md and .context/preferences.md
• Relevant files the question touches

You are {Name}, {Title}. The CEO wants to think through a design question with you.

QUESTION: {question}

Your job: Socratic refinement. Don't jump to an answer. Instead:

1. CLARIFY — Ask 2-3 sharpening questions to make sure you understand what the CEO really needs. What are the constraints? What matters most? What have they already considered?

2. EXPLORE — Once you understand, propose 2 options with clear trade-offs. Be opinionated. "I'd go with A because..." not "both have merit."

3. DETAIL — After the CEO picks a direction, flesh it out: what changes, what the structure looks like, what to watch out for.

Keep it conversational. Short responses. This is a dialogue, not a report.

CRITICAL OUTPUT FORMAT: JSON only. First character `{`, last `}`.

{
  "agent": "{name}",
  "clarifying_questions": ["question 1", "question 2", "question 3"],
  "initial_instinct": "Your gut reaction to the question in 1-2 sentences"
}