WO Structured Format
Benchmarked against: Anthropic — Structured outputs Tools:
create_work_order,get_work_order_formVersion: WO System v4.0
Every Work Order follows a structured format with required fields, naming conventions, and validation rules. This ensures consistency across all agents and ships.
WO form template
create_work_order(
title="[Project-Category] Descriptive title", # Required
assignee="Mac CLI 小克", # Required — exact identity
project="SS1", # Required
description="Detailed work description...", # Recommended
priority="medium", # high / medium / low
requester="夏哥", # Default: 夏哥
due_date="2026-03-10", # YYYY-MM-DD
estimated_hours=2.0, # Estimated effort
acceptance_criteria="What defines completion", # When is this done?
deliverables="Expected outputs", # What's produced
tags='["docs", "engines"]', # JSON array string
notes="Additional context" # Free text
)
Field reference
| Field | Required | Type | Description |
|---|---|---|---|
title | Yes | String | Must start with [Project-Category] prefix |
assignee | Yes | String | Must be an exact valid agent identity |
project | Yes | String | Project code (SS1, catmints-cafe, etc.) |
description | No | String | Detailed work instructions |
priority | No | Enum | high / medium (default) / low |
requester | No | String | Who requested this (default: 夏哥) |
due_date | No | Date | YYYY-MM-DD format |
estimated_hours | No | Number | Estimated hours to complete |
acceptance_criteria | No | String | Definition of done |
deliverables | No | String | Expected outputs |
tags | No | JSON array | Categorization tags |
related_wo_ids | No | JSON array | Related WO IDs |
parent_wo_id | No | String | Parent WO for sub-tasks |
notes | No | String | Free text notes |
Title convention
Format: [Project-Category] Descriptive title
| Example | Project | Category |
|---|---|---|
[SS1-Operations] Deploy Cloud UB backup cron | SS1 | Operations |
[SP-Development] MTAAA P10 — Self-tuning | SP (SuperPortia) | Development |
[EGS-CodeStandards] Research code standards | EGS | CodeStandards |
[Infrastructure-Critical] Migrate dispatch worker | Infrastructure | Critical |
WO ID format
System auto-generates: WO-YYYY-MMDD-XXX
| Component | Meaning |
|---|---|
WO | Work Order prefix |
YYYY | Year |
MMDD | Month and day |
XXX | Random 3-character hex |
Example: WO-2026-0305-A7F
Valid agent identities
The assignee field must match exactly:
| Identity | Ship | Interface |
|---|---|---|
| Mac App 小克 | SS1 | Desktop App |
| Mac CLI 小克 | SS1 | Claude Code CLI |
| Win App 小克 | SS2 | Desktop App |
| Win CLI 小克 | SS2 | Claude Code CLI |
| Mac App 小A | SS1 | Desktop App (Sonnet) |
| Mac CLI 小A | SS1 | Claude Code CLI (Sonnet) |
| Win App 小A | SS2 | Desktop App (Sonnet) |
| Win CLI 小A | SS2 | Claude Code CLI (Sonnet) |
| Web 小克 | SS3 | Cloudflare |
| 小西 | SS1 | Chat tab |
| 夏哥 | — | Captain |
| system:cron | — | Scheduled jobs |
| system:webhook | — | External triggers |
Completion requirements
When completing a WO (in_progress → review), two fields are required:
| Field | Required | Description |
|---|---|---|
completion_summary | Yes | What was done and results |
actual_hours | Yes (must be > 0) | Hours actually spent |
complete_work_order(
order_id="WO-2026-0305-A7F",
summary="Completed all 6 Engines pages with full content...",
actual_hours=1.5
)
Related pages
| Page | Relationship |
|---|---|
| WO Admin | State machine, transitions, RBAC |
| Work Order API | API reference |
| Batch Dispatch | Dispatching WOs |