Customaize Agent Create Workflow Command

Key Principles

1. Context Isolation

Each subagent gets its own isolated context window. The main orchestrator stays lean while subagents load detailed instructions from files.

2. Subagent Capabilities

Subagents invoked via Task tool or @mention:

3. File Reference Pattern

Use .opencode/commands/ for portable paths:

Read .opencode/commands/step-1-workflow-name.md and execute.

Subagent will use Read tool to fetch the file content.

Implementation Process

Step 1: Gather Requirements

Ask user (if not provided):

1. Workflow name: kebab-case identifier (e.g., feature-implementation)
2. Description: What the workflow accomplishes
3. Steps: List of discrete steps with:
   • Step name
   • Step goal
   • Required tools
   • Expected output
4. Execution mode: Sequential or parallel steps
5. Agent type: general-purpose or custom agent

Step 2: Create Directory Structure

# Create commands directory (if it doesn't exist)
mkdir -p .opencode/commands

# Optional: Create agents directory (if using custom agents)
mkdir -p .opencode/agents

Note: All task files (both workflow-specific steps and shared context) are placed directly in commands/ without subdirectories.

Step 3: Create Task Files

For each step, create a task file with this structure:

# Step N: <Step Name>

## Context
You are executing step N of the <workflow-name> workflow.

## Goal
<Clear, specific goal for this step>

## Input
<What this step receives from previous steps or user>

## Instructions
1. <Specific action>
2. <Specific action>
3. <Specific action>

## Constraints
- <Limitation or boundary>
- <What NOT to do>

## Expected Output
<What to return to orchestrator>

## Success Criteria
- [ ] <Measurable outcome>
- [ ] <Measurable outcome>

Step 4: Create Orchestrator Command

Create the main command file with this pattern:

---