skilless.ai-brainstorming

Engineering Community

Repo stars 190
Author repo skilless.ai

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Help turn ideas into fully formed plans through collaborative dialogue. Use before starting any project - product features, busi…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Process”, “1. Understand the Idea”, “2. Clarify Context”, “3. Explore Approaches”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name skilless.ai-brainstorming directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Process / 1. Understand the Idea / 2. Clarify Context” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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, or questions tool 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

<HARD-GATE> Do NOT start implementing until the user has approved the plan. Even "simple" ideas need clarity first. </HARD-GATE>

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, or questions tools 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-research to search the web, read pages, extract video transcripts, or conduct deep multi-source investigations
Ready to document the plan? → Invoke skilless.ai-writing to produce a professional, structured design doc or report from the approved plan

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Engineering
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @BrikerMan · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview skilless-ai-brainstorming.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# 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`, or `questions` tool 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

<HARD-GATE>
Do NOT start implementing until the user has approved the plan. Even "simple" ideas need clarity first.
</HARD-GATE>

## 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`, or `questions` tools 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

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Process → 1. Understand the Idea → 2. Clarify Context → 3. Explore Approaches → 4. Get Approval → 5. Document the Plan
terms    -> Help turn ideas into fully formed plans through natural collaborative dialogue. · Batch questions by dependency · Use question tools first · Multiple choice preferred · Start broad, then narrow · No assumptions · YAGNI ruthlessly · Explore alternatives
files/cmd -> askquestions · ask · questions · skilless.ai-research · skilless.ai-writing
body sha256 -> 3a2e062546b6