Use Brainstorming from Superpowers to clarify what a project should accomplish before implementation. Explore the existing context, discuss approaches and trade-offs, and turn the chosen direction into a design document that can guide the next planning step without silently filling important gaps with assumptions.
Bring the current project, intended outcome, and decisions that remain open. Prepare a design discussion that compares alternatives and preserves real constraints before drafting the agreed direction, with implementation planning following rather than replacing that conversation.
Describe the user, current process, desired outcome, and constraints.
Copy the request into a new Floatboat conversation and provide the required material.
Download FloatboatPreview and copy the request. It is not sent automatically from this page.
Reference: Brainstorming https://github.com/obra/superpowers/blob/main/skills/brainstorming/SKILL.md Read the original documentation and check the current environment and dependencies. Propose any new installation or tool connection before proceeding. My task: Use Superpowers Brainstorming to plan a receipt-review workflow. Read the current project first, clarify the user outcome, and compare approaches before writing a design. Expected deliverable: Clarified requirements and compared approaches, followed by a design only after the direction is agreed.
Brainstorming is the intent-and-design Skill in Superpowers, maintained by Jesse Vincent and the project’s contributors. It helps an agent understand the desired outcome and its reasons before deciding what to build. Existing project context is read first; the conversation then explores unresolved goals, constraints, and alternatives. Substantial work moves through an agreed approach and a written design before the writing-plans companion takes over. The current source also distinguishes fully specified small tasks and users who choose to proceed without further questions. Installing the Superpowers integration keeps its bootstrap and companion instructions available; copying only this file does not recreate that broader workflow.
New features, workflow changes, and non-code projects all need an intended outcome before implementation choices. Explore how Brainstorming compares alternatives and identifies unresolved decisions while preserving the constraints that matter to the next planning stage.
A new feature should begin with the user's problem and intended outcome, considered alongside the project's existing state and constraints. Compare plausible approaches before choosing behavior or implementation details. The design should distinguish agreed decisions from open choices so planning does not quietly settle questions that were never discussed.
Reshaping a workflow starts with its current documents, the people affected, and the reason for changing it. Establish which behavior should remain and which should change before planning implementation. The proposal should connect each adjustment to its purpose rather than substitute a new process merely because it looks more structured.
A talk, process, or creative project can use the same design conversation without becoming a coding task. Clarify the audience, intended outcome, and material constraints, then compare alternatives against those needs. Carry a coherent direction and the remaining constraints into the next stage rather than invent implementation details prematurely.
A clearly specified minor task may not need an extensive design document. Read the current project context and confirm whether any consequential choice is still open, then keep the discussion proportionate to the work. Preserve the agreed scope and use the appropriate planning handoff without creating new questions or artifacts solely to make the process look complete.
Brainstorming begins with the current project and a concrete outcome to clarify. Use the relevant Superpowers setup to compare approaches and resolve missing decisions, then review a design sized to the task before handing the agreed direction into planning.
Share the intended outcome and relevant files or earlier decisions. Let existing evidence answer facts before discussing open choices.
Discuss unresolved needs and compare alternatives. Review the agent’s understanding and correct assumptions before settling the direction.
Inspect a design sized to the work and confirm it before planning. Keep the companion writing-plans Skill available for the next stage.
Read another Skill guide and check its original source before using it.
