plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "ship",
  "version": "0.13.5",
  "description": "SHIP is your autonomous software team. Assign a Linear, Jira or GitHub issue to SHIP, and its autonomous coding agents plan, build, review and test the change in your own GitHub repository. A mission works toward a pull request. Your CI, an automated code review and a test of its acceptance criteria each gate it.\n\nHand work to SHIP from the assistant you already use. File a mission from an issue in your tracker, or from a title and a description. Follow the mission through its stages, and read its verdicts, cost and session logs. Send an instruction to the agent that runs next, or leave a note for it. Read the proof that a run produced, such as test traces and screenshots.\n\nSHIP runs agentic development as a headless AI software factory, so no screen has to be in the loop. You operate the whole mission from your coding agent, your AI assistant, your tracker or your terminal. A Planner, a Builder, a Reviewer and a Tester each do one stage of the agentic SDLC. They follow the agentic engineering practices in your repository, such as its agent instructions and skills. Your CI and a preview deploy are gates between the roles, and work that fails a gate goes back to the Builder with the reason.\n\nSchedule maintenance missions, such as a weekly dependency upgrade. Manage the preview environments of your pull requests and the MCP servers that your agents use.\n\nSign in with OAuth, or send a SHIP personal access token. A token that you bind to one project can reach only the missions of that project.\n\nYou need a SHIP account and a connected GitHub repository. Create an account at https://letsship.ai.",
  "author": {
    "name": "SHIP",
    "email": "support@letsship.ai",
    "url": "https://letsship.ai"
  },
  "homepage": "https://letsship.ai/docs/mcp",
  "repository": "https://github.com/letsship/skills",
  "license": "MIT",
  "keywords": [
    "coding-agents",
    "code-review",
    "agentic-coding",
    "agentic-testing",
    "pull-requests",
    "linear",
    "jira",
    "github-issues",
    "agentic-sdlc",
    "headless",
    "ship",
    "automated-code-review",
    "ai-sdlc",
    "ai-software-factory",
    "headless-software-factory",
    "delegate"
  ],
  "extensions": {
    "com.openai": {
      "interface": {
        "displayName": "SHIP",
        "shortDescription": "Agentic coding for your SDLC",
        "longDescription": "SHIP is your autonomous software team. Assign a Linear, Jira or GitHub issue to SHIP, and its autonomous coding agents plan, build, review and test the change in your own GitHub repository. A mission works toward a pull request. Your CI, an automated code review and a test of its acceptance criteria each gate it.\n\nHand work to SHIP from the assistant you already use. File a mission from an issue in your tracker, or from a title and a description. Follow the mission through its stages, and read its verdicts, cost and session logs. Send an instruction to the agent that runs next, or leave a note for it. Read the proof that a run produced, such as test traces and screenshots.\n\nSHIP runs agentic development as a headless AI software factory, so no screen has to be in the loop. You operate the whole mission from your coding agent, your AI assistant, your tracker or your terminal. A Planner, a Builder, a Reviewer and a Tester each do one stage of the agentic SDLC. They follow the agentic engineering practices in your repository, such as its agent instructions and skills. Your CI and a preview deploy are gates between the roles, and work that fails a gate goes back to the Builder with the reason.\n\nSchedule maintenance missions, such as a weekly dependency upgrade. Manage the preview environments of your pull requests and the MCP servers that your agents use.\n\nSign in with OAuth, or send a SHIP personal access token. A token that you bind to one project can reach only the missions of that project.\n\nYou need a SHIP account and a connected GitHub repository. Create an account at https://letsship.ai.",
        "developerName": "SHIP",
        "category": "Developer Tools",
        "capabilities": [
          "File a mission from an issue or a description",
          "Follow a mission through plan, build, review and test",
          "Send instructions to the agent that runs next",
          "Read test traces, screenshots and session logs",
          "Schedule maintenance missions"
        ],
        "websiteURL": "https://letsship.ai",
        "supportURL": "https://letsship.ai/support",
        "privacyPolicyURL": "https://letsship.ai/privacy",
        "termsOfServiceURL": "https://letsship.ai/terms",
        "defaultPrompt": [
          "Which SHIP projects can you reach, and what stage is each open mission in?",
          "Assign SHIP-412 to SHIP. Tell me when its pull request passes CI, review and tests.",
          "Turn the plan we just wrote into a SHIP mission that starts at the Builder."
        ],
        "brandColor": "#e84826",
        "brandColorDark": "#f26d4a",
        "composerIcon": "./assets/ship.png",
        "logo": "./assets/ship.png"
      },
      "review": {
        "test_cases": {
          "positive": [
            {
              "description": "List the projects that the token can reach.",
              "prompt": "List my SHIP projects.",
              "tools_triggered": "list_projects",
              "expected_behavior": "Returns the demo project with its repository name."
            },
            {
              "description": "File a new mission from a description, with acceptance criteria.",
              "prompt": "File a SHIP mission in the demo project to fix the typo on the pricing page.",
              "tools_triggered": "list_projects, create_mission",
              "expected_behavior": "Creates an issue and a mission, and returns the issue id and its link."
            },
            {
              "description": "Read the state of a mission.",
              "prompt": "What stage is the last mission in, and what did the Reviewer say?",
              "tools_triggered": "inspect_mission",
              "expected_behavior": "Returns the current stage and the latest review verdict of the mission."
            },
            {
              "description": "Send review feedback to the agent that runs next.",
              "prompt": "Tell the Builder on that mission to keep the old route and add the new one beside it.",
              "tools_triggered": "send_mission_instruction",
              "expected_behavior": "Returns a receipt that says what SHIP recorded and what the instruction will start."
            },
            {
              "description": "Read the proof that a QA run produced.",
              "prompt": "Show the proof from the last QA run.",
              "tools_triggered": "list_artifacts, get_artifact",
              "expected_behavior": "Lists the test trace and screenshots of the run, each with a link."
            }
          ],
          "negative": [
            {
              "description": "A travel request has nothing to do with SHIP.",
              "prompt": "Book a flight to Berlin."
            },
            {
              "description": "SHIP has no tool that deletes a repository.",
              "prompt": "Delete my GitHub repository."
            },
            {
              "description": "A weather question has nothing to do with SHIP.",
              "prompt": "What is the weather tomorrow?"
            }
          ]
        },
        "demo_recording_url": "https://videos.letsship.ai/marketing/ship-intro.58beca97.mp4",
        "commerce": false
      },
      "apps": "./.app.json"
    }
  }
}