resource-development

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Resource Development: Infrastructure and Tooling

资源开发:基础设施与工具

Overview

概述

The Underboss decomposes the signed Contract into Work Packages, sets up infrastructure for parallel execution, and produces the War Plan — the detailed task breakdown that governs The Hit.
Underboss将已签署的合同拆解为工作包,搭建用于并行执行的基础设施,并生成作战计划——这份详细的任务分解将指导The Hit(执行阶段)的开展。

Trigger

触发条件

Invoked after the Don signs the Contract (The Sit-Down complete).
在Don签署合同后触发(即The Sit-Down(洽谈阶段)完成)。

Process

流程

Step 1: Decompose Contract into Work Packages

步骤1:将合同拆解为工作包

For each requirement in the Contract:
  1. Identify affected files (create/modify)
  2. Determine territory ownership (which Capo)
  3. Define acceptance criteria (from Contract)
  4. Write verification command
  5. Estimate token budget
Each Work Package must be:
  • Independent — Can be implemented without waiting for other Work Packages (within the same territory, order may matter)
  • Verifiable — Has a specific test or command that proves it works
  • Bite-sized — 2-5 minutes of Soldier work
  • Traceable — References a specific Contract clause
针对合同中的每一项需求:
  1. 确定受影响的文件(创建/修改)
  2. 确定工作区域负责人(对应哪个Capo)
  3. 定义验收标准(来源于合同)
  4. 编写验证命令
  5. 估算Token预算
每个工作包必须满足:
  • 独立性 — 无需等待其他工作包即可实施(同一工作区域内的任务可能存在顺序要求)
  • 可验证性 — 具备特定测试或命令以验证功能有效性
  • 小型化 — 仅需Soldier(执行人员)2-5分钟即可完成
  • 可追溯性 — 关联到合同中的具体条款

Step 2: Define Territories

步骤2:定义工作区域

Group Work Packages by domain and define Capo territories:
markdown
undefined
按领域对工作包进行分组,并定义各Capo负责的工作区域:
markdown
undefined

Territory: <Name>

Territory: <名称>

Domain: <Description> Files: <Glob patterns> Work Packages: WP-001, WP-003, WP-007 Soldiers: <Parallel count> Budget: <Token allocation>
undefined
Domain: <描述> Files: <Glob匹配模式> Work Packages: WP-001, WP-003, WP-007 Soldiers: <并行执行人数> Budget: <Token分配额度>
undefined

Step 3: Set Up Isolation

步骤3:设置隔离环境

If the project uses git:
  • Create a branch for the Heist:
    heist/<heist-name>
  • Optionally create worktrees per territory for true parallel work
If not:
  • Document the isolation strategy (directory copies, etc.)
若项目使用Git:
  • 为本次Heist(项目任务)创建分支:
    heist/<heist-name>
  • 可选:为每个工作区域创建工作树以实现真正的并行工作
若未使用Git:
  • 记录隔离策略(如目录复制等)

Step 4: Verify Prerequisites

步骤4:验证前置条件

Before The Hit begins:
  • All existing tests pass on the current baseline
  • Required dependencies are available
  • File paths in Work Packages are valid
  • No merge conflicts with the base branch
在The Hit(执行阶段)开始前:
  • 当前基线版本的所有测试均通过
  • 所需依赖已准备就绪
  • 工作包中指定的文件路径有效
  • 与基准分支无合并冲突

Step 5: Produce War Plan

步骤5:生成作战计划

Compile everything into the War Plan.
将所有内容整合为作战计划。

War Plan Format

作战计划格式

Save to:
docs/gangsta/<heist-name>/plans/YYYY-MM-DD-war-plan.md
markdown
---
heist: <heist-name>
date: YYYY-MM-DD
total-work-packages: <N>
territories: <N>
estimated-total-budget: <tokens>
---
保存路径:
docs/gangsta/<heist-name>/plans/YYYY-MM-DD-war-plan.md
markdown
---
heist: <heist-name>
date: YYYY-MM-DD
total-work-packages: <数量>
territories: <数量>
estimated-total-budget: <tokens>
---

War Plan: <Heist Name>

War Plan: <Heist名称>

Territories

工作区域

Territory: <Name 1>

Territory: <名称1>

Capo Domain: <description> Files: <globs> Soldiers: <N parallel> Budget: <tokens>
Capo负责领域: <描述> Files: <Glob匹配模式> Soldiers: <N个并行执行人员> Budget: <tokens>

Territory: <Name 2>

Territory: <名称2>

...
...

Work Packages

工作包

WP-001: <Title>

WP-001: <标题>

Territory: <Name> Contract Clause: FR-001 Files:
  • Create:
    path/to/file
  • Test:
    tests/path/to/test
    Acceptance Criteria:
  1. <criterion>
Verification:
<command>
Budget: <tokens> Dependencies: None | WP-XXX
Territory: <名称> Contract Clause: FR-001 Files:
  • Create:
    path/to/file
  • Test:
    tests/path/to/test
    Acceptance Criteria:
  1. <标准> Verification:
    <命令>
    Budget: <tokens> Dependencies: None | WP-XXX

WP-002: <Title>

WP-002: <标题>

...
...

Execution Order

执行顺序

  1. Independent packages (can run in parallel): WP-001, WP-002, WP-005
  2. Depends on group 1: WP-003 (needs WP-001)
  3. ...
  1. 独立工作包(可并行执行):WP-001, WP-002, WP-005
  2. 依赖第一组的工作包:WP-003(需要WP-001)
  3. ...

Baseline Verification

基线验证

  • Tests: <PASS/FAIL — must be PASS>
  • Dependencies: <OK/MISSING>
  • Branch: heist/<heist-name> created from <base>
undefined
  • Tests: <PASS/FAIL — 必须为PASS>
  • Dependencies: <OK/MISSING>
  • Branch: heist/<heist-name><base>分支创建
undefined

Step 6: Don Approves War Plan

步骤6:Don批准作战计划

Present to the Don:
"War Plan ready. <N> Work Packages across <N> territories. Estimated budget: <tokens>. Ready to execute The Hit?"
向Don汇报:
"作战计划已准备就绪。共<N>个工作包,分布在<N>个工作区域。预估总预算:<tokens>。是否可以启动The Hit(执行阶段)?"

Checkpoint

检查点

yaml
---
heist: <heist-name>
phase: resource-development
status: completed
timestamp: <ISO 8601>
next-action: Proceed to The Hit
artifacts:
  - docs/gangsta/<heist-name>/plans/YYYY-MM-DD-war-plan.md
---
yaml
---
heist: <heist-name>
phase: resource-development
status: completed
timestamp: <ISO 8601格式时间>
next-action: Proceed to The Hit
artifacts:
  - docs/gangsta/<heist-name>/plans/YYYY-MM-DD-war-plan.md
---

Omerta Compliance

Omerta合规性检查

  • Spec is Law: Every Work Package traces to a Contract clause
  • Rule of Tribute: Token budgets allocated per territory
  • Rule of Availability: War Plan and checkpoint saved
  • 规格即法律:每个工作包均可追溯至合同条款
  • 贡献规则:按工作区域分配Token预算
  • 可用性规则:已保存作战计划与检查点记录