Skip to content

All Tools

Lifecycle, discovery, collaboration. Filter by category, search by keyword, click any card to expand its full schema.

  • Create a new ticket. Always lands in backlog (s=bk).

  • Fetch a single ticket with full relations (comments, links, child IDs).

  • Atomically take ownership. Moves bk/td/bl → ip.

  • Update any field. Always supply etag when working with concurrent agents.

  • Soft-delete. Sets archived_at. Excluded from all queries.

  • Filter tickets across any combination of fields. Ordered by created_at DESC.

  • Priority-ordered view of bk tickets. Use this to decide what to do next.

  • Kanban snapshot grouped by status.

  • Full-text search across title, description, labels via SQLite FTS5.

  • List children of a ticket, sorted by exec_order.

  • Mermaid flowchart of ticket hierarchy with status colors.

  • Append a note to a ticket.

  • Create a directional relationship between two tickets.

flowchart TB
    subgraph "Lifecycle"
        A[ticket_create]
        B[ticket_get]
        C[ticket_claim]
        D[ticket_update]
        E[ticket_archive]
    end
    subgraph "Discovery"
        F[ticket_list]
        G[ticket_backlog]
        H[ticket_board]
        I[ticket_search]
        J[ticket_children]
        K[ticket_diagram]
    end
    subgraph "Collaboration"
        L[ticket_comment]
        M[ticket_link]
    end
ToolRequiredReturnsWhen
ticket_createtitleT{...}Adding new work
ticket_getidT{...} (with cmt, lnk, ch)Reading a single ticket
ticket_claimidT{s:ip,...} (atomic)Taking ownership
ticket_updateidT{...}Changing any field (always send etag)
ticket_archiveid{ok:true}Hiding finished work
ToolReturnsBest for
ticket_list[T{...}]Filtered queries (status, type, labels)
ticket_backlog[T{...}] priority-orderedStart here. “What should I work on?”
ticket_boardBOARD{bk:[],ip:[],...}Kanban snapshot
ticket_search[T{...}] rankedFTS5 keyword search
ticket_children[T{...}]Listing subtasks of a parent
ticket_diagramMermaid flowchartVisualizing a hierarchy
ToolRequiredReturns
ticket_commentid, bodyT{...} (updated ticket)
ticket_linkfrom_id, to_id, link_type{ok:true}

link_type is blk (blocks), rel (relates), or dup (duplicates).