f2s-req-clarify
Ensures PRD and project requirements are clear and well-defined before starting technical implementation.
Install
mkdir -p .claude/skills/f2s-req-clarify && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12764" && unzip -o skill.zip -d .claude/skills/f2s-req-clarify && rm skill.zipInstalls to .claude/skills/f2s-req-clarify
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
针对 PRD/需求反问直到清楚，再可用 f2s-req-tech 出技术方案；触发：需求澄清、PRD 澄清Key capabilities
- →Identify ambiguous statements in PRD/requirements
- →Find undefined concepts and missing information
- →Detect contradictions and unstated implementation details
- →Ask targeted questions to clarify requirements
- →Produce a formal clarification document
How it works
This skill identifies ambiguities and missing information in requirements, asks clarifying questions, and iteratively refines understanding until a clear clarification document can be produced.
Inputs & outputs
When to use f2s-req-clarify
- →Refining vague product requirements
- →Identifying missing edge cases in PRDs
- →Standardizing feature definitions for development
- →Documenting project boundaries
About this skill
编排（主 / 子 agent）
subAgent/switchAgentVerification两字段语义以统一入口为唯一事实源：Cursor/Claude 读配置根rules/f2s-flow2spec-unified-entry.*；Codex 读.codex/topics/f2s-flow2spec-unified-entry.md（与上同源，flow2spec init镜像）。本技能不复述。- 本技能默认不拆子：无论
subAgent真值，澄清流程全程在主会话进行（追问与用户对齐强依赖连续同会话，拆子必断上下文）。 - 校验口径为落盘侧自验，本技能不绑定交叉校验。
需求澄清
执行口径：澄清文档统一落盘到
.Knowledge/req-docs/。
入参：可选。PRD 全文、需求描述或文档路径（如 .Knowledge/req-docs/xxx.md）；不传则按当前对话内容澄清。后续回复可补需求条件。
行为：找出需求中的模糊表述、未定义概念、缺失信息、矛盾、与实现相关但未说明的点 → 分组、具体可答地反问 → 根据回答迭代追问，直到流程、边界、异常、关键概念无歧义。不替用户做业务假设，不清楚就问。
结束（澄清文档落盘 → 自动衔接技术方案）：当信息已足够清晰时，必须输出一份可直接落盘的「需求澄清文档」（Markdown）。文档至少包含：背景与目标、范围（包含/不包含）、关键流程、边界与异常、关键概念定义、验收标准、未决问题（如有）。建议保存到 .Knowledge/req-docs/（推荐命名 <能力名>_需求澄清.md）。
澄清文档落盘后本技能同轮自动衔接 f2s-req-tech：以刚落盘的澄清文档路径为输入直接进入技术方案生成，无需等用户再次触发；进入前给用户一行提示「澄清文档已就绪：<路径>；正在按 f2s-req-tech 生成技术方案」，然后继续。
例外——停在澄清、不自动衔接技术方案（任一命中即停）：
- 澄清文档「未决问题」小节仍有影响方案结构的关键项未回答（如库/表/接口/状态机主契约缺定义），此时输出一段说明列出待答项，等用户回答后再落盘并衔接；
- 用户在澄清过程中明确说「先只出澄清 / 别急着做方案 / 先讨论」等停步语；
- 用户显式指定了不同的后续动作（如「澄清完就停」「先给我拆任务」）。
禁止：
- 在澄清文档尾部或紧随其后追加
f2s-kb-distill收口提示（见rules/f2s-kb-feedback-closing.*禁止段——过程编排型技能落盘不触发 distill）； - 未落盘澄清文档就自动衔接
f2s-req-tech（自动衔接的前提是磁盘上已有澄清文档路径）； - 越级自动衔接
f2s-req-plan/implement-tech-design/ 其他f2s-*技能（同轮只允许接到f2s-req-tech一步，后续仍须用户新一轮触发）。
When not to use it
- →When the task is to generate a technical solution
- →When the task does not involve clarifying requirements or PRDs
Limitations
- →It does not generate technical solutions
- →It requires user interaction for iterative questioning
- →It focuses on clarifying existing documents
How it compares
This skill provides a structured process for requirement clarification, focusing on iterative questioning and formal documentation, rather than directly proceeding to technical solutions.
Compared to similar skills
f2s-req-clarify side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| f2s-req-clarify (this skill) | 0 | 2mo | No flags | Intermediate |
| spec-kit-workflow | 11 | 8mo | No flags | Intermediate |
| product-manager-toolkit | 32 | 7mo | Review | Beginner |
| to-prd | 0 | 2mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
to-prd
manuelseeger
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
product-spec-builder
zinohome
你是一个**毒舌产品经理**，负责需求收集、产品文档编写和迭代更新。你的核心特点是：
self-host-development-light
doolin
Lightweight self-hosted project management using markdown files in a .development directory. Covers backlog, planning, todo, roadmap, and saved plans — everything an agent needs to orient and start working.
bmad-agent-pm
alibaba
Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.