Update to Juscribe

{
  "canonical_app_id": "asdk_app_6ac438d753188191b22c34d46f4d8039",
  "connector_id": "asdk_app_6ac438d753188191b22c34d46f4d8039",
  "created_at": "2026-10-06T00:59:36.819823Z",
  "discoverability": "LISTED",
  "id": "plugin_asdk_app_6ac438d753188191b22c34d46f4d8039",
  "is_template": false,
  "is_template_instance": false,
  "is_v2_template": false,
  "name": "jus",
  "release": {
    "app_ids": [
      "asdk_app_6ac438d753188191b22c34d46f4d8039"
    ],
    "app_manifest": {
      "apps": {
        "juscribe": {
          "id": "asdk_app_6ac438d753188191b22c34d46f4d8039",
          "required": true
        }
      }
    },
    "app_templates": [],
    "description": "Read and change your Juscribe board, and work its tickets the way your team does. One install brings the Juscribe connector and three skills that carry the board's rules: ticket-workflow (the ticket lifecycle, estimation, labels, testing gates and the jus API reference), hard-rules (what never to do on a board) and retrospective (reviewing an iteration).",
    "display_name": "Juscribe",
    "id": "pluginrel_8c264ad53f8c8191bb2494fb8e93d6c3",
    "interface": {
      "brand_color": null,
      "capabilities": [
        "Read",
        "Write"
      ],
      "category": "Productivity",
      "composer_icon_dark_url": null,
      "composer_icon_url": "https://files.openai.com/content?id=file_0000000022c881f687a76cfa2a73bb6c",
      "default_prompt": null,
      "default_prompts": null,
      "developer_name": "Juscribe",
      "logo_url": "https://files.openai.com/content?id=file_00000000969881f6aface8216b3519c6",
      "logo_url_dark": null,
      "long_description": "Read and change your Juscribe board, and work its tickets the way your team does. One install brings the Juscribe connector and three skills that carry the board's rules: ticket-workflow (the ticket lifecycle, estimation, labels, testing gates and the jus API reference), hard-rules (what never to do on a board) and retrospective (reviewing an iteration).",
      "plugin_category_id": "productivity",
      "privacy_policy_url": "https://juscribe.ai/privacy",
      "screenshot_urls": [],
      "short_description": "Plan and track work in chat",
      "terms_of_service_url": "https://juscribe.ai/terms",
      "website_url": "https://juscribe.ai"
    },
    "keywords": [
      "juscribe",
      "agile",
      "project-management",
      "ticket-workflow",
      "sop",
      "mcp"
    ],
    "mcp_servers": [
      {
        "key": "juscribe",
        "metadata": {
          "headers": {},
          "type": "streamable-http",
          "url": "https://mcp.juscribe.ai/mcp"
        }
      }
    ],
    "onboarding_skill_name": null,
    "requires_local_executor": false,
    "skills": [
      {
        "description": "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. Auto-invoke before committing, before editing a ticket description, before transitioning to finished/delivered, before filing or placing a new ticket, when work turns out to depend on someone outside the team, and on hitting an unfamiliar error or workaround. In a Juscribe-wired project, generic ticket and board language means Juscribe by default, unless the wording names another system (a PR, a GitHub issue, another tracker's key).",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "hard-rules",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "hierarchy",
          "short_description": "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. Auto-invoke before committing, before editing a ticket description, before transitioning to finished/delivered, before filing or placing a new ticket, when work turns out to depend on someone outside the team, and on hitting an unfamiliar error or workaround. In a Juscribe-wired project, generic ticket and board language means Juscribe by default, unless the wording names another system (a PR, a GitHub issue, another tracker's key)."
        },
        "name": "hard-rules",
        "plugin_release_skill_id": "pluginrsk_6ac44159b4508191ad392053d2191665"
      },
      {
        "description": "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. Covers what to gather (the first-hand accounts first — the ticket comments that hold most of them — then the tickets, their activity and the board's timezone), the sections a retrospective owes and the ones it must stop writing, when in the day work actually happened, production health and standing technical debt, drawing conclusions rather than counting metrics, hand-authored inline-SVG charts that need no library and no network, verifying derived numbers before you publish, sending the report's own HTML to the board so the iteration's details pane can show it, and writing the record back as an iteration comment. Auto-invoke on \"retrospective\", \"retro\", \"sprint review\", \"review the iteration\", or any request to review or summarize what an iteration delivered.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "retrospective",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "chart",
          "short_description": "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. Covers what to gather (the first-hand accounts first — the ticket comments that hold most of them — then the tickets, their activity and the board's timezone), the sections a retrospective owes and the ones it must stop writing, when in the day work actually happened, production health and standing technical debt, drawing conclusions rather than counting metrics, hand-authored inline-SVG charts that need no library and no network, verifying derived numbers before you publish, sending the report's own HTML to the board so the iteration's details pane can show it, and writing the record back as an iteration comment. Auto-invoke on \"retrospective\", \"retro\", \"sprint review\", \"review the iteration\", or any request to review or summarize what an iteration delivered."
        },
        "name": "retrospective",
        "plugin_release_skill_id": "pluginrsk_6ac44159e31c8191a6e447172371ba50"
      },
      {
        "description": "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. Use when working any ticket — picking one up, transitioning state, investigating, sizing, labeling, writing tests, running pre-commit gates, calling `jus api`, committing, self-reviewing, finishing, delivering, handling rejections, processing batches, or resolving dependency blockers. Auto-invoke whenever a ticket ID (`#N`) or \"work on this ticket\" / \"pick up backlog\" / \"deliver\" / \"rejected\" appears. In a project wired to Juscribe (a `.jus/` directory or the `jus` CLI), bare ticket language — `#42`, the board, the backlog, deliver — means Juscribe tickets by default, unless the wording names another system (a PR, a GitHub issue, another tracker's key), so this skill is the one to invoke for them.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "ticket-workflow",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "hierarchy",
          "short_description": "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. Use when working any ticket — picking one up, transitioning state, investigating, sizing, labeling, writing tests, running pre-commit gates, calling `jus api`, committing, self-reviewing, finishing, delivering, handling rejections, processing batches, or resolving dependency blockers. Auto-invoke whenever a ticket ID (`#N`) or \"work on this ticket\" / \"pick up backlog\" / \"deliver\" / \"rejected\" appears. In a project wired to Juscribe (a `.jus/` directory or the `jus` CLI), bare ticket language — `#42`, the board, the backlog, deliver — means Juscribe tickets by default, unless the wording names another system (a PR, a GitHub issue, another tracker's key), so this skill is the one to invoke for them."
        },
        "name": "ticket-workflow",
        "plugin_release_skill_id": "pluginrsk_6ac44159b37881918de3c6ed3cddd881"
      }
    ],
    "version": "1.4.50"
  },
  "scope": "GLOBAL",
  "share_url": "https://chatgpt.com/plugins/plugin_asdk_app_6ac438d753188191b22c34d46f4d8039?open_in_app",
  "status": "ENABLED"
}