Brainstorming.Conflict

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

Security Scan

This is an instruction-only 'brainstorming → design' helper that reads the project workspace, produces a design doc, and commits it to git; its requested actions and lack of credentials/install steps are coherent with that purpose.

Purpose & Capability

The skill's name/description (brainstorming → turn ideas into designs) matches the instructions (ask questions, propose approaches, produce design docs). Minor inconsistencies: the package listing shows the skill as 'Brainstorming.Conflict' while SKILL.md and _meta.json use 'brainstorming', and ownerId differs between registry metadata and _meta.json — likely a metadata mismatch but not evidence of malicious intent.

Instruction Scope

Instructions explicitly tell the agent to inspect the current project (files, docs, recent commits), iteratively ask questions, write a design to docs/plans/YYYY-MM-DD-<topic>-design.md and commit it. All of these actions are within the stated purpose. Users should note the skill will read and modify repository files and create commits.

Install Mechanism

No install spec and no code files — instruction-only. This minimizes risk because nothing is downloaded or written to disk by an installer.

Credentials

No environment variables, credentials, or config paths are requested. The instructions reference git operations and other optional 'superpower' skills, which may require credentials if invoked, but this skill itself does not ask for secrets.

Persistence & Privilege

always is false and model invocation is not disabled (normal). The skill requests no persistent presence or elevated privileges. It does instruct committing a file to the repository (normal for a design helper) but does not instruct modifying other skills or system configurations.

Assessment

This skill is coherent for converting ideas into documented designs. Before installing or running it: (1) be aware it will read your repository files and create/commit design documents — review any commits it creates; (2) the skill references other 'superpower' skills (e.g., for git worktrees) which may request credentials if used — the brainstorming skill itself does not request secrets; (3) there are minor metadata mismatches (name/ownerId) — consider verifying the source/owner before trusting automated commits; (4) if you want to avoid repository changes, run it in a sandbox branch or local copy and inspect outputs before pushing to remote.

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