Back to Details

scope

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Scope

范围

Turn ideas into specs that AI tools can execute and stakeholders can evaluate.
将想法转化为AI工具可执行、利益相关方可评估的规格说明。

When to Use This Skill

何时使用该技能

  • Starting any new feature or product
  • Before hiring developers or estimating costs
  • When AI keeps building the wrong thing (unclear spec)
  • When stakeholders need to review scope and budget
  • 启动任何新功能或产品时
  • 雇佣开发人员或估算成本前
  • AI持续生成不符合需求的内容时（规格说明不清晰）
  • 利益相关方需要审核范围和预算时

Choose Your Approach

选择合适的方法

Quick Feature Spec (10-15 minutes)
  • Use for: Single features, iterations, additions
  • Give to: AI tools (Claude Code, Lovable, Replit) to build directly
  • See: QUICK-SPEC.md
Full Project Scope (1-2 hours)
  • Use for: New products, major releases, stakeholder review
  • Give to: Contractors, team members, budget planning
  • See: PROJECT-SCOPE.md
快速功能规格（10-15分钟）
  • 适用场景：单一功能、迭代优化、功能新增
  • 交付对象：AI工具（Claude Code、Lovable、Replit）直接用于构建
  • 查看详情：QUICK-SPEC.md
完整项目范围说明书（1-2小时）
  • 适用场景：新产品、重大版本发布、利益相关方审核
  • 交付对象：承包商、团队成员、用于预算规划
  • 查看详情：PROJECT-SCOPE.md

Quick Feature Spec Workflow

快速功能规格工作流程

Use this checklist and complete each section:
Feature Spec Progress:
- [ ] Write what users will do (2-3 sentences)
- [ ] Show what it looks like (reference, screenshot, or description)
- [ ] Define happy path (3-5 steps)
- [ ] List edge cases (2-4 scenarios)
- [ ] Specify out of scope items
- [ ] Save to docs/specs/YYYY-MM-DD-feature-name.md
使用以下清单完成每个部分：
Feature Spec Progress:
- [ ] Write what users will do (2-3 sentences)
- [ ] Show what it looks like (reference, screenshot, or description)
- [ ] Define happy path (3-5 steps)
- [ ] List edge cases (2-4 scenarios)
- [ ] Specify out of scope items
- [ ] Save to docs/specs/YYYY-MM-DD-feature-name.md

Section 1: What Users Will Do

第1部分：用户操作说明

Write 2-3 sentences describing user actions and outcomes.
Template:
Users can [ACTION] to [OUTCOME].
When they [DO THIS], they see [WHAT HAPPENS].
If [EDGE CASE], then [WHAT HAPPENS].
Example:
Users sign up with email/password, receive confirmation email, and log in to 
see their dashboard. They can reset forgotten passwords via email link.
用2-3句话描述用户的操作及预期结果。
模板：
Users can [ACTION] to [OUTCOME].
When they [DO THIS], they see [WHAT HAPPENS].
If [EDGE CASE], then [WHAT HAPPENS].
示例：
Users sign up with email/password, receive confirmation email, and log in to 
see their dashboard. They can reset forgotten passwords via email link.

Section 2: What It Looks Like

第2部分：界面呈现说明

Pick ONE:
  • Reference app: "Login like Linear - minimal, centered, email/password/button"
  • Screenshot/sketch: Quick mockup or phone photo
  • Description: "Card 400px wide, 'Welcome' header Inter 24px, two inputs, blue button"
选择以下一种方式：
  • 参考应用： "登录界面参考Linear - 极简风格、居中布局、包含邮箱/密码输入框和按钮"
  • 截图/草图： 快速原型图或手机拍摄的照片
  • 文字描述： "卡片宽度400px，标题为'欢迎'，使用Inter字体24px，包含两个输入框和蓝色按钮"

Section 3: Happy Path

第3部分：正常流程

List 3-5 steps users take to complete the task.
列出用户完成任务的3-5个步骤。

Section 4: Edge Cases

第4部分：异常场景

List 2-4 scenarios where things don't go as planned and what happens.
Format:
- **[Scenario]:** [Response shown to user]
列出2-4种非预期场景及对应的处理逻辑。
格式：
- **[Scenario]:** [Response shown to user]

Section 5: Out of Scope

第5部分：非范围内容

Define what you're NOT building to prevent scope creep.
For complete template and examples, see QUICK-SPEC.md
明确说明不包含的功能，以防止范围蔓延。
完整模板及示例请查看QUICK-SPEC.md

Full Project Scope Workflow

完整项目范围说明书工作流程

