gsd-execute-phase
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese<objective>
Execute all plans in a phase using wave-based parallel execution.
Orchestrator stays lean: discover plans, analyze dependencies, group into waves, spawn subagents, collect results. Each subagent loads the full execute-plan context and handles its own plan.
Context budget: ~15% orchestrator, 100% fresh per subagent.
</objective>
<execution_context>
@{{PLATFORM_ROOT}}/get-shit-done/workflows/execute-phase.md
@{{PLATFORM_ROOT}}/get-shit-done/references/ui-brand.md
</execution_context>
<context>
Phase: $ARGUMENTS
Flags:
- — Execute only gap closure plans (plans with
--gaps-onlyin frontmatter). Use after verify-work creates fix plans.gap_closure: true
Context files are resolved inside the workflow via and per-subagent blocks.
</context>
<process>
Execute the execute-phase workflow from @{{PLATFORM_ROOT}}/get-shit-done/workflows/execute-phase.md end-to-end.
Preserve all workflow gates (wave execution, checkpoint handling, verification, state updates, routing).
</process>gsd-tools init execute-phase<files_to_read><objective>
采用波浪式并行执行方式，执行一个阶段中的所有计划。
Orchestrator 保持轻量化：发现计划、分析依赖关系、分组为波浪、生成subagent、收集结果。每个subagent加载完整的执行计划上下文并处理自己的计划。
上下文预算：约15% 分配给Orchestrator，每个subagent分配100%的全新上下文。
</objective>
<execution_context>
@{{PLATFORM_ROOT}}/get-shit-done/workflows/execute-phase.md
@{{PLATFORM_ROOT}}/get-shit-done/references/ui-brand.md
</execution_context>
<context>
阶段：$ARGUMENTS
标志：
- — 仅执行缺口填补计划（在前置元数据中包含
--gaps-only的计划）。在verify-work创建修复计划后使用。gap_closure: true
上下文文件通过工作流中的和每个subagent的块进行解析。
</context>
<process>
端到端执行@{{PLATFORM_ROOT}}/get-shit-done/workflows/execute-phase.md中的execute-phase工作流。
保留所有工作流关卡（波浪执行、检查点处理、验证、状态更新、路由）。
</process>gsd-tools init execute-phase<files_to_read>