brainstorming

Devflow wrapper for the upstream brainstorming skill. Use when starting any creative work — creating features, building components, adding functionality, or modifying behavior — to explore user intent, requirements, and design before implementation. Always invoke `/devflow:brainstorming` rather than the upstream skill directly so devflow can layer in project-specific behavior (recall hooks, phase-handoff entry points) without callers ever needing to know about the upstream.

Quality

87%

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

Quality

Content

85%Weight 40%Scale 1-5

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

A crisp, highly actionable wrapper skill: the delegation, override condition, terminal handoff message, and fallback are all concrete and unambiguous. The only cost is token redundancy — the writing-plans prohibition is repeated three times and the rationale section adds execution-irrelevant context.

Suggestions

State the 'do NOT invoke writing-plans' override once in step 3 and let the quoted terminal message carry it; remove the duplicate prose repetition.

Trim or compress the 'Why this wrapper exists' section — the pipeline-facing rationale is not needed to execute the wrapper and competes with conversation context.

The session-boundary detail (spec-feature in the SAME session, phase-handoff only at later boundaries) is stated both in the quoted message and the following paragraph; consolidate into one place.

Dimension	Reasoning	Score
Conciseness	The prohibition on invoking writing-plans is stated three times (step 3's intro, the quoted terminal message, and again in the surrounding prose), and the 'Why this wrapper exists' section is execution-irrelevant rationale. Not 2: there is no explanation of concepts Claude already knows and no generic padding; not 4: the repetition and rationale section are real trimmable bulk.	3 / 5
Actionability	Fully executable for an instruction-only skill: exact Skill-tool invocation ('Invoke superpowers:brainstorming via the Skill tool'), verbatim $ARGUMENTS pass-through, a copy-paste-ready terminal handoff message, and a concrete fallback (search 'brainstorm', with the exact error text to surface).	5 / 5
Workflow Clarity	Three clearly sequenced steps with an explicit terminal-state condition (design approved + spec written + spec approved), a well-defined fallback branch, and a guard against prematurely auto-invoking spec-feature. As a simple, non-destructive skill with an unambiguous flow it meets the top anchor via the simple-skill exception.	5 / 5
Progressive Disclosure	At ~37 lines with no bundle files and no need for external references, the body is well-organized into clear sections (Steps, Fallback, Important), which per the rubric's under-50-line guideline earns the top score.	5 / 5
	Total	18 / 20 Passed

Description

83%Weight 40%Scale 1-5

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

A strong description that clearly states what the wrapper does, when to use it with concrete trigger phrases, and how it differs from the upstream skill, all in third person. The only weakness is trigger breadth ('any creative work') that could overlap with other design/brainstorming skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete, third-person actions ('explore user intent, requirements, and design before implementation', 'invoke /devflow:brainstorming', 'layer in project-specific behavior (recall hooks, phase-handoff entry points)') with minor coverage gaps. Not 5: the action inventory is thinner than anchor-5's comprehensive list; not 3: it goes well beyond 1-2 generic actions.	4 / 5
Completeness	Explicitly answers both: what ('Devflow wrapper for the upstream brainstorming skill... explore user intent, requirements, and design before implementation') and when ('Use when starting any creative work — creating features, building components, adding functionality, or modifying behavior') with concrete trigger phrases, matching the anchor-5 example pattern.	5 / 5
Trigger Term Quality	Natural phrases users would say are present ('creating features, building components, adding functionality, or modifying behavior'), plus 'brainstorming'. Not 5: common synonyms like 'designing', 'planning', or 'new feature' are missing; not 3: coverage is good, not partial.	4 / 5
Distinctiveness Conflict Risk	Mostly distinct: it names a specific canonical entry point and explicitly disambiguates from the upstream skill ('Always invoke /devflow:brainstorming rather than the upstream skill directly'). Not 5: the 'any creative work' trigger breadth overlaps with generic brainstorming/design skills; not 3: the conflict with the closest neighbor (the upstream skill) is explicitly addressed.	4 / 5
	Total	17 / 20 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: AndreJorgeLopes/devflow
Path: skills/brainstorming/SKILL.md
Commit: bd4b70c

Reviewed: 7 days 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.