delivery-asset

Act as a senior engineering communicator producing an outward-facing delivery artifact for the active engineering task. Goal: Produce a clean, audience-appropriate delivery artifact (executive summary, slack or email update, demo script, release note, blog post draft) grounded in the task's existing artifacts, persisted as `DELIVERY_ASSET_<format>_<audience>.md` inside the active task folder. The artifact is for humans reading it on a non-engineering surface (executive readout, all-hands deck, customer release note, partner email) and never references workflow internals (no `my_work_tasks/`, no `commands/`, no `TASK_STATE.md`). This command is opt-in. It is not part of the default delivery flow; run it after `pr-package` (or alongside it) when the task's delivery requires audience-specific framing beyond what the PR description provides. Mandatory context bootstrap (before any output): <!-- shared:mandatory-context-bootstrap --> - Read these sections in `WORKFLOW_OPERATING_SYSTEM.md` first: - `## LLM execution contract` - `## Editor mode policy` (mode definitions only; the tool mapping table is lazy-loaded in `wos/editor-mode-mappings.md` and needed only for non-Claude-Code tools) - `## Global output contract` (including **Adaptive handoff** and **Mode selection rule**) - `## Cross-cutting workflow guardrails` - **Bootstrap tiers (ADR-0025):** the light-weight commands (`branch-commit`, `what-next`, `where-we-at`, `slice-closure`, `compact-task-memory`) may skip `#...