Brainstorming
Explore ideas and design solutions collaboratively before implementation. Use BEFORE building features, components, or making architectural changes. Triggers: 'brainstorm', 'design this feature', 'let's think through', 'explore approaches', 'before we build', 'what should we consider'. Do NOT use for implementation, code review, or bug fixes.
Install
$ agentstack add skill-cor-incorporated-claude-code-skills-brainstorming ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-cor-incorporated-claude-code-skills-brainstorming) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Brainstorming Ideas Into Designs
Turn ideas into validated designs through structured collaborative dialogue before writing any code.
Process
1. Understand Context
- Read project state: files, docs, recent commits.
- Ask one question at a time to refine the idea.
- Prefer multiple-choice questions over open-ended ones.
- Focus on: purpose, constraints, success criteria.
2. Explore Approaches
- Propose 2-3 approaches with trade-offs.
- Lead with your recommended option and explain why.
- Apply YAGNI ruthlessly -- remove unnecessary features.
3. Present Design Incrementally
- Break design into sections of 200-300 words.
- Ask after each section: "Does this look right so far?"
- Cover: architecture, components, data flow, error handling, testing.
- Go back and clarify when something does not make sense.
4. Document
- Write validated design to
docs/plans/YYYY-MM-DD--design.md. - Commit the design document.
5. Transition to Implementation (Optional)
- Ask: "Ready to set up for implementation?"
- Create isolated workspace with git worktree if proceeding.
- Draft a detailed implementation plan.
Error Handling
- If project context is unclear, ask for the repository path or relevant files before proceeding.
- If the user provides conflicting requirements, surface the conflict explicitly and ask for resolution.
- If a design section is rejected, revise that section before moving to the next.
Key Principles
- One question at a time -- do not overwhelm.
- Multiple choice preferred -- easier to answer.
- YAGNI ruthlessly -- cut unnecessary scope.
- Explore alternatives -- always compare 2-3 approaches.
- Incremental validation -- present in sections, confirm each.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Cor-Incorporated
- Source: Cor-Incorporated/claude-code-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.