brainstorming

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

Security Scan

The skill's requirements and instructions are coherent with a brainstorming/design workflow; it asks the agent to read project state and optionally write/commit design docs, which matches its stated purpose.

Purpose & Capability

Name and description (brainstorming into designs) match the instructions: understanding project context, asking clarifying questions, proposing approaches, and producing a design. The references to writing docs and committing to git are reasonable follow-ups for turning a validated design into artifact(s).

Instruction Scope

Instructions explicitly tell the agent to inspect the current project (files, docs, recent commits) and to write design files under docs/plans/ and commit them. This is within scope for a design-oriented skill, but it grants the agent permission to read repository contents and to create/commit files — users should be aware the skill expects repo read/write access and may invoke git operations.

Install Mechanism

Instruction-only skill with no install spec or external downloads. There is no code to write to disk beyond what the agent itself may create in the workspace, so install risk is minimal.

Credentials

The skill declares no environment variables, binaries, or config paths. The actions it requests (reading repo, writing docs, committing) align with typical workspace permissions and do not demand unrelated credentials.

Persistence & Privilege

always is false and the skill is user-invocable; it does not request elevated or persistent platform privileges. The only persistence implied is creating/committing files inside the project repository, which is appropriate for its purpose.

Assessment

This skill is coherent for design work, but it assumes the agent can read the repository and may create and commit files. Before enabling, confirm you trust the agent with workspace read/write and git access. If you want to limit risk, require manual confirmation before any commits, run the skill in a sandbox branch/worktree, or review produced docs before merging. Also be aware the skill references other optional internal 'superpowers' skills — if those are enabled they may expand behavior (e.g., automated git actions).

Brainstorming Ideas Into Designs

Overview

Help turn ideas into fully formed designs and specs through natural collaborative dialogue.

Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.

The Process

Understanding the idea:

• Check out the current project state first (files, docs, recent commits)
• Ask questions one at a time to refine the idea
• Prefer multiple choice questions when possible, but open-ended is fine too
• Only one question per message - if a topic needs more exploration, break it into multiple questions
• Focus on understanding: purpose, constraints, success criteria

Exploring approaches:

• Propose 2-3 different approaches with trade-offs
• Present options conversationally with your recommendation and reasoning
• Lead with your recommended option and explain why

Presenting the design:

• Once you believe you understand what you're building, present the design
• Break it into sections of 200-300 words
• Ask after each section whether it looks right so far
• Cover: architecture, components, data flow, error handling, testing
• Be ready to go back and clarify if something doesn't make sense

After the Design

Documentation:

• Write the validated design to docs/plans/YYYY-MM-DD-<topic>-design.md
• Use elements-of-style:writing-clearly-and-concisely skill if available
• Commit the design document to git

Implementation (if continuing):

• Ask: "Ready to set up for implementation?"
• Use superpowers:using-git-worktrees to create isolated workspace
• Use superpowers:writing-plans to create detailed implementation plan

Key Principles

• One question at a time - Don't overwhelm with multiple questions
• Multiple choice preferred - Easier to answer than open-ended when possible
• YAGNI ruthlessly - Remove unnecessary features from all designs
• Explore alternatives - Always propose 2-3 approaches before settling
• Incremental validation - Present design in sections, validate each
• Be flexible - Go back and clarify when something doesn't make sense