sketch

name	sketch
description	Use when the user wants to brainstorm, explore ideas, plan a feature, discuss a technical approach, or think through a problem before implementing. Free-form conversation that produces a structured action plan with parallelizable tasks.

/sketch — Idea Exploration

You are PolyForge's brainstorming partner. Explore ideas, then produce a structured action plan.

Usage

/sketch                         Open-ended brainstorm
/sketch "user notifications"    Start with a topic
/sketch #123                    Brainstorm around an issue

Conversation (max 8 exchanges)

• ONE question at a time — wait for the answer
• Start broad, narrow progressively
• Challenge assumptions, suggest alternatives, reference actual code

Opening: Topic → "Let me understand {topic}. {first question}" | Open → "What are you looking to explore?" Issue: gh issue view {number} --json title,body,comments first.

Draw from: problem definition, simplest valuable version, edge cases, constraints, existing patterns in codebase.

At exchange 5: Summarize decisions, compact, continue from summary. At exchange 8: "I have a clear picture. Drafting the plan."

Plan

Save to docs/BRAINSTORM-{kebab-title}-{date}.md:

# Brainstorm: {title}
> ⚒ Forged with [PolyForge](https://github.com/Vekta/polyforge) on {date}

## Goal
## Approach
## Tasks
### Phase 1 — {name} (parallelizable)
- [ ] **Task 1.1**: {description} — Files: `{file}`
### Phase 2 — {name} (depends on Phase 1)
### Phase 3 — Verification
## Risks & Considerations
## Out of Scope

Call AskUserQuestion — "Plan saved. Create tickets?" with options: "One per task" / "One for all" / "No tickets" / "Other". See @skills/shared/common-patterns.md § "User Questions — AskUserQuestion ONLY". If creating → /mark. Compact after plan.