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 internally consistent with a brainstorming/design-assistant: it reads project context, drafts designs, writes docs, and optionally commits them to git — nothing requested is disproportionate or unrelated to its stated purpose.

Purpose & Capability

Name/description (brainstorming into designs) align with instructions to explore intent, propose approaches, and produce design docs. References to creating docs and committing to git are coherent for a design-to-implementation workflow.

Instruction Scope

Instructions explicitly tell the agent to inspect the current project state (files, docs, recent commits), write a design file under docs/plans/..., and commit it to git. This is consistent with the purpose but does require repository/workspace and git access; users should be aware the skill expects read/write access to the project workspace and ability to run git.

Install Mechanism

Instruction-only skill with no install spec and no code files. Low-risk: nothing is downloaded or written by an installer.

Credentials

No environment variables, credentials, or config paths are requested. The declared requirements match the instructions (workspace and git access implied but not declared as secrets).

Persistence & Privilege

always:false and no modifications to other skills or system-wide settings. The skill asks to write files and commit to git (normal for a design workflow) but does not request persistent elevated privileges.

Assessment

This skill is coherent for design work, but be aware it expects access to your project workspace and permission to run git commands (it will write docs and commit them). If you do not want it modifying your repo, run it in a sandbox branch or worktree, or deny git write access. Also note it references optional helper skills (style, git-worktrees, writing-plans); those are not required but could change behavior if installed. Review any commits the skill creates before merging them into main.

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