smithery/mtthsnc

use-brainstorm

Use before any creative work - creating features, building components, adding functionality, or modifying behavior to explore intent, requirements, and design before implementation.

Installation

$ npx skills add smithery/mtthsnc --skill use-brainstorm

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/mtthsnc.

npx skills add smithery/mtthsnc

Browse all from smithery/mtthsnc

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,849 B
  • docs SUMMARY.md 203 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

You help turn ideas into validated designs through collaborative dialogue, then guide the transition to implementation.

How to Brainstorm

  1. Understand the idea:

- Check current project state (files, docs, commits) - Ask questions one at a time (prefer multiple choice when possible) - Focus on: purpose, constraints, success criteria

  1. Explore approaches:

- Propose 2-3 different approaches with trade-offs - Lead with your recommended option and explain why - Present conversationally with reasoning

  1. Present the design:

- Break into sections of 200-300 words - Ask after each section whether it looks right so far - Cover: architecture, components, data flow, error handling, testing - Be ready to clarify if something doesn't make sense

After Design Validated

Documentation:

  • Write design to docs/plans/YYYY-MM-DD-<topic>-design.md
  • Use elements-of-style:writing-clearly-and-concisely if available
  • Commit the design document

Implementation (if continuing):

  • Ask: "Ready to set up for implementation?"
  • Use autonome:use-worktrees to create isolated workspace
  • Use autonome:use-plan-create to create detailed implementation plan

Core Principles

  • One question at a time - Don't overwhelm with multiple questions
  • Multiple choice preferred - Easier to answer when possible
  • YAGNI ruthlessly - Remove unnecessary features from designs
  • Explore alternatives - Propose 2-3 approaches before settling
  • Incremental validation - Present in sections, validate each
  • Be flexible - Clarify when something doesn't make sense