write_task
Create a new task file with YAML frontmatter and markdown body for team coordination. Place tasks in the project's inbox for the recipient to claim.
Instructions
Create a new task file (v3: _lifecycle/inbox/; v2: fcop/tasks/).
The library assigns a filename of the form
TASK-YYYYMMDD-NNN-{SENDER}-to-{RECIPIENT}.md and writes a
FCoP-compliant YAML frontmatter + markdown body.
In a v3 project the task is placed in _lifecycle/inbox/ so the
recipient can claim_task it.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sender | Yes | Sender role code (uppercase). | |
| recipient | Yes | Recipient role code (uppercase). May use the slot form ``ROLE.D1`` for per-slot targeting or ``TEAM`` for broadcast. | |
| subject | Yes | One-line subject written to the ``subject:`` frontmatter field. | |
| body | Yes | Task body in Markdown. | |
| priority | No | FCoP priority. Accepts ``P0`` / ``P1`` / ``P2`` / ``P3`` (canonical) or the legacy aliases ``urgent`` / ``high`` / ``normal`` / ``low``. Default: ``P2``. | P2 |
| thread_key | No | Optional thread identifier for linking this task to an ongoing conversation. | |
| references | No | Comma-separated task filenames this task refers back to (for ``references:`` frontmatter field). | |
| risk_level | No | Operation risk level (per ADR-0024). One of ``low`` / ``medium`` / ``high`` / ``irreversible``. Default: ``medium``. ``high`` and ``irreversible`` will automatically require a ``needs_human`` review gate. Leave empty to accept the default (``medium``). |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |