agentleFS
Sign inStart free
involvexinvolvex/youtube-music-cli/.agents/skills/brainstorming/SKILL.md

brainstorming

Skill461 starsChanged 3 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

15 rules. 1 is common, 13 are distinctive, and 1 is very specific to this project.

  • 1

    Common

    Most of the 173 edited versions we read keep these.

  • 13

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start by understanding the current project context, then ask questions one at a time to refine the idea.

    line 12
  2. Common:

    Check out the current project state first (files, docs, recent commits)

    line 18
  3. Distinctive:

    Ask questions one at a time to refine the idea

    line 19
  4. Distinctive:

    Prefer multiple choice questions when possible, but open-ended is fine too

    line 20
  5. Distinctive:

    Only one question per message - if a topic needs more exploration, break it into multiple questions

    line 21
  6. Distinctive:

    Ask after each section whether it looks right so far

    line 34
  7. Very specific:

    Write the validated design to docs/plans/YYYY-MM-DD-<topic>-design.md

    line 42
  8. Distinctive:

    Use elements-of-style:writing-clearly-and-concisely skill if available

    line 43
  9. Distinctive:

    Commit the design document to git

    line 44
  10. Distinctive:

    Ask: "Ready to set up for implementation?"

    line 48
  11. Distinctive:

    Use superpowers:using-git-worktrees to create isolated workspace

    line 49
  12. Distinctive:

    Use superpowers:writing-plans to create detailed implementation plan

    line 50
  13. Distinctive:

    One question at a time: - Don't overwhelm with multiple questions

    line 54
  14. Distinctive:

    YAGNI ruthlessly: - Remove unnecessary features from all designs

    line 56
  15. Distinctive:

    Explore alternatives: - Always propose 2-3 approaches before settling

    line 57

“Common” is measured: kept by at least 6 in 10 of the 173 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Brainstorming Ideas Into Designs

Overview

Help turn ideas into fully formed designs and specs through natural collaborative dialogue.

Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.

The Process

Understanding the idea:

  • Check out the current project state first (files, docs, recent commits)
  • Ask questions one at a time to refine the idea
  • Prefer multiple choice questions when possible, but open-ended is fine too
  • Only one question per message - if a topic needs more exploration, break it into multiple questions
  • Focus on understanding: purpose, constraints, success criteria

Exploring approaches:

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

Presenting the design:

  • Once you believe you understand what you're building, present the design
  • Break it 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 go back and clarify if something doesn't make sense

After the Design

Documentation:

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

Implementation (if continuing):

  • Ask: "Ready to set up for implementation?"
  • Use superpowers:using-git-worktrees to create isolated workspace
  • Use superpowers:writing-plans to create detailed implementation plan

Key Principles

  • One question at a time - Don't overwhelm with multiple questions
  • Multiple choice preferred - Easier to answer than open-ended when possible
  • YAGNI ruthlessly - Remove unnecessary features from all designs
  • Explore alternatives - Always propose 2-3 approaches before settling
  • Incremental validation - Present design in sections, validate each
  • Be flexible - Go back and clarify when something doesn't make sense

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free