Add /saga skill for autonomous spec-driven development#32
Conversation
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR adds a new /saga skill and supporting reference docs for a spec-driven, orchestrator/worker workflow.
Concerns
- The worker contract requires force-removing task worktrees before it requires any commit, push, patch, or other durable handoff. That can discard validated implementation work and leave only an unchanged branch for milestone integration.
- Resume guidance would be more reliable if
PROGRESS.mdrecorded addressable worker identifiers for in-progress tasks, since a fresh orchestrator cannot message a prior worker by display name alone.
Verdict
Found: 0 critical, 1 important, 1 suggestions
Request changes
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
|
|
||
| 1. Implement only its assigned task and owned files. | ||
| 2. **Self-validate in a loop** against the task's validation criteria using the prescribed method (computer use / interactive CLI subagent / unit + integration tests). Iterate fix→validate until all criteria pass or it is genuinely blocked. | ||
| 3. **Remove the worktree** once validation passes (or before reporting a blocked status): `git worktree remove <worktree-path> --force`. The branch persists; the worktree does not. Stale worktrees are unacceptable — this step is not optional. |
There was a problem hiding this comment.
There was a problem hiding this comment.
worth addresing this comment
| <One line per task: status, branch, evidence pointer. | ||
| Branch naming convention: saga/<saga-name>/m<M>t<T>-<task-slug> (prepend a team/user branch prefix if your repo requires one)> | ||
| - 1.1 <name>: done — branch saga/<saga-name>/m1t1-<slug>, evidence: <pointer / test names / screenshot path> | ||
| - 1.2 <name>: in progress (worker <name>, worktree ../saga-<saga-name>-m1t2) |
There was a problem hiding this comment.
💡 [SUGGESTION] Store the worker's addressable agent/run ID here, not only a display name, so a fresh orchestrator can actually resume or message in-progress work.
|
|
||
| 1. Implement only its assigned task and owned files. | ||
| 2. **Self-validate in a loop** against the task's validation criteria using the prescribed method (computer use / interactive CLI subagent / unit + integration tests). Iterate fix→validate until all criteria pass or it is genuinely blocked. | ||
| 3. **Remove the worktree** once validation passes (or before reporting a blocked status): `git worktree remove <worktree-path> --force`. The branch persists; the worktree does not. Stale worktrees are unacceptable — this step is not optional. |
There was a problem hiding this comment.
worth addresing this comment
Adds the saga skill: an orchestrator-driven, spec-first workflow for autonomously implementing medium-to-large features with a fleet of worker subagents. - Phase 1: collaborative planning that produces a resumable spec tree (SAGA.md + per-milestone/per-task specs) with airtight, per-level validation criteria stored in a saga directory under ~/.sagas. - Phase 2: parallelized implementation via worker agents in isolated git worktrees, each self-validating against its task contract; orchestrator integrates and validates per milestone while preserving its context. - Phase 3: final saga-level validation and human acceptance. Includes reference docs for the spec templates, validation strategies, and continuing/resuming a saga with a fresh orchestrator. Generalized for any user/team (neutral saga/ branch convention, per-user ~/.sagas). Co-Authored-By: Oz <oz-agent@warp.dev>
zachbai
force-pushed
the
zb/add-saga-skill
branch
from
c9f3758 to
a13effc
Compare
2 participants
Adds the saga skill: an orchestrator-driven, spec-first workflow for
autonomously implementing medium-to-large features with a fleet of worker
subagents.
(SAGA.md + per-milestone/per-task specs) with airtight, per-level
validation criteria stored in a saga directory under ~/.sagas.
worktrees, each self-validating against its task contract; orchestrator
integrates and validates per milestone while preserving its context.
Includes reference docs for the spec templates, validation strategies, and
continuing/resuming a saga with a fresh orchestrator. Generalized for any
user/team (neutral saga/ branch convention, per-user ~/.sagas).
Co-Authored-By: Oz oz-agent@warp.dev