Workflows
<objective> Follow established SOPs before executing repo-specific procedures. Capture repeatable processes as workflows for future reuse. </objective> <procedure name="before-repo-work">Before Executing Repo-Specific Procedures
- •Check
<available_workflows>in the system prompt - •If a matching workflow exists, call
workflowswith that name - •Follow the returned procedure step-by-step
- •If you must adapt steps, explain why the deviation is safe
After Completing a Reusable Process
- •Identify if the process could be repeated (deployments, migrations, releases, etc.)
- •Structure what you learned:
- •Prerequisites: What must be true before starting
- •Steps: Numbered, with exact commands
- •Verification: How to confirm success
- •Troubleshooting: What can fail and how to recover
- •Call
workflows_createwith:- •
name: Descriptive identifier - •
description: 5-10 word summary - •
body: Markdown with the structured content above
- •
When a Workflow Doesn't Match Reality
If a loaded workflow doesn't match your experience or you discover a new edge case:
- •Read the workflow file at
.opencode/workflows/<name>/WORKFLOW.md - •Use the Edit tool to surgically update the workflow:
- •Add missing steps or prerequisites
- •Correct inaccurate commands or outputs
- •Document the new edge case in Troubleshooting
- •Keep changes minimal and focused on what you learned
Do NOT create duplicate workflows. Always update the existing one.
</procedure> <rules>- •MUST check
<available_workflows>before repo-specific procedures - •MUST load workflow when a matching entry exists
- •MUST create workflow after completing a reusable process
- •MUST use Edit tool on
.opencode/workflows/*/WORKFLOW.mdto correct inaccuracies or add edge cases - •MUST update existing workflows rather than creating variants
- •SHOULD include exact commands and expected outputs in steps
- •SHOULD document failure scenarios and recovery steps
- •MAY add workflow references to nested
AGENTS.mdfor directory-specific suggestions