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.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is brainstorming in obra/superpowers

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, actionable process skill with a clear sequenced workflow and an explicit feedback loop for design approval. Its only meaningful weakness is conciseness: the central 'invoke only writing-plans' constraint is repeated across several sections and could be consolidated.

Suggestions

Consolidate the repeated 'do not invoke implementation skills / only invoke writing-plans' guidance into a single authoritative statement (e.g., keep it in the Process Flow and After the Design) and reference it elsewhere rather than restating it 3-4 times.

Fix the diagram fence: '```dot' is a non-standard fence and will not render as Graphviz in most viewers; use '```graphviz' or a plain code block, or render it as a numbered fallback so the flow is legible everywhere.

Trim the Key Principles section where it duplicates The Process (e.g., 'One question at a time' and 'Explore alternatives' already appear above) to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	The body is mostly high-signal process instruction, but the 'only writing-plans / no implementation skills' message is restated in the HARD-GATE, Anti-Pattern, Process Flow, and After-the-Design sections, and Key Principles partly reiterates The Process; tightening these redundancies would reach score 3.	2 / 3
Actionability	Provides concrete, specific guidance for an instruction skill: a numbered checklist, exact output path 'docs/plans/YYYY-MM-DD-<topic>-design.md', and precise rules ('Only one question per message', 'up to 200-300 words'), matching the executable-guidance intent of the score-3 anchor.	3 / 3
Workflow Clarity	Steps are explicitly ordered ('complete them in order'), the Process Flow diagram includes an approval decision node with a 'no, revise' feedback loop back to presenting design, and approval checkpoints appear after each section, satisfying the score-3 anchor.	3 / 3
Progressive Disclosure	No bundle files exist, so the single-file body is appropriately organized into Overview, Checklist, Process Flow, The Process, After the Design, and Key Principles; per the rubric's simple-skill guidance, well-organized sections with no need for external references score 3.	3 / 3
	Total	11 / 12 Passed

Description

77%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states what the skill does and when to use it with explicit triggers, and uses correct third-person voice. Its main weakness is trigger breadth: the terms are framed as Claude's pre-work rather than naturally varied user phrasings, and broad triggers create overlap risk with other implementation skills.

Suggestions

Add a natural "Use when..." clause with user-voiced variations (e.g., 'Use when the user wants to add a feature, build a new component, or plan a change before coding') to improve trigger_term_quality.

Narrow the trigger scope to reduce conflict risk, e.g., frame it as the pre-implementation design/planning step rather than all 'creative work', so it is less likely to compete with frontend-design or writing-plans.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions ("creating features, building components, adding functionality, or modifying behavior") and a clear domain, matching the score-3 anchor's multi-action list rather than the single-domain score-2 anchor.	3 / 3
Completeness	Answers both what ("Explores user intent, requirements and design") and when ("You MUST use this before any creative work") with explicit trigger guidance equivalent to a "Use when" clause, so it is not capped at 2.	3 / 3
Trigger Term Quality	Phrases like "creating features" and "adding functionality" are somewhat natural but framed as Claude's own pre-work rather than varied user-uttered terms, missing common variations; closer to the score-2 anchor than the broad natural-term coverage of score 3.	2 / 3
Distinctiveness Conflict Risk	The design-before-implementation gate is a niche, but broad triggers like "creative work" and "modifying behavior" overlap with many implementation skills (frontend-design, writing-plans), fitting the score-2 "could still overlap" anchor.	2 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/brainstorming/SKILL.md
Commit: f627ab5

Reviewed: about 8 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.