Use this checklist for comprehensive project planning:
Project Scope Progress:
- [ ] Write introduction (background, in/out of scope)
- [ ] Define user roles
- [ ] List all pages/screens
- [ ] Describe core features
- [ ] Identify integrations
- [ ] Create milestones with hour estimates
- [ ] Document assumptions and open questions
- [ ] Save to docs/specs/YYYY-MM-DD-project-name.md
使用以下清单进行全面项目规划：
Project Scope Progress:
- [ ] Write introduction (background, in/out of scope)
- [ ] Define user roles
- [ ] List all pages/screens
- [ ] Describe core features
- [ ] Identify integrations
- [ ] Create milestones with hour estimates
- [ ] Document assumptions and open questions
- [ ] Save to docs/specs/YYYY-MM-DD-project-name.md

The 7 Required Sections

7个必填部分

  1. Introduction - Background, in scope, out of scope
  2. User Roles - Each role's responsibilities
  3. Pages & Screens - Every page with one-line purpose
  4. Core Features - Outcome-focused capabilities
  5. Integrations - External services with complexity/risk notes
  6. Milestones & Tasks - Phases with hour estimates
  7. Open Questions - Assumptions and unresolved decisions
For complete template and examples, see PROJECT-SCOPE.md
  1. 引言 - 项目背景、包含范围、排除范围
  2. 用户角色 - 每个角色的职责
  3. 页面与界面 - 所有页面的一句话用途说明
  4. 核心功能 - 以结果为导向的功能说明
  5. 集成服务 - 外部服务及复杂度/风险说明
  6. 里程碑与任务 - 各阶段及工时估算
  7. 待解决问题 - 假设前提及未决议题
完整模板及示例请查看PROJECT-SCOPE.md

Using Your Spec With AI Tools

如何将规格说明用于AI工具

Claude Code / Cursor:
Build this feature: [paste Quick Feature Spec]
Lovable / Replit / Bolt:
  • Paste Quick Feature Spec as initial prompt
  • Break complex features into smaller chunks
  • Iterate: "Close, but error message should say X not Y"
Hiring contractors:
  • Send Full Project Scope
  • Ask: "What's unclear? What would you change?"
  • Get hour estimate and compare to yours
Claude Code / Cursor：
Build this feature: [paste Quick Feature Spec]
Lovable / Replit / Bolt：
  • 将快速功能规格作为初始提示词粘贴
  • 将复杂功能拆分为更小的模块
  • 迭代优化："接近了，但错误提示应该显示X而不是Y"
雇佣承包商时：
  • 发送完整项目范围说明书
  • 询问："哪些内容不清晰？你会做出哪些调整？"
  • 获取工时估算并与你的估算对比

Common Mistakes

常见错误

MistakeFix
"Build a dashboard"Describe what's ON dashboard and what each thing does
Describing HOW to code itDescribe WHAT it should do
Forgetting mobileAdd "Works on mobile" to every spec
Skipping edge casesDefine what happens when things break
No out-of-scopePrevents scope creep
错误解决方法
"构建一个仪表盘"描述仪表盘上的内容及每个元素的功能
描述代码实现方式说明功能应该实现的效果
忽略移动端适配在每个规格说明中添加"支持移动端"
跳过异常场景定义出现问题时的处理逻辑
未明确非范围内容防止范围蔓延

When You're Stuck

遇到瓶颈时的解决方法

"I don't know what I want yet"
  • Use competitor's product for 20 minutes
  • Screenshot 3 things you like
  • Write: "I want these 3 things, but simpler"
"AI keeps building the wrong thing"
  • Your spec is vague
  • Use templates in QUICK-SPEC.md or PROJECT-SCOPE.md
  • Fill in EVERY section
"我还不清楚自己想要什么"
  • 使用竞品产品20分钟
  • 截图3个你喜欢的功能
  • 写下："我想要这3个功能，但更简洁的版本"
"AI持续生成不符合需求的内容"
  • 你的规格说明不够明确
  • 使用QUICK-SPEC.md或PROJECT-SCOPE.md中的模板
  • 填写每个部分的内容

After Scoping

完成规格说明后

Save as: 
docs/specs/YYYY-MM-DD-feature-name.md
Then:
  • Quick Feature Spec → Give directly to AI tool
  • Full Project Scope → Review with stakeholders/contractors first
保存格式： 
docs/specs/YYYY-MM-DD-feature-name.md
后续操作：
  • 快速功能规格 → 直接交付给AI工具
  • 完整项目范围说明书 → 先与利益相关方/承包商审核

Success Looks Like

成功的标志

✅ AI builds it right first time (or very close) ✅ Contractors give realistic estimates without surprises
✅ Edge cases don't surprise you in production ✅ Stakeholders know exactly what they're getting
✅ AI首次构建就符合需求（或非常接近） ✅ 承包商给出符合实际的估算，无意外情况 ✅ 异常场景在生产环境中不会造成突发问题 ✅ 利益相关方清楚知道最终交付内容