Skip to content
Back to skills

Brainstorming

ASecurity

Explore user intent, requirements, and design before implementation. Recommended before creative work such as new features or component design.

  • 4 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added June 4, 2026
code-qualitygotesting

Security analysis

A100/100

Scanned June 4, 2026

npx -y skills add lidge-jun/cli-jaw-skills --skill brainstorming --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Brainstorming?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Brainstorming
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lidge-jun-brainstorming/badge)](https://www.skillsdirectory.com/skills/lidge-jun-brainstorming)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: brainstorming
description: Explore user intent, requirements, and design before implementation. Recommended before creative work such as new features or component design.
---

# Brainstorming Ideas Into Designs

## Goal

Clarify requirements and produce a design before jumping to code. Reduces wasted work from unexamined assumptions.

## Design Review

Present a design and get user feedback before implementation. The design can be brief for simple tasks. For trivial changes (rename, typo fix), skip directly to implementation.

## Checklist

1. **Explore project context** — check files, docs, recent commits
2. **Ask clarifying questions** — one at a time; prefer multiple-choice over open-ended
3. **Propose 2-3 approaches** — with trade-offs; lead with your recommendation
4. **Present design** — scale detail to complexity; check after each section
5. **Save design doc** — `docs/plans/YYYY-MM-DD-<topic>-design.md`
6. **Transition** — invoke writing-plans skill to create implementation plan

## Guidelines

- Scale sections to complexity — a few sentences if straightforward, more if nuanced
- Cover: architecture, components, data flow, error handling, testing
- Apply YAGNI — remove unnecessary features from designs

## After Approval

1. Save the design to `docs/plans/YYYY-MM-DD-<topic>-design.md`
2. Commit the design document
3. Invoke writing-plans to create the implementation plan

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…