skilless.ai-brainstorming
- Repo stars 190
- Author updated Live
- Author repo skilless.ai
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @BrikerMan · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: skilless.ai-brainstorming
description: Help turn ideas into fully formed plans through collaborative dialogue. Use before starting any…
category: engineering
runtime: no special runtime
---
# skilless.ai-brainstorming output preview
## PART A: Task fit
- Use case: Help turn ideas into fully formed plans through collaborative dialogue. Use before starting any project - product features, business ideas, creative projects, or process improvements..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Process / 1. Understand the Idea / 2. Clarify Context” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Help turn ideas into fully formed plans through collaborative dialogue. Use before starting any project - product features, business ideas, creative projects, or process improvements.”.
- **02** When the source has headings, the agent prioritizes “Process / 1. Understand the Idea / 2. Clarify Context” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Process / 1. Understand the Idea / 2. Clarify Context”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skilless.ai-brainstorming
description: Help turn ideas into fully formed plans through collaborative dialogue. Use before starting any…
category: engineering
source: BrikerMan/skilless.ai
---
# skilless.ai-brainstorming
## When to use
- Help turn ideas into fully formed plans through collaborative dialogue. Use before starting any project - product feat…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Process / 1. Understand the Idea / 2. Clarify Context” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skilless.ai-brainstorming" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Process / 1. Understand the Idea / 2. Clarify Context
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Brainstorming: From Idea to Plan
Help turn ideas into fully formed plans through natural collaborative dialogue.
Works for: product features, business ideas, creative projects, process improvements, technical designs, or any new initiative.
Process
Explore context → Ask questions → Propose approaches → Get approval → Document plan
1. Understand the Idea
- Check any existing context first (files, docs, prior notes, recent work)
- Gather all clarifying questions upfront — use
ask_questions,ask, orquestionstool if available; plain text otherwise - Focus on: purpose, who it's for, constraints, success criteria, timeline
2. Clarify Context
- Timeline, budget, resources, technical constraints
- Who is the audience? What does success look like?
3. Explore Approaches
- Propose 2-3 different approaches with trade-offs
- Lead with your recommended option and explain why
4. Get Approval
- Present plan section by section, get approval before moving on
- Scale depth to complexity of the idea
- Cover dimensions relevant to the domain: structure, key decisions, risks, next steps
5. Document the Plan
- Create a clear, actionable plan based on the agreed direction
Principles
- Batch questions by dependency — Ask independent questions together in one round; hold dependent ones for the next round after getting answers
- Use question tools first — If
ask_questions,ask, orquestionstools are available, use them; otherwise ask in plain text - Multiple choice preferred — Easier to answer than open-ended when possible
- Start broad, then narrow — Understand the big picture first
- No assumptions — "Simple" ideas often have hidden complexity
- YAGNI ruthlessly — Remove unnecessary scope from all plans
- Explore alternatives — Always propose 2-3 approaches before settling
- Incremental validation — Present plan section by section, get approval before moving on
- Be flexible — Go back and clarify when something doesn't make sense
Cross-References
- Need research? → Invoke
skilless.ai-researchto search the web, read pages, extract video transcripts, or conduct deep multi-source investigations - Ready to document the plan? → Invoke
skilless.ai-writingto produce a professional, structured design doc or report from the approved plan
Decide Fit First
Design Intent
How To Use It
Boundaries And Review