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.
68
58%
Does it follow best practices?
Impact
74%
1.17xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/brainstorming/SKILL.mdDesign workflow compliance and spec documentation
No premature implementation
100%
100%
Context exploration first
0%
100%
Clarifying questions phase
62%
100%
Multiple approaches proposed
100%
100%
Trade-offs presented
100%
100%
Recommended approach identified
100%
100%
Design spec written
0%
0%
Spec self-review performed
0%
100%
User review gate
40%
0%
writing-plans as next step
0%
0%
Design covers required topics
100%
0%
Clarifying questions and approach proposals
One question per message
53%
100%
Multiple choice questions used
100%
20%
Exactly 2-3 approaches
0%
100%
Recommendation leads
0%
100%
Recommendation reasoning
0%
100%
Trade-offs for each approach
100%
100%
YAGNI applied
100%
100%
Design precedes spec writing
100%
100%
Questions focus on purpose and constraints
100%
100%
No implementation before design approval
100%
100%
Scope decomposition and design quality
Scope flag raised early
100%
100%
Decomposition performed
100%
100%
Ordered sub-projects
100%
100%
First sub-project designed
50%
0%
Design isolation principles
100%
100%
Existing code problems addressed
100%
100%
No unrelated refactoring
100%
100%
Spec written to correct path
0%
0%
writing-plans as next step
0%
0%
No implementation artifacts
100%
100%
b7a8f76
Table of Contents
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.