wu:create
wu:create
Section titled “wu:create”Create new WU spec
Invalid authoring input is reported once in stable order before any create transaction starts. The report includes every independently detectable field, sizing, test-policy, exposure-verification, and acceptance-scope issue, with one remediation per finding. Checks that depend on a missing prerequisite are deferred. A failed report exits nonzero without creating a micro-worktree, WU file, commit, remote update, backlog change, or initiative link.
Options:
| Flag | Description | Required |
|---|---|---|
-i, --id <wuId> | Work Unit ID (e.g., WU-123). If not provided, auto-generates next sequential ID. | No |
-l, --lane <lane> | Lane name (required for creation; e.g., “Operations: Tooling”) | Yes |
-t, --title <title> | Work Unit title (required for creation) | Yes |
-p, --priority <priority> | Priority level (P0, P1, P2, P3) | No |
--type <type> | WU type (feature, bug, documentation, process, tooling, chore, refactor) | No |
--initiative <ref> | Parent initiative (INIT-XXX or slug) | No |
--initiative-phase <number> | Canonical initiative_phase number within parent initiative | No |
--blocked-by <wuIds> | WU IDs that block this WU (repeatable) | No |
--blocks <wuIds> | WU IDs this WU blocks (repeatable) | No |
--labels <labels> | Labels (repeatable) | No |
--assigned-to <email> | Override assigned_to (defaults to git config user.email) | No |
--description <text> | Required WU description (Context/Problem/Solution) | No |
--acceptance <criterion> | Acceptance criterion (required for creation; repeatable, use multiple times) | No |
--notes <text> | Implementation notes or context (required for creation) | No |
--code-paths <paths> | Code paths (required for non-documentation/process WUs; repeatable) | No |
--test-paths-manual <tests> | Manual verification (required for non-documentation/process WUs unless configured test policy waives evidence; repeatable) | No |
--test-paths-unit <paths> | Unit test file paths (repeatable) | No |
--test-paths-e2e <paths> | E2E test file paths (repeatable) | No |
--validate | Validate spec completeness (requires description, acceptance, test paths) | No |
--spec-refs <paths> | Spec/plan references (required for feature WUs unless —plan is supplied; repeatable or comma-separated) | No |
--exposure <type> | Exposure level (required for creation: ui, api, backend-only, documentation; UI exposure requires accessibility evidence) | No |
--user-journey <text> | User journey description (recommended for ui/api exposure) | No |
--ui-pairing-wus <wuIds> | UI WU IDs that consume this API (repeatable or comma-separated, for api exposure) | No |
--plan | Create plan template in the repo plansDir (legacy LUMENFLOW_HOME/plans still resolve) | No |
--estimated-files <count> | Estimated artifacts modified by the WU (all-or-none sizing tuple when any sizing option is supplied; non-negative integer; exclude audit read coverage) | No |
--estimated-tool-calls <count> | Estimated tool calls for the whole WU (required in the sizing tuple; non-negative integer; the per-session checkpoint rule still applies) | No |
--sizing-strategy <strategy> | Executable sizing strategy (required in the sizing tuple: single-session, checkpoint-resume, orchestrator-worker; decomposition is plan-only) | No |
--sizing-exception-type <type> | Optional bounded sizing exception (docs-only, shallow-multi-file, review-audit); WU type, paths, and strategy must qualify | No |
--sizing-exception-reason <text> | Required with an exception type; for review-audit, record modified outputs here and read coverage separately | No |
--no-strict | Bypass code_paths/test_paths path existence checks. Reality-phase checks run at wu:prep/wu:done. Logged when used. | No |
--cloud | Use cloud/branch-pr mode (no worktree, PR-based completion for cloud agents and MCP callers) | No |
--offline | Skip remote fetch during ID generation (air-gapped/offline mode) | No |