Back to Details

agency-sprint-prioritizer

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Sprint Prioritizer

Sprint优先级排序工具

Use this skill when the problem is choosing what to do next within delivery constraints.
当你需要在交付限制内选择下一步工作时，可以使用这个方法。

Best for

适用场景

  • Sprint planning and backlog selection
  • Ranking work by value, effort, risk, and dependency
  • Cutting scope to fit a real delivery window
  • Making prioritization tradeoffs explicit for stakeholders
  • Sprint规划与待办事项（Backlog）筛选
  • 按价值、工作量、风险及依赖关系对工作进行排序
  • 削减范围以适配实际交付周期
  • 向利益相关方明确优先级权衡方案

Workflow

工作流程

  1. Start with the real delivery window and team capacity.
  2. Inventory candidate work with:
    • expected value
    • effort
    • dependencies
    • delivery risk
    • whether it is must-have or optional
  3. Choose the lightest useful prioritization framework for the decision:
    • simple value vs effort
    • RICE
    • must-have vs nice-to-have
  4. Build the proposed sprint or backlog slice.
  5. Call out what was excluded and why.
  1. 从实际交付周期和团队容量开始。
  2. 梳理候选工作的以下信息：
    • 预期价值
    • 工作量
    • 依赖关系
    • 交付风险
    • 是否为必备项或可选项
  3. 为决策选择最适用的轻量化优先级排序框架：
    • 简单价值vs工作量框架
    • RICE
    • 必备项vs锦上添花项框架
  4. 构建拟议的Sprint或待办事项切片。
  5. 说明被排除的工作及其原因。

Output contract

输出约定

Produce:
  • ranked backlog or sprint slice
  • rationale for ordering
  • assumptions about capacity
  • scope cuts and deferrals
  • major risks or blockers
需生成：
  • 排序后的待办事项或Sprint切片
  • 排序理由
  • 关于团队容量的假设
  • 范围削减与延后事项
  • 主要风险或障碍

Critical rules

关键规则

  1. Do not prioritize without a stated capacity assumption.
  2. Prefer explicit tradeoffs over vague “high priority” labels.
  3. Separate must-have work from polish.
  4. Include dependencies that can invalidate the order.
  5. Say what should be deferred, not only what should be done.
  1. 若无明确的容量假设，不得进行优先级排序。
  2. 优先采用明确的权衡方案，而非模糊的“高优先级”标签。
  3. 将必备工作与优化工作分开。
  4. 纳入可能影响排序有效性的依赖关系。
  5. 说明应延后的工作，而非仅说明应开展的工作。

Starter prompts

起始提示语

  • Prioritize this backlog for the next sprint using explicit value, effort, and dependency tradeoffs.
  • Given this capacity, tell me what actually fits and what should be cut.
  • Turn this feature list into a ranked plan with clear deferrals and risk notes.
  • 使用明确的价值、工作量和依赖关系权衡，为下一个Sprint排序此待办事项。
  • 基于此容量，告诉我哪些工作实际可纳入，哪些应被削减。
  • 将此功能列表转化为包含明确延后事项和风险说明的排序计划。

Autonomous decision rules

自主决策规则

Use this skill when:
  • the user asks what should happen next in a sprint or backlog
  • the problem is ordering or cutting work, not defining the whole project plan
Do NOT use when:
  • the task is broad cross-functional delivery planning better handled by 
    agency-project-shepherd
  • the task is long-horizon portfolio strategy better handled by 
    agency-studio-producer
适用场景：
  • 用户询问Sprint或待办事项中下一步应开展的工作
  • 问题为工作排序或削减，而非定义整个项目计划
不适用场景：
  • 任务为需由
    agency-project-shepherd
    处理的跨职能交付规划
  • 任务为需由
    agency-studio-producer
    处理的长期组合策略