requirements-clarity

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Requirements Clarity Skill

需求澄清Skill

Description

描述

Automatically transforms vague requirements into actionable PRDs through systematic clarification with a 100-point scoring system.

通过带有100分评分体系的系统性澄清，自动将模糊需求转化为可落地的PRD。

Instructions

说明

When invoked, detect vague requirements:

Vague Feature Requests
- User says: "add login feature", "implement payment", "create dashboard"
- Missing: How, with what technology, what constraints?
Missing Technical Context
- No technology stack mentioned
- No integration points identified
- No performance/security constraints
Incomplete Specifications
- No acceptance criteria
- No success metrics
- No edge cases considered
- No error handling mentioned
Ambiguous Scope
- Unclear boundaries ("user management" - what exactly?)
- No distinction between MVP and future enhancements
- Missing "what's NOT included"

Do NOT activate when:

Specific file paths mentioned (e.g., "auth.go:45")
Code snippets included
Existing functions/classes referenced
Bug fixes with clear reproduction steps

触发本Skill时，需识别模糊需求：

模糊的功能请求
- 用户表述："添加登录功能"、"实现支付功能"、"创建仪表盘"
- 缺失信息：实现方式、使用的技术、约束条件？
缺失技术上下文
- 未提及技术栈
- 未识别集成点
- 未说明性能/安全约束
不完整的规格说明
- 无验收标准
- 无成功指标
- 未考虑边缘情况
- 未提及错误处理
模糊的范围
- 边界不清晰（如"用户管理"——具体包含哪些内容？）
- 未区分MVP与未来增强功能
- 缺失"不包含的内容"

请勿激活本Skill的场景：

提及了具体文件路径（如"auth.go:45"）
包含代码片段
引用了现有函数/类
有清晰复现步骤的Bug修复

Core Principles

核心原则

Systematic Questioning
- Ask focused, specific questions
- One category at a time (2-3 questions per round)
- Build on previous answers
- Avoid overwhelming users
Quality-Driven Iteration
- Continuously assess clarity score (0-100)
- Identify gaps systematically
- Iterate until ≥ 90 points
- Document all clarification rounds
Actionable Output
- Generate concrete specifications
- Include measurable acceptance criteria
- Provide executable phases
- Enable direct implementation

系统性提问
- 提出针对性、具体的问题
- 每次针对一个类别（每轮2-3个问题）
- 基于之前的回答逐步深入
- 避免使用户感到负担过重
质量驱动的迭代
- 持续评估澄清得分（0-100分）
- 系统性识别缺口
- 迭代至得分≥90分
- 记录所有澄清轮次
可落地的输出
- 生成具体的规格说明
- 包含可衡量的验收标准
- 提供可执行的阶段计划
- 支持直接开展开发工作

Clarification Process

澄清流程

Step 1: Initial Requirement Analysis

步骤1：初始需求分析

Input: User's requirement description

Tasks:

Parse and understand core requirement
Generate feature name (kebab-case format)
Determine document version (default
```
1.0
```
unless user specifies otherwise)
Ensure
```
./docs/prds/
```
exists for PRD output
Perform initial clarity assessment (0-100)

Assessment Rubric:

Functional Clarity: /30 points
- Clear inputs/outputs: 10 pts
- User interaction defined: 10 pts
- Success criteria stated: 10 pts

Technical Specificity: /25 points
- Technology stack mentioned: 8 pts
- Integration points identified: 8 pts
- Constraints specified: 9 pts

Implementation Completeness: /25 points
- Edge cases considered: 8 pts
- Error handling mentioned: 9 pts
- Data validation specified: 8 pts

Business Context: /20 points
- Problem statement clear: 7 pts
- Target users identified: 7 pts
- Success metrics defined: 6 pts

Initial Response Format:

markdown

I understand your requirement. Let me help you refine this specification.

**Current Clarity Score**: X/100

