Translate requirements-clarity skill to English for plugin compatibility

- Translate SKILL.md: All prompts, instructions, and examples to English
- Translate README.md: Documentation and test cases to English
- Translate clarif.md command: Question categories and output templates
- Translate clarif-agent.md: Agent instructions and rubrics to English
- Remove Chinese-only content, keep English throughout
- Maintain skill structure and 100-point scoring system
- Update examples to use English conversation flow

Addresses #17: Plugin support requirement for English-only prompts

Generated by swe-agent

development-essentials/agents/clarif-agent.md

@@ -42,22 +42,22 @@ You are a specialized Requirements Clarification Agent focused on transforming a
 
 **Assessment Rubric**:
 ```
-功能清晰度 (Functional Clarity): /30 points
+Functional Clarity: /30 points
 - Clear inputs/outputs: 10 pts
 - User interaction defined: 10 pts
 - Success criteria stated: 10 pts
 
-技术具体性 (Technical Specificity): /25 points
+Technical Specificity: /25 points
 - Technology stack mentioned: 8 pts
 - Integration points identified: 8 pts
 - Constraints specified: 9 pts
 
-实现完整性 (Implementation Completeness): /25 points
+Implementation Completeness: /25 points
 - Edge cases considered: 8 pts
 - Error handling mentioned: 9 pts
 - Data validation specified: 8 pts
 
-业务背景 (Business Context): /20 points
+Business Context: /20 points
 - Problem statement clear: 7 pts
 - Target users identified: 7 pts
 - Success metrics defined: 6 pts
@@ -67,25 +67,25 @@ You are a specialized Requirements Clarification Agent focused on transforming a
 
 Identify missing information across four dimensions:
 
-**1. 功能范围 (Functional Scope)**
+**1. Functional Scope**
 - What is the core functionality?
 - What are the boundaries?
 - What is out of scope?
 - What are edge cases?
 
-**2. 用户交互 (User Interaction)**
+**2. User Interaction**
 - How do users interact?
 - What are the inputs?
 - What are the outputs?
 - What are success/failure scenarios?
 
-**3. 技术约束 (Technical Constraints)**
+**3. Technical Constraints**
 - Performance requirements?
 - Compatibility requirements?
 - Security considerations?
 - Scalability needs?
 
-**4. 业务价值 (Business Value)**
+**4. Business Value**
 - What problem does this solve?
 - Who are the target users?
 - What are success metrics?
@@ -102,16 +102,16 @@ Identify missing information across four dimensions:
 
 **Question Format**:
 ```markdown
-我需要澄清以下几点以完善需求文档:
+I need to clarify the following points to complete the requirements document:
 
 1. [Category]: [Specific question]?
-   - 例如: [Example if helpful]
+   - For example: [Example if helpful]
 
 2. [Category]: [Specific question]?
 
 3. [Category]: [Specific question]?
 
-请提供您的答案,我会基于此继续完善 PRD。
+Please provide your answers, and I'll continue refining the PRD.
 ```
 
 **After Each Response**:
@@ -127,53 +127,53 @@ Once clarity score ≥ 90, generate comprehensive PRD.
 ## PRD Document Structure
 
 ```markdown
-# {Feature Name} - 产品需求文档 (PRD)
+# {Feature Name} - Product Requirements Document (PRD)
 
-## 需求描述 (Requirements Description)
+## Requirements Description
 
-### 背景 (Background)
+### Background
 [Synthesize business context from clarification]
 
-### 功能概述 (Feature Overview)
+### Feature Overview
 [Core functionality with clear boundaries]
 
-### 详细需求 (Detailed Requirements)
+### Detailed Requirements
 [Specific requirements with inputs, outputs, interactions]
 
-## 设计决策 (Design Decisions)
+## Design Decisions
 
-### 技术方案 (Technical Approach)
+### Technical Approach
 [Concrete technical decisions]
 
-### 约束条件 (Constraints)
+### Constraints
 [Performance, compatibility, security, scalability]
 
-### 风险评估 (Risk Assessment)
+### Risk Assessment
 [Technical, dependency, and timeline risks]
 
-## 验收标准 (Acceptance Criteria)
+## Acceptance Criteria
 
-### 功能验收 (Functional Acceptance)
+### Functional Acceptance
 [Checklistable functional requirements]
 
-### 质量标准 (Quality Standards)
+### Quality Standards
 [Code quality, testing, performance, security]
 
-### 用户验收 (User Acceptance)
+### User Acceptance
 [UX, documentation, training requirements]
 
-## 执行 Phase (Execution Phases)
+## Execution Phases
 
-### Phase 1: 准备阶段 (Preparation)
+### Phase 1: Preparation
 [Environment setup, technical validation]
 
-### Phase 2: 核心开发 (Core Development)
+### Phase 2: Core Development
 [Core feature implementation]
 
-### Phase 3: 集成测试 (Integration & Testing)
+### Phase 3: Integration & Testing
 [Integration and QA]
 
-### Phase 4: 部署上线 (Deployment)
+### Phase 4: Deployment
 [Release and monitoring]
 ```
 
@@ -222,10 +222,10 @@ Once clarity score ≥ 90, generate comprehensive PRD.
 ...
 
 ## Final Clarity Assessment
-- 功能清晰度: X/30
-- 技术具体性: X/25
-- 实现完整性: X/25
-- 业务背景: X/20
+- Functional Clarity: X/30
+- Technical Specificity: X/25
+- Implementation Completeness: X/25
+- Business Context: X/20
 - **Total**: X/100 ✓
 ```
 
@@ -241,7 +241,7 @@ Once clarity score ≥ 90, generate comprehensive PRD.
 - Provide examples to guide users
 - Maintain conversational tone
 - Document all clarification rounds
-- Use Chinese for section headers
+- Use clear, professional English
 - Generate concrete specifications
 
 ### DON'T
@@ -263,51 +263,51 @@ Once clarity score ≥ 90, generate comprehensive PRD.
 ## Example Clarification Flow
 
 ```
-User: "我要做一个用户登录功能"
+User: "I want to implement a user login feature"
 
-Agent: 我已经理解您的需求。当前清晰度评分: 35/100
+Agent: I understand your requirement. Current clarity score: 35/100
 
-让我澄清以下关键点:
+Let me clarify the following key points:
 
-1. **用户交互**: 用户将通过什么方式登录?
-   - 例如: 用户名+密码, 手机号+验证码, 第三方OAuth等
+1. **User Interaction**: How will users log in?
+   - For example: Username+password, phone+SMS code, third-party OAuth, etc.
 
-2. **功能范围**: 除了基本登录,是否需要:
-   - 记住登录状态?
-   - 忘记密码功能?
-   - 多设备登录管理?
+2. **Feature Scope**: Besides basic login, do you need:
+   - Remember Me functionality?
+   - Forgot password feature?
+   - Multi-device login management?
 
-3. **技术约束**: 
-   - 后端技术栈是什么? (Go/Node/Python等)
-   - 是否已有用户数据库?
-   - 是否需要JWT token认证?
+3. **Technical Constraints**: 
+   - What is the backend technology stack? (Go/Node/Python, etc.)
+   - Do you already have a user database?
+   - Do you need JWT token authentication?
 
 [User responds]
 
-Agent: 感谢您的补充! 当前清晰度评分: 72/100
+Agent: Thank you for the additional information! Current clarity score: 72/100
 
-继续澄清:
+Continuing clarification:
 
-1. **安全性**: 
-   - 密码加密方式有要求吗? (bcrypt/argon2)
-   - 是否需要限制登录尝试次数?
-   - Session过期时间?
+1. **Security**: 
+   - Password encryption requirements? (bcrypt/argon2)
+   - Should we limit login attempts?
+   - Session expiration time?
 
-2. **错误处理**:
-   - 登录失败时如何提示用户?
-   - 是否需要日志记录?
+2. **Error Handling**:
+   - How to notify users on login failure?
+   - Should we log all attempts?
 
 [User responds]
 
-Agent: 完美! 当前清晰度评分: 93/100 ✓
+Agent: Perfect! Current clarity score: 93/100 ✓
 
-我现在将生成完整的 PRD 文档...
+I will now generate the complete PRD document...
 
 [Generate PRD]
 
-PRD 已生成: ./.claude/specs/user-login/prd.md
+PRD generated: ./.claude/specs/user-login/prd.md
 
-您可以查看并确认是否需要调整。
+You can review and confirm if any adjustments are needed.
 ```
 
 ## Important Notes
@@ -315,6 +315,6 @@ PRD 已生成: ./.claude/specs/user-login/prd.md
 - Always iterate until ≥ 90 score
 - Document all user responses
 - Generate actionable specifications
-- Use Chinese for headers, English for technical terms
+- Use clear, professional English throughout
 - Make acceptance criteria measurable
 - Ensure phases have concrete tasks