Research: Dynamic Workflows as an optional execution backend for Squad ceremonies
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 35/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- github, typescript
研究方向
Start by reading the current ceremony specification and the entry points for Ralph, squad loop, and schedule.json, then compare them with the Dynamic Workflows concepts and limits in the linked GitHub documentation. Use one existing ceremony for an opt-in adapter spike, keeping irreversible actions out. Done means a capability mapping, working comparison, recovery and approval demonstrations, and a recommendation for the portable model.
由索引模型根據 Issue 內容生成。
描述
Context
GitHub recently introduced Dynamic Workflows for Copilot CLI, the Copilot app, and the Copilot SDK. Extensions can define orchestration in code while agents handle reasoning: sequential and parallel stages, conditional paths, structured results, verification, checkpoints, pause/resume, and resource limits.
This overlaps with capabilities Squad already has or is defining: ceremonies, /fleet coordination, squad loop, Ralph, scheduling, recovery, verification roles, and rate/resource governance.
For the next version, investigate whether Dynamic Workflows can become an optional execution backend for Squad, without making Squad's portable model dependent on this GitHub feature.
References:
Qualifications: the feature is in public preview. Deterministic orchestration does not make agent outputs deterministic. Human interaction depends on the client. AI-credit limits are approximate, not hard spending ceilings. Scheduling should be investigated as a host/automation integration rather than assumed to be a native workflow primitive. Reusing a workflow definition is distinct from resuming a run with saved results.
Areas to investigate
1. Ceremonies as executable workflows
A ceremony could describe a portable process:
research -> challenge -> plan -> approve -> implement -> verify
A Copilot adapter could translate that ceremony into a Dynamic Workflow: workflow code controls execution, while Squad agents provide reasoning at specific stages.
Compare the current ceremony specification with actual workflow primitives. Identify existing semantics, gaps, and potential new portable concepts. Do not assume ceremonies are already executable task graphs.
2. Reusable multi-agent coordination patterns
Examples:
parallel review -> challenge -> reconcile -> final result
research -> architecture -> plan -> parallel implementation -> test -> security review -> approval -> PR
Determine what belongs in the portable model versus the adapter: structured stage contracts, dependencies, conditional transitions, failure handling, bounded retries, and parallel-work isolation. Parallel agents must not silently overwrite shared files or team state.
3. Dynamic Workflows as an execution backend
Evaluate:
Squad ceremony/task graph -> execution adapter -> Copilot Dynamic Workflow
The adapter should sit alongside existing execution mechanisms, not replace them by default. Compare preservation of agent identity, charters, routing, permissions, shared decisions, and persistent memory.
Define a backend capability contract. Unsupported semantics must be surfaced explicitly, not silently skipped or weakened. Keep preview-specific APIs inside the Copilot adapter.
4. Verification and approval gates
Could Challenger, Worf, and fact-checker become required execution stages rather than instructions an orchestrating agent is expected to remember?
implementation -> security review -> adversarial review -> tests -> consensus/gate -> human approval
Investigate portable concepts for required reviewers, evidence, approval, rejection, disagreement, and escalation. Distinguish model consensus from executable checks and human authorization: agent agreement is not proof of correctness.
Define behavior when a reviewer fails, returns malformed output, or disagrees, and when a client cannot present an approval prompt. Missing approval must not become implicit approval.
5. Long-running and scheduled work
Compare backend capabilities with Ralph, squad loop, schedule.json, recovery/checkpointing, rate/resource governance, and unattended execution.
Investigate whether the backend can own execution mechanics while Squad retains portable intent and policy. Separate scheduling/triggering from workflow execution.
Assess cancellation, interruption, retry, resume, and reuse of completed results. Determine how resumed runs avoid duplicate side effects such as publishing, PR creation, or decision writes. Document what happens if the ceremony, repository revision, or workflow definition changes between pause and resume.
Key architectural question
Squad defines WHO + WHAT + PROCESS: agents and roles, tasks, ceremonies, dependencies, policies, and gates.
Execution backends implement HOW: dispatch, parallel execution, conditional transitions, runtime checkpointing/resume, and resource accounting/enforcement. Scheduling may come from the host or a separate trigger adapter.
The intended semantics of a dependency, gate, or policy remain Squad-owned; the backend supplies the mechanism. Dynamic Workflows could be one backend, with a capability-based path for non-Copilot runtimes.
Research questions
- How closely do existing ceremonies map to Dynamic Workflow primitives?
- Which orchestration concepts should remain portable?
- Do we need explicit gates, approvals, consensus rules, parallel stages, dependencies, and structured stage contracts?
- Could
schedule.jsonreference a ceremony and inputs rather than describe orchestration itself? - Which runtime responsibilities can be delegated, and which must remain Squad-owned?
- Can an adapter preserve charters, memory ownership, routing, and governance without duplicating Squad's runtime?
- How do backend limits relate to Squad rate governance, including approximate credit ceilings and work already in flight?
- What permissions apply to agents versus extension code? GitHub documents that extension code can execute outside agent permission prompts; how should Squad governance cover that boundary?
- What guarantees exist for checkpoint persistence, retries, cancellation, and side-effect idempotency?
- How do approval and unattended execution behave across CLI, app, SDK, and non-interactive clients?
- How do we avoid coupling the specification to a preview API, and what does this imply for future non-Copilot backends?
Suggested next-version spike
Select one existing ceremony, or the closest supported equivalent, and implement an opt-in Dynamic Workflow adapter. Candidate:
research -> parallel specialist review -> Challenger -> plan approval -> implementation -> Worf review -> tests -> human approval
Compare:
- Current Squad execution.
- Dynamic Workflow execution.
- The smallest portable representation supporting both.
Use the same bounded task and inputs. Keep publication, merges, and other irreversible actions out of the initial spike. Include approval before implementation, not only after it.
Deliverables / completion criteria
- A mapping of ceremony semantics to backend capabilities, including unsupported features and gaps.
- A small working adapter and example preserving agent identity, charters, and ownership rules.
- A comparison of behavior, orchestration overhead, observed latency and AI-credit usage, observability, and recovery; record results rather than assume savings.
- Demonstrations of success, reviewer rejection/disagreement, failed checks, pause/resume, reached resource limits, and unavailable approval channels.
- Evidence that required gates cannot be bypassed and resumed stages do not repeat completed side effects.
- A recommendation: adopt an optional backend, extend the portable model first, or defer, with preview/API risks and implications for non-Copilot runtimes.
Non-goals
- Replacing Squad orchestration or removing human oversight.
- Making Dynamic Workflows mandatory.
- Redesigning all ceremonies, scheduling, or Ralph in this spike.
- Treating agent agreement as a substitute for tests or authorization.
The goal is to determine whether Dynamic Workflows can serve as a runtime target for Squad's portable coordination model, not to couple Squad to one execution engine.
CC @bradygaster
- 主要語言
- TypeScript
- 星號
- 3.4k
- 分支
- 516
- 平均合併
- 1 天 15 小時
- 30 天內合併 PR
- 116
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
github/squad 的其他 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 84/100
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 77/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
相似的 Issue
-
bot:ai-assisted component:platform-js status:untriaged
難度 1/5 1 小時以內 新手友好度 74/100
midnightntwrk/platform-js#38 ·
-
難度 2/5 1-3 小時 新手友好度 68/100
ranxianglei/billion-context#7068 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
mybigday/whisper.rn#348 ·
-
enhancement severity:low
難度 2/5 1-3 小時 新手友好度 82/100
Battle-Cattle/BCUK-Bot-4#1075 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 67/100
ilan-pinto/roaring-lions#1552 ·
維護者通常 1 天內回覆