**Clear Aspects**:
- [List what's clear]

**Needs Clarification**:
- [List gaps]

Let me systematically clarify these points...

输入：用户的需求描述

任务：

解析并理解核心需求
生成功能名称（kebab-case格式）
确定文档版本（默认
```
1.0
```
，除非用户指定其他版本）
确保
```
./docs/prds/
```
目录存在，用于输出PRD
执行初始澄清评估（0-100分）

评估标准：

功能清晰度：/30分
- 输入/输出明确：10分
- 用户交互已定义：10分
- 成功标准已说明：10分

技术特异性：/25分
- 提及技术栈：8分
- 识别集成点：8分
- 指定约束条件：9分

开发完整性：/25分
- 考虑边缘情况：8分
- 提及错误处理：9分
- 指定数据验证规则：8分

业务上下文：/20分
- 问题陈述清晰：7分
- 已识别目标用户：7分
- 定义成功指标：6分

初始回复格式：

markdown

我已了解你的需求，让我帮你完善这个规格说明。

**当前澄清得分**：X/100

**已明确的内容**：
- [列出已明确的部分]

**需要澄清的内容**：
- [列出缺口]

让我系统性地澄清这些要点...

Step 2: Gap Analysis

步骤2：缺口分析

Identify missing information across four dimensions:

1. Functional Scope

What is the core functionality?
What are the boundaries?
What is out of scope?
What are edge cases?

2. User Interaction

How do users interact?
What are the inputs?
What are the outputs?
What are success/failure scenarios?

3. Technical Constraints

Performance requirements?
Compatibility requirements?
Security considerations?
Scalability needs?

4. Business Value

What problem does this solve?
Who are the target users?
What are success metrics?
What is the priority?

从四个维度识别缺失的信息：

1. 功能范围

核心功能是什么？
边界是什么？
不包含哪些内容？
边缘情况有哪些？

2. 用户交互

用户如何与功能交互？
输入是什么？
输出是什么？
成功/失败场景有哪些？

3. 技术约束

性能要求是什么？
兼容性要求是什么？
安全考虑有哪些？
可扩展性需求是什么？

4. 业务价值

该功能解决什么问题？
目标用户是谁？
成功指标是什么？
优先级如何？

Step 3: Interactive Clarification

步骤3：交互式澄清

Question Strategy:

Start with highest-impact gaps
Ask 2-3 questions per round
Build context progressively
Use user's language
Provide examples when helpful

Question Format:

markdown

I need to clarify the following points to complete the requirements document:

1. **[Category]**: [Specific question]?
   - For example: [Example if helpful]

2. **[Category]**: [Specific question]?

3. **[Category]**: [Specific question]?

Please provide your answers, and I'll continue refining the PRD.

After Each User Response:

Update clarity score
Capture new information in the working PRD outline
Identify remaining gaps
If score < 90: Continue with next round of questions
If score ≥ 90: Proceed to PRD generation

Score Update Format:

markdown

Thank you for the additional information!

**Clarity Score Update**: X/100 → Y/100

**New Clarified Content**:
- [Summarize new information]

**Remaining Points to Clarify**:
- [List remaining gaps if score < 90]

[If score < 90: Continue with next round of questions]
[If score ≥ 90: "Perfect! I will now generate the complete PRD document..."]

提问策略：

从影响最大的缺口开始提问
每轮提出2-3个问题
逐步构建上下文
使用用户熟悉的语言
必要时提供示例

提问格式：

markdown

我需要澄清以下要点以完成需求文档：

1. **[类别]**：[具体问题]？
   - 例如：[如有帮助，提供示例]

2. **[类别]**：[具体问题]？

3. **[类别]**：[具体问题]？

请提供你的答案，我会继续完善PRD。

每次用户回复后：

更新澄清得分
将新信息记录到PRD工作大纲中
识别剩余缺口
如果得分<90分：继续下一轮提问
如果得分≥90分：进入PRD生成阶段

得分更新格式：

markdown

感谢你提供的补充信息！

**澄清得分更新**：X/100 → Y/100

**新澄清的内容**：
- [总结新信息]

**仍需澄清的要点**：
- [如果得分<90分，列出剩余缺口]

[如果得分<90分：继续下一轮提问]
[如果得分≥90分："完美！我现在将生成完整的PRD文档..."]

Step 4: PRD Generation

步骤4：PRD生成

Once clarity score ≥ 90, generate comprehensive PRD.

Output File:

Final PRD:

./docs/prds/{feature_name}-v{version}-prd.md

Use the

Write

tool to create or update this file. Derive

{version}

from the document version recorded in the PRD (default

1.0

当澄清得分≥90分时，生成完整的PRD。

输出文件：

最终PRD：

./docs/prds/{feature_name}-v{version}-prd.md

使用

Write

工具创建或更新该文件。

{version}

取自PRD中记录的文档版本（默认

1.0

）。

PRD Document Structure

PRD文档结构

markdown

undefined

markdown

undefined

{Feature Name} - Product Requirements Document (PRD)

{功能名称} - 产品需求文档（PRD）

Requirements Description

需求描述

Background

背景

Business Problem: [Describe the business problem to solve]
Target Users: [Target user groups]
Value Proposition: [Value this feature brings]

业务问题：[描述要解决的业务问题]
目标用户：[目标用户群体]
价值主张：[该功能带来的价值]

Feature Overview

功能概述

Core Features: [List of main features]
Feature Boundaries: [What is and isn't included]
User Scenarios: [Typical usage scenarios]

核心功能：[主要功能列表]
功能边界：[包含与不包含的内容]
用户场景：[典型使用场景]

Detailed Requirements

详细需求

Input/Output: [Specific input/output specifications]
User Interaction: [User operation flow]
Data Requirements: [Data structures and validation rules]
Edge Cases: [Edge case handling]

输入/输出：[具体的输入/输出规格]
用户交互：[用户操作流程]
数据需求：[数据结构与验证规则]
边缘情况：[边缘情况处理方式]

Design Decisions

设计决策

Technical Approach

技术方案

Architecture Choice: [Technical architecture decisions and rationale]
Key Components: [List of main technical components]
Data Storage: [Data models and storage solutions]
Interface Design: [API/interface specifications]

架构选择：[技术架构决策及理由]
核心组件：[主要技术组件列表]
数据存储：[数据模型与存储方案]
接口设计：[API/接口规格]

Constraints

约束条件

Performance Requirements: [Response time, throughput, etc.]
Compatibility: [System compatibility requirements]
Security: [Security considerations]
Scalability: [Future expansion considerations]

性能要求：[响应时间、吞吐量等]
兼容性：[系统兼容性要求]
安全性：[安全考虑事项]
可扩展性：[未来扩展考虑]

Risk Assessment

风险评估

Technical Risks: [Potential technical risks and mitigation plans]
Dependency Risks: [External dependencies and alternatives]
Schedule Risks: [Timeline risks and response strategies]

技术风险：[潜在技术风险及缓解方案]
依赖风险：[外部依赖及替代方案]
进度风险：[ timeline风险及应对策略]

Acceptance Criteria

验收标准

Functional Acceptance

功能验收

Feature 1: [Specific acceptance conditions]
Feature 2: [Specific acceptance conditions]
Feature 3: [Specific acceptance conditions]

功能1：[具体验收条件]
功能2：[具体验收条件]
功能3：[具体验收条件]

Quality Standards

质量标准

Code Quality: [Code standards and review requirements]
Test Coverage: [Testing requirements and coverage]
Performance Metrics: [Performance test pass criteria]
Security Review: [Security review requirements]

代码质量：[代码标准与评审要求]
测试覆盖率：[测试要求与覆盖率]
性能指标：[性能测试通过标准]
安全评审：[安全评审要求]

User Acceptance

用户验收

User Experience: [UX acceptance criteria]
Documentation: [Documentation delivery requirements]
Training Materials: [If needed, training material requirements]

用户体验：[UX验收标准]
文档：[文档交付要求]
培训材料：[如有需要，培训材料要求]

Execution Phases

执行阶段

Phase 1: Preparation

阶段1：准备工作

Goal: Environment preparation and technical validation

Task 1: [Specific task description]
Task 2: [Specific task description]
Deliverables: [Phase deliverables]
Time: [Estimated time]

目标：环境准备与技术验证

任务1：[具体任务描述]
任务2：[具体任务描述]
交付物：[阶段交付物]
时间：[预估时长]

Phase 2: Core Development

阶段2：核心开发

Goal: Implement core functionality

Task 1: [Specific task description]
Task 2: [Specific task description]
Deliverables: [Phase deliverables]
Time: [Estimated time]

目标：实现核心功能

任务1：[具体任务描述]
任务2：[具体任务描述]
交付物：[阶段交付物]
时间：[预估时长]

Phase 3: Integration & Testing

阶段3：集成与测试

Goal: Integration and quality assurance

Task 1: [Specific task description]
Task 2: [Specific task description]
Deliverables: [Phase deliverables]
Time: [Estimated time]

目标：集成与质量保障

任务1：[具体任务描述]
任务2：[具体任务描述]
交付物：[阶段交付物]
时间：[预估时长]

Phase 4: Deployment

阶段4：部署上线

Goal: Release and monitoring

Task 1: [Specific task description]
Task 2: [Specific task description]
Deliverables: [Phase deliverables]
Time: [Estimated time]

Document Version: 1.0 Created: {timestamp} Clarification Rounds: {clarification_rounds} Quality Score: {quality_score}/100

undefined

目标：发布与监控

任务1：[具体任务描述]
任务2：[具体任务描述]
交付物：[阶段交付物]
时间：[预估时长]

文档版本：1.0 创建时间：{timestamp} 澄清轮次：{clarification_rounds} 质量得分：{quality_score}/100

undefined

Behavioral Guidelines

行为准则

DO

应做事项

Ask specific, targeted questions
Build on previous answers
Provide examples to guide users
Maintain conversational tone
Summarize clarification rounds within the PRD
Use clear, professional English
Generate concrete specifications
Stay in clarification mode until score ≥ 90

提出具体、针对性的问题
基于之前的回答逐步深入
提供示例引导用户
保持对话式语气
在PRD中总结澄清轮次
使用清晰、专业的表述
生成具体的规格说明
在得分≥90分前保持澄清模式

DON'T

不应做事项

Ask all questions at once
Make assumptions without confirmation
Generate PRD before 90+ score
Skip any required sections
Use vague or abstract language
Proceed without user responses
Exit skill mode prematurely

一次性提出所有问题
在未确认的情况下做出假设
得分未达90分就生成PRD
跳过任何必填章节
使用模糊或抽象的语言
未得到用户回复就继续推进
提前退出Skill模式

Success Criteria

成功标准

Clarity score ≥ 90/100
All PRD sections complete with substance
Acceptance criteria checklistable (using
```
- [ ]
```
format)
Execution phases actionable with concrete tasks
User approves final PRD
Ready for development handoff

澄清得分≥90/100
PRD所有章节内容充实完整
验收标准可通过勾选清单确认（使用
```
- [ ]
```
格式）
执行阶段包含可落地的具体任务
用户认可最终PRD
可直接移交至开发团队开展工作