sf-brainstorm

/sf-brainstorm

Persona dispatch. This skill dispatches its research personas as isolated subagents — see the dispatching-parallel-personas skill for the mechanics (isolated subagents, same-response parallelism, same-file-conflict check). Research personas are referenced from ../sf-plan/references/personas/.

Principles enforced: 4 (spec is the artifact, in embryo). See PRINCIPLES.md.

Strategy grounding: If a STRATEGY.md exists at the repo root, read it first so the brainstorm stays inside the program's target problem, approach, and personas.

Copy-paste-to-agent

Run a Salesforce-aware brainstorm to refine a feature idea before planning. Ask one
focused question at a time about problem, users, scale, and constraints. For each viable
approach, evaluate the declarative-vs-code trade-off (governor limits, maintenance,
testability, sharing impact). Save the result to docs/brainstorms/YYYY-MM-DD-{slug}.md as
input to /sf-plan — this is pre-spec exploration, not a spec.

<feature_description> #$ARGUMENTS </feature_description>

Interaction Method

When asking the user a question, use the platform's blocking question tool: AskUserQuestion in Claude Code (call ToolSearch with select:AskUserQuestion first if its schema isn't loaded), request_user_input in Codex, ask_user in Gemini. Fall back to numbered options in chat only when no blocking tool exists in the harness or the call errors. Never silently skip the question.

Ask one question at a time. Prefer a concise single-select choice when natural options exist.

You are facilitating a brainstorm session to explore an idea before planning. Your job is to help think through approaches, trade-offs, and Salesforce-specific considerations.

Goal

Explore and refine: $ARGUMENTS.idea

---

Phase 0: Assess Clarity

Rate the idea's clarity:

• Clear: User knows what they want, specific requirements → Move fast through Phase 1

• Exploratory: User has a general direction but needs options → Spend time in Phase 2