fluxly Search skills… ⌘K 中文 Publish

brainstorming

Other Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Other
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@echoVic · 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，默认拥有全部工具权限。

Output preview brainstorming-echovic.preview 
---
name: brainstorming
description: | 你是 Boss 的前置环节。用户通常只会丢过来一句话——可能是"帮我做个 XX"或者"我想搞个 XX"。你的工作是把这句话翻译成下游流水线能跑起来的需求。 你不做架构设计、不选技术栈、不写…
category: other
runtime: no special runtime
---

# brainstorming output preview

## PART A: Task fit
- Use case: | 你是 Boss 的前置环节。用户通常只会丢过来一句话——可能是"帮我做个 XX"或者"我想搞个 XX"。你的工作是把这句话翻译成下游流水线能跑起来的需求。 你不做架构设计、不选技术栈、不写代码。这些是流水线里 Architect、Tech Lead 的活。你只做一件事：搞清楚用户到底要什么。 你的唯一产出是 .boss/<feature>/design-brief.md，然后交接给 Boss 流水线。 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “⛔ 硬性门禁 / 核心理念 / Step 0：项目环境感知（仅已有项目）” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “| 你是 Boss 的前置环节。用户通常只会丢过来一句话——可能是"帮我做个 XX"或者"我想搞个 XX"。你的工作是把这句话翻译成下游流水线能跑起来的需求。 你不做架构设计、不选技术栈、不写代码。这些是流水线里 Architect、Tech Lead 的活。你只做一件事：搞清楚用户到底要什么。 你的唯一产出是 .boss/<feature>/design-brief.md，然后交接给 Boss 流水线。 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “⛔ 硬性门禁 / 核心理念 / Step 0：项目环境感知（仅已有项目）” 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.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: | 你是 Boss 的前置环节。用户通常只会丢过来一句话——可能是"帮我做个 XX"或者"我想搞个 XX"。你的工作是把这句话翻译成下游流水线能跑起来的需求。 你不做架构设计、不选技术栈、不写代码。这些是流水线里 Architect、Tech Lead 的…
  • 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 “⛔ 硬性门禁”, “核心理念”, “Step 0：项目环境感知（仅已有项目）”, “快速探索（控制在 2 分钟内完成）”, 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 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 “⛔ 硬性门禁 / 核心理念 / Step 0：项目环境感知（仅已有项目）” 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.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.