finesse-linear

Finesse Linear — Issue-Driven Planning

Fetch a Linear issue via MCP and delegate to /finesse or /finesse-mini with a structured task description. This is a lightweight wrapper — all planning logic lives in the delegated command.

Argument Parsing

Parse $ARGUMENTS:

1. Extract flags first:

   • --max-refinements N — store N, remove from arguments. Passed through to /finesse.
   • --mini — store as boolean, remove from arguments. Delegates to /finesse-mini instead of /finesse.

2. Extract issue identifier from remaining arguments:

   • If the argument is a URL containing issue/([A-Z]+-[0-9]+), extract the issue ID from the match.
   • If the argument matches [A-Z]+-[0-9]+ directly, use it as the issue ID.
   • If neither pattern matches, say: "Could not parse a Linear issue ID. Provide a URL (e.g., https://linear.app/team/issue/PF-254/...) or a raw ID (e.g., PF-254)." and STOP.

3. If $ARGUMENTS is empty or blank: Ask the user for the Linear issue URL or ID using AskUserQuestion. Then parse the response as in step 2.

4. If multiple issue-like arguments are present: Use the first one. Say: "Multiple issues detected — using [ID]. Run /finesse-linear separately for each issue."

Step 1: Fetch Issue Data

Call the MCP tool mcp__linear-server__get_issue with the extracted issue ID.

If the MCP tool is unavailable

If the tool call fails because the MCP server is not configured or the tool is not found, display:

---

Linear MCP Server Not Available

/finesse-linear requires the Linear MCP server. To set it up:

1. Get a Linear API key from https://linear.app/settings/api

2. Add to your MCP configuration (.mcp.json in project root or ~/.claude/mcp.json globally):

{
  "mcpServers": {
    "linear-server": {
      "command": "npx",
      "args": ["-y", "@anthropic/linear-mcp-server"],
      "env": {
        "LINEAR_API_KEY": "your-api-key-here"
      }
    }
  }
}

1. Restart Claude Code to load the server.