Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vaycentsun/sw-requirements-clarification
Use when starting software development of new feature in the project, before writing implementation code
Passed 10 of 20 test cases with the skill, and 8 of 20 without it.
and 11 more in the full report
9 fixed3 passed either way5 still failing6 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to introduce a notification center into our web platform supporting push notifications, email digests, and user preference controls. Since the scope isn't fully defined yet, please help me refine this requirement. Ask me clarifying questions one by one, present a few design options with trade-offs, write out a business specification file in the agile docs folder, and present a final decision summary before moving to technical planning.
| Checked | Without skill | With skill |
|---|---|---|
| Asks strictly one clarifying question at a time. | Passed | Passed |
| Explores project context before posing questions. | Missed | Passed |
The instructions your model reads when the skill loads.
通过与用户的苏格拉底式对话，将模糊的想法转化为清晰的需求和明确的设计决策。
以下情况属于简单任务，不经过需求澄清，直接调用 sw-test-driven-dev：
不确定是否属于简单任务？ 走需求澄清流程。宁可流程过度，不可跳过设计。
以下情况必须走需求澄清，不可走快速通道：
| 场景 | 说明 |
|---|---|
| Bug 修复涉及新增组件 | 需要新增文件、模块或服务 |
| Bug 修复涉及接口变更 | 修改函数签名、API 契约或数据结构 |
| Bug 影响多个模块 | 修复一处导致其他模块需要适配 |
| 快速扫描后发现改动范围超预期 | 原本以为只改单函数，实际涉及多处修改 |
回退规则：快速扫描后发现改动超出预期 → 立即回退到需求澄清流程。
铁律：在完整呈现设计方案之前，严禁执行以下任何操作：
设计必须完整呈现（需求澄清 + 方案决策 + business-spec），但无需在每个节点等待用户明确批准。Agent 自动推进流程，用户可随时打断并提出异议。
反模式警告："这个需求太简单了，不需要设计"
test cases passed, vs 8 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.