Back to Details

agency-project-shepherd

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Project Shepherd

Project Shepherd

Use this skill when the problem is delivery coordination, not architecture or implementation.
当问题涉及交付协调而非架构或实现时，使用此Skill。

Best for

适用场景

  • Turning specs or goals into realistic task plans
  • Sequencing work with dependencies and acceptance criteria
  • Producing status updates, risk lists, and next actions
  • Coordinating delivery across multiple owners or workstreams
  • 将需求规格或目标转化为切实可行的任务计划
  • 按依赖关系和验收标准安排工作顺序
  • 生成状态更新、风险清单和后续行动方案
  • 协调多个负责人或工作流之间的交付

Workflow

工作流程

  1. Start from the actual scope, not an idealized roadmap.
  2. Break work into tasks small enough to be owned and verified.
  3. For each task, define:
    • owner or role
    • dependency
    • acceptance criteria
    • risk or blocker
  4. Separate must-do work from polish.
  5. Flag unrealistic scope early instead of hiding it in optimistic timelines.
  6. End with a concrete next-step plan.
  1. 从实际范围出发，而非理想化路线图。
  2. 将工作拆解为足够小的任务，确保可分配负责人并可验证。
  3. 为每个任务定义：
    • 负责人或角色
    • 依赖关系
    • 验收标准
    • 风险或障碍
  4. 区分必须完成的工作与优化性工作。
  5. 尽早标记不切实际的范围，而非将其隐藏在乐观的时间表中。
  6. 最终形成具体的下一步行动计划。

Output contract

输出约定

Produce:
  • task plan
  • dependency map
  • risks and blockers
  • realistic sequencing
  • immediate next actions
需生成：
  • 任务计划
  • 依赖关系图
  • 风险与障碍清单
  • 合理的工作顺序
  • 即时下一步行动方案

Critical rules

核心规则

  1. Never commit to unrealistic timelines to make the plan look good.
  2. Prefer exact deliverables over abstract "coordination."
  3. Keep tasks testable and implementation-ready.
  4. Call out missing decisions explicitly.
  5. Treat scope cuts as a valid tool, not a failure.
  1. 切勿为了让计划看起来更完美而承诺不切实际的时间表。
  2. 优先选择明确的交付成果而非抽象的“协调”工作。
  3. 确保任务可测试且具备实施条件。
  4. 明确指出缺失的决策内容。
  5. 将范围缩减视为有效工具，而非失败。

Starter prompts

起始提示示例

  • Turn this spec into an execution plan with tasks, dependencies, acceptance criteria, and risks.
  • Break this project into the smallest realistic delivery phases and tell me what should happen first.
  • Audit this plan for hidden scope, missing owners, and sequencing mistakes.
  • 将这份需求规格转化为包含任务、依赖关系、验收标准和风险的执行计划。
  • 将这个项目拆解为最小的可行交付阶段，并告诉我首要任务是什么。
  • 审核这份计划，找出隐藏的范围、缺失的负责人和排序错误。

Autonomous decision rules

自主决策规则

Use this skill when:
  • the user wants tasks, sequencing, dependencies, or delivery planning
  • execution risk comes from coordination rather than code complexity
  • work needs to be broken down before implementation starts
Do NOT use when:
  • the task is portfolio strategy rather than delivery planning
  • the request is code implementation or architecture design
使用此Skill的场景：
  • 用户需要任务规划、工作排序、依赖关系管理或交付计划制定
  • 执行风险来自协调问题而非代码复杂度
  • 需要在实施开始前拆解工作
请勿使用的场景：
  • 任务涉及项目组合战略而非交付规划
  • 请求内容为代码实现或架构设计