skilld
All skills
obra avatar

/brainstorming

@5bf4e78 official
by Jesse Vincentobra/superpowers293k stars
26,244

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Ask your Agent

Use this Skill: https://skilld.dev/gh/obra/superpowers/brainstorming

This session only. Nothing lands on disk.

spec-document-reviewer-prompt.md

≈437 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Spec Document Reviewer Prompt Template

Use this template when dispatching a spec document reviewer subagent.

Purpose: Verify the spec is complete, consistent, and ready for implementation planning.

Dispatch after: Spec document is written to docs/superpowers/specs/

Subagent (general-purpose):
  description: "Review spec document"
  prompt: |
    You are a spec document reviewer. Verify this spec is complete and ready for planning.

    **Spec to review:** [SPEC_FILE_PATH]

    ## What to Check

    | Category | What to Look For |
    |----------|------------------|
    | Completeness | TODOs, placeholders, "TBD", incomplete sections |
    | Consistency | Internal contradictions, conflicting requirements |
    | Clarity | Requirements ambiguous enough to cause someone to build the wrong thing |
    | Scope | Focused enough for a single plan — not covering multiple independent subsystems |
    | YAGNI | Unrequested features, over-engineering |

    ## Calibration

    **Only flag issues that would cause real problems during implementation planning.**
    A missing section, a contradiction, or a requirement so ambiguous it could be
    interpreted two different ways — those are issues. Minor wording improvements,
    stylistic preferences, and "sections less detailed than others" are not.

    Approve unless there are serious gaps that would lead to a flawed plan.

    ## Output Format

    ## Spec Review

    **Status:** Approved | Issues Found

    **Issues (if any):**
    - [Section X]: [specific issue] - [why it matters for planning]

    **Recommendations (advisory, do not block approval):**
    - [suggestions for improvement]

Reviewer returns: Status, Issues (if any), Recommendations

Source: SKILL.md on GitHub

Third-party checks

1 alert12d5 checks · Risk SAFE
  • Gen Agent Trust Hub12d

    The brainstorming skill is a robust tool for design collaboration that includes a 'Visual Companion' local web server for displaying mockups. The skill demonstrates high security awareness by implementing session tokens, owner-only file permissions, and automatic server termination when the agent process exits. While it captures user interactions from the browser, it does so using structured data formats, minimizing injection risks.

  • Socket12d

    1 alert: gptAnomaly

  • Snyk12d

    Risk: LOW · No issues

  • Runlayer6mo

    3/8 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 5bf4e78. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 6 days ago.

Activeupdated 2 weeks ago

Topics

  • Design
  • brainstorming
  • requirements
  • planning
  • specification
  • collaboration
  • workflow

README badge

README badge for obra/superpowers/brainstorming

What it does

Enforces a structured brainstorming process before any implementation work: explores project context, asks clarifying questions one at a time, proposes 2-3 design approaches, presents a design for user approval, and writes a spec document to `docs/superpowers/specs/`. Prevents coding, scaffolding, or any implementation action until design approval is complete.

Generated from the current SKILL.md.

Frequently asked

Does this skill write code or just plan design?
This skill only plans and designs. It has a hard gate that prevents any code writing, scaffolding, or implementation until the user approves a written design spec. After approval, it invokes the writing-plans skill to create an implementation plan.
When should I use this skill?
Use this before any creative work — creating features, building components, adding functionality, or modifying behavior. It applies to every project regardless of perceived simplicity, including todo lists and single-function utilities.
What output does this skill produce?
A written design spec saved to `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md`, covering architecture, components, data flow, error handling, and testing. The spec is committed to git and reviewed by the user before implementation planning begins.
Does this skill handle large projects with multiple subsystems?
If a project describes multiple independent subsystems, the skill flags this immediately and helps decompose it into sub-projects. Each sub-project gets its own design spec, implementation plan, and build cycle.
Can this skill create visual mockups?
Yes, via an optional Visual Companion tool that renders mockups, diagrams, and layout comparisons in a browser. The skill offers it only when visual content would help clarify upcoming questions.

Generated from the current SKILL.md. These answers refresh after source changes.