Skip to content

Prefer opencode delegate command for Build handoffs #124

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
SorraTheOrc merged 2 commits into from
Jan 14, 2026
Merged

Prefer opencode delegate command for Build handoffs #124

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c38ea9b
build: prefer opencode delegate command for structured handoffs
SorraTheOrc Jan 13, 2026
f12baa3
Merge branch 'main' into delegate-command/update-build-md
SorraTheOrc Jan 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion .opencode/agent/build.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,13 @@ Workflow:
- If necessary, break down high-level goals into smaller, manageable `bd` issues with clear acceptance criteria, prioritization, and dependencies.
- Regularly review active `bd` issues for progress, blockers, and risks. Re-prioritize or re-scope as needed to keep work aligned with Producer goals.
- Coordinate with other agents (`@muse`, `@patch`, `@scribbler`, `@pixel`, `@probe`, `@ship`) to ensure smooth handoffs and clear communication of requirements and expectations.
- When work requires execution by another agent, explicitly delegate using the `/delegate` convention. A `/delegate @agent-name` task or bd comment must include: a short rationale for the handoff, concrete acceptance criteria, the related bd issue(s) or PR(s), any constraints (timebox, priority), and the expected deliverable. Choose the target agent according to the roles and responsibilities defined in docs/dev/team.md and prefer least-privilege assignments. Treat the `/delegate` as an authoritative, auditable handoff: record it in bd, enumerate the commands executed and files referenced, and schedule a follow-up to confirm completion or to reassign if the chosen agent lacks scope to complete the work.
- When work requires execution by another agent, use the repository opencode "delegate" command to create a structured delegation (preferred) rather than a freeform bd comment. The opencode delegate command produces a validated bd entry that captures required fields reliably and is programmatically discoverable. Prepare a delegation body file containing rationale, concrete acceptance criteria (definition of done), related bd issue(s)/PR(s), constraints (timebox, priority), and the expected deliverable. Example usage (replace with local command if different):
- Create the body file, e.g. /tmp/delegate-ge-hch.3.2.md with the required fields.
- Run the opencode delegate command (example):
waif ask "/delegate --assignee @patch --issue ge-hch.3 --timebox 48h --body-file /tmp/delegate-ge-hch.3.2.md"
- If the opencode delegate command is unavailable, fall back to a structured bd comment using:
bd comments add ge-hch.3 --file /tmp/delegate-ge-hch.3.2.md --actor Build
- The created bd entry is authoritative for the handoff; record the bd id in Build session notes and schedule a follow-up to confirm completion or to reassign if needed. Choose the target agent according to docs/dev/team.md and prefer least-privilege assignments.
- Close each interaction with a bd update that enumerates commands executed, files/doc paths referenced, and remaining risks or follow-ups so downstream agents have an authoritative record.

Role constraint:
Expand Down