Brainstorming

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.

Security Scan

The skill's instructions, requested privileges, and absence of installs/credentials are consistent with a brainstorming/design helper that reads project state and writes design documents to the repo.

Purpose & Capability

Name and description match the behavior in SKILL.md: the skill explores intent, asks questions, proposes approaches, and produces a written design. It explicitly reads project state and writes design docs/commits them, which is coherent for a design workflow.

Instruction Scope

Instructions direct the agent to inspect the current project (files, docs, recent commits), produce a design in 200–300 word sections, write the validated design to docs/plans/YYYY-MM-DD-<topic>-design.md, and commit to git. This is within the stated purpose, but it does grant the agent permission to read repository contents and modify the repo (create/commit files). Users should expect those side effects.

Install Mechanism

No install spec and no code files; the skill is instruction-only, which minimizes installation risk.

Credentials

The skill requests no environment variables or external credentials. However, its runtime actions (reading repo state and committing) implicitly rely on access to the local repository and any git credentials/config the environment provides. No unrelated secrets are requested.

Persistence & Privilege

The skill will create persistent artifacts in the repository (design docs and git commits). always:false (default) and autonomous invocation is not disabled, so the agent could act autonomously when invoked. The skill does not request system-wide privileges or modify other skills.

Assessment

This skill is coherent for turning ideas into documented designs, but be aware it will read your repository and write/commit design files. Before installing or invoking it: 1) Ensure you want the agent to access the repo and make commits (consider requiring confirmation before committing or using a separate branch). 2) Verify the agent's git identity and remote push behavior (it may use local git credentials). 3) Review generated files and commits before pushing them upstream. 4) If you prefer more control, ask the agent to produce the design as output rather than committing it automatically.

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