---
name: workorder
description: Generate numbered work-order documents (WO-NNN) for a goal or program of work — the BlockNinja works/ convention with phases, dependencies, task checklists, acceptance criteria, and evidence requirements. Use when the user asks for work orders, a WO set, or to break a spec/goal into trackable execution units.
---

# Work Order Generator

Produce work-order markdown files matching the established convention (see `sites/bidmasters/docs/works/` for canon). One WO per coherent unit of work; a program is a numbered series.

## Process

1. **Locate context**: find the governing spec (`docs/superpowers/specs/`) and any existing `works/` directory. Continue the existing WO numbering (`ls works/ | sort` — next number). If no works/ dir exists, ask where to put it (default: `docs/works/`).
2. **Decompose the goal** into WOs sized so each is independently completable and verifiable. Order by dependency; assign phases.
3. **Write each WO** using the exact format below.
4. **Update or create `works/README.md`** index: table of WO number, title, phase, status, dependencies.
5. Commit the documents (house rule: plan/work docs are always committed, never left untracked).

## WO Format (exact)

```markdown
# WO-NNN: <Title>

**Phase:** <N>
**Status:** TODO | IN PROGRESS | BLOCKED | DONE
**Spec:** [<relative link>](<relative link>)
**Repos:** <repo names touched>
**Depends on:** <WO-NNN list or "—">

## Overview

<2-4 sentences: what this delivers and why. Name the user-visible outcome.>

## Tasks

### <Subsystem / file-area heading>

- [ ] <concrete task with file paths where known>
- [ ] <...>

### <Next subsystem>

- [ ] <...>

## Acceptance Criteria

- [ ] <observable behavior, stated so a reviewer can check it without reading code>
- [ ] <...>

## Evidence Required

- <exact command(s) to run and the expected output — build, test, check-safety, curl, screenshot>
- <runtime proof required before Status may be set to DONE; "verified" means evidence captured in the WO or commit message, not asserted>
```

## Rules

- Tasks reference real file paths (verify they exist; mark new files "(new)").
- Every WO ends with check-safety in Evidence Required when it touches cms, plugins/*, sites/*, or themes/* (mandated gate).
- Acceptance criteria are behaviors, not task restatements.
- Status changes to DONE only with evidence captured — claims without runtime proof stay IN PROGRESS.
- Keep WOs small enough that one agent session can complete one WO with margin.