CtrlK
BlogDocsLog inGet started
Tessl Logo

brainstorming

This skill should be used before implementing features, building components, or making changes. It guides exploring user intent, approaches, and design decisions before planning. Triggers on "let's brainstorm", "help me think through", "what should we build", "explore approaches", ambiguous feature requests, or when the user's request has multiple valid interpretations that need clarification.

83

1.34x
Quality

79%

Does it follow best practices?

Impact

85%

1.34x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/compound-engineering/skills/brainstorming/SKILL.md
SKILL.md
Quality
Evals
Security

Evaluation results

91%

57%

Product Search for Growing E-Commerce Platform

Design doc generation and approach proposals

Criteria
Without context
With context

Correct file location

0%

100%

Filename format

0%

100%

Frontmatter date

0%

100%

Frontmatter topic kebab-case

0%

100%

Required sections present

20%

70%

Next Steps /ce:plan

0%

100%

2-3 approaches proposed

0%

100%

Approach Pros and Cons

100%

100%

Best when statement

100%

100%

Recommendation with reasoning

100%

100%

YAGNI simplicity

80%

100%

Handoff options

0%

40%

65%

8%

Explore a Notification Feature Request

Question technique and brainstorm exploration process

Criteria
Without context
With context

One question at a time

100%

66%

Multiple-choice format

0%

100%

Broad-to-narrow ordering

90%

80%

Explicit assumption validation

41%

58%

Success criteria question

100%

100%

No implementation details in Phase 1

33%

25%

Section word count

100%

87%

Validation checkpoint

0%

0%

No assumption made silently

71%

71%

100%

1%

Triage Two Developer Requests

Requirement clarity assessment and YAGNI discipline

Criteria
Without context
With context

Clear-req case identified

100%

100%

Proceed-to-planning suggestion

100%

100%

No full brainstorm for clear req

90%

100%

Ambiguous-req case identified

100%

100%

Brainstorm initiated for vague req

100%

100%

Clarity signals referenced

100%

100%

YAGNI pushback

100%

100%

Simpler approach favored

100%

100%

No hypothetical future design

100%

100%

Repository
EveryInc/compound-engineering-plugin
Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

Table of Contents

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.