Plan and track work in chat
Juscribe is a shared board for planning and tracking a team's work. Tickets move from the Icebox and the Backlog into Current and on to Done, and everyone on the board sees each change as it happens. More
MCP connector Server URL https://mcp.juscribe.ai/mcpCopy Login OAuth Tools Reads data14 get_ get_ get_ get_ get_ list_ list_ list_ list_ list_ list_ list_ list_ search
Changes data14 add_ add_ add_ append_ attach_ attach_ create_ create_ create_ create_ create_ move_ move_ resolve_
Deletes or can't be undone9 accept_ delete_ delete_ reject_ transition_ update_ update_ update_ update_
Skills 3 in the ChatGPT listing
Hard rules Non-negotiable behavioral guardrails for Juscribe work — every-ticket lifecycle, COMMIT-IMMEDIATELY rule, no lint/test suppression, stakeholder-verbatim ticket descriptions (agent additions kept current), no false deliveries, external blockers when waiting on user input, where a new ticket gets filed, splitting a ticket blocked on a third party, steps-as-subtasks, no `git push`, and the document-discoveries protocol. retrospective How to run a retrospective on an iteration and hand it over as a self-contained HTML report with charts, then record it back on the board. Ticket workflow The single load-bearing Juscribe SOP skill — the full ticket lifecycle from pickup to delivery, plus estimation, ticket types, labels, metadata, testing gates, and the complete `jus` CLI / API reference in bundled files this skill points at. 
Smartsheet US#68