Skip to main content

chainmail item create

Create a work item; a task with no --parent goes to the inbox

Usage​

chainmail item create <type> <title> [flags]

Examples​

# a task in the inbox, to sort later
chainmail item create task "Renew the domain" --area work --due 2026-11-20
# a chore under the work Admin initiative, with acceptance criteria
chainmail item create task "File the expense report" --parent it_admin_work --criterion "Receipts attached" --criterion "Submitted"
chainmail item create feature "Search by item" --parent it_01jcb7m2k9r8q3v4w5x6y7z8b0 --description-file spec.md

Flags​

      --area string               work or personal; required with no --parent, inherited otherwise
      --criterion stringArray     an acceptance criterion (repeatable, kept in order)
      --description string        the description, as Markdown
      --description-file string   read the description from this file
      --due string                the due date, YYYY-MM-DD
      --estimate float            the estimate, a number in a unit of your choosing such as days
      --idempotency-key string    a key that makes a retry return the first item instead of making a second
      --parent string             the parent item's ID (default: none, and a task then goes to the inbox)
      --priority string           p0 to p3 (default: the parent's, or p2 with no parent)
      --start string              the start date, YYYY-MM-DD
      --state string              backlog, in-progress, in-review or done (default backlog)

Global flags​

      --output string   output format: json or table (default $CHAINMAIL_OUTPUT, then cli.toml, then table on a terminal, json otherwise)
      --socket string   daemon socket (default $CHAINMAIL_SOCKET, then cli.toml, then /run/chainmail/chainmail.sock)

See also​