fluxly Search skills… ⌘K 中文 Publish

requirements-analysis

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
@RainLib · 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 requirements-analysis.preview 
---
name: requirements-analysis
description: 本阶段在主对话中执行，需与用户多轮对话，不得臆造需求。 以下每组为一轮提问。每轮向用户呈现结构化选项，用户选择后再进入下一轮。 向用户确认以下内容（可合并为一组选项）： 若用户没有原型图/设计…
category: other
runtime: no special runtime
---

# requirements-analysis output preview

## PART A: Task fit
- Use case: 本阶段在主对话中执行，需与用户多轮对话，不得臆造需求。 以下每组为一轮提问。每轮向用户呈现结构化选项，用户选择后再进入下一轮。 向用户确认以下内容（可合并为一组选项）： 若用户没有原型图/设计稿，向用户呈现以下选项： 根据用户前面的回答，对仍有模糊的业务流程、异常分支、非功能需求进行针对性追问。此轮可使用开放式问题。 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “何时使用 / 与用户交流（必须） / 交互原则” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “本阶段在主对话中执行，需与用户多轮对话，不得臆造需求。 以下每组为一轮提问。每轮向用户呈现结构化选项，用户选择后再进入下一轮。 向用户确认以下内容（可合并为一组选项）： 若用户没有原型图/设计稿，向用户呈现以下选项： 根据用户前面的回答，对仍有模糊的业务流程、异常分支、非功能需求进行针对性追问。此轮可使用开放式问题。 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “何时使用 / 与用户交流（必须） / 交互原则” 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: 本阶段在主对话中执行，需与用户多轮对话，不得臆造需求。 以下每组为一轮提问。每轮向用户呈现结构化选项，用户选择后再进入下一轮。 向用户确认以下内容（可合并为一组选项）： 若用户没有原型图/设计稿，向用户呈现以下选项： 根据用户前面的回答，对仍有模糊的业务流…
  • 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 “何时使用”, “与用户交流（必须）”, “交互原则”, “执行要点”, 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 requirements-analysis 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 “何时使用 / 与用户交流（必须） / 交互原则” 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.