From speckit-extensions
Use when the user wants to create an implementation plan from a SwaggerHub OpenAPI spec — e.g. "plan from swagger <url>", "/speckit-extensions:plan-from-swagger <url>". Fetches the OpenAPI spec via the fetch-swagger MCP server and pipes it into /speckit.plan to produce an implementation plan.
npx claudepluginhub yesmarket/claude-marketplace --plugin speckit-extensionsThis skill uses the workspace's default tool permissions.
Fetch an OpenAPI spec from SwaggerHub and use its content as context for `/speckit.plan`.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Fetch an OpenAPI spec from SwaggerHub and use its content as context for /speckit.plan.
$ARGUMENTS contains: <swaggerhub-url> [additional-input]
swaggerhub-url (required): URL to a SwaggerHub API spec, e.g. https://api.swaggerhub.com/apis/MyOrg/MyAPI/1.0.0additional-input (optional): Extra context or instructions to pass alongside the specExtract the SwaggerHub URL (first whitespace-delimited token from $ARGUMENTS) and any additional input (everything after it).
The SwaggerHub API requires an Authorization header containing the API key.
SWAGGERHUB_API_KEY is available in the environment (it is injected into the fetch-swagger MCP server process via the plugin's MCP config).Authorization header on every SwaggerHub request in this session.Using the fetch-swagger MCP server, make a GET request to the SwaggerHub URL with the following header:
Authorization: <SWAGGERHUB_API_KEY>
Request the response in JSON format (append ?format=json to the URL if a format parameter is not already present). If the server returns a resolve/dereference option (e.g. ?resolve=true), prefer using it to receive a fully-resolved spec without $ref pointers.
Format the retrieved spec into a context block:
SwaggerHub API Spec: <url>
OpenAPI Spec:
<full spec content as returned>
Append any additional input from $ARGUMENTS after the above block.
Pass the composed context block as the feature description to /speckit.plan.