By yesmarket
Configures MCP servers, plugins, and skills for an AI-assisted spec-driven development workflow. Includes context-gathering skills that query external systems like Jira, Confluence, Figma, and others to drive wrapped speckit commands.
npx claudepluginhub yesmarket/claude-marketplace --plugin speckit-extensionsUse when the user wants to build a project constitution from a Confluence page hierarchy — e.g. "constitution from confluence <url>", "/speckit-extensions:constitution-from-confluence <url>". Fetches the page and all child pages via the Atlassian MCP server and feeds each page's content individually into /speckit.constitution.
Use when the user wants to create an implementation plan from a Confluence page — e.g. "plan from confluence <url>", "/speckit-extensions:plan-from-confluence <url>". Fetches the page and all child pages via the Atlassian MCP server and feeds each page's content individually into /speckit.plan.
Use when the user wants to create an implementation plan from a Lucidchart diagram — e.g. "plan from lucid <url>", "/speckit-extensions:plan-from-lucid <url>". Fetches the diagram via the Lucidchart MCP server and pipes it into /speckit.plan to produce an implementation plan.
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.
Use when the user wants to create a feature spec from a Jira ticket — e.g. "specify from jira PROJ-123", "/speckit-extensions:specify-from-jira PROJ-123", or "write a spec for <ticket>". Queries the Jira ticket via the Atlassian MCP server and pipes the ticket context into /speckit.specify to produce a feature spec.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Works with Claude Code, Kiro, Clawd CLI, Gemini CLI, Cursor, Continue, Hermes, and 17+ AI coding assistants. Now with Arabic, German, Spanish, and Chinese (Simplified & Traditional) support.
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Meta-prompting and spec-driven development system for Claude Code. Productivity framework for structured AI-assisted development.
Permanent coding companion for Claude Code — survives any update. MCP-based terminal pet with ASCII art, stats, reactions, and personality.
External network access
Connects to servers outside your machine
Requires secrets
Needs API keys or credentials to function
Share bugs, ideas, or general feedback.
A Claude Code plugin for AI-assisted spec-driven development. Provides skills that gather context from external systems such as Jira, Confluence, Figma, and others, and pipes it into speckit commands to drive spec driven development workflows.
1. Add the marketplace
claude plugin marketplace add yesmarket/claude-marketplace
This adds the yesmarket/claude-marketplace as a source for plugin installation.
2. Install the plugin
claude plugin install speckit-extensions@yesmarket/claude-marketplace
This plugin bundles the following MCP servers directly — no separate dependency installation required:
Why bundle MCP servers directly? At the time of writing, Claude Code does not auto-install plugin dependencies, so declaring an Atlassian plugin dependency would require users to install it manually. Bundling the MCP server directly keeps installation to a single step. If plugin dependency auto-installation is supported in a future release, this plugin may switch to declaring dependencies instead.
Note: If you also have the official Atlassian plugin installed, there are no conflicts. Claude Code handles duplicate MCP server registrations gracefully.
constitution-from-confluenceFetches a Confluence page and its full child hierarchy, feeding each page individually into /speckit.constitution.
/speckit-extensions:constitution-from-confluence <confluence-url> [additional-input]
Arguments:
| Argument | Required | Description |
|---|---|---|
confluence-url | Yes | URL to a Confluence page, e.g. https://mycompany.atlassian.net/wiki/spaces/PROJ/pages/123456789/Page+Title |
additional-input | No | Extra context or instructions passed as a separate invocation of /speckit.constitution |
Example:
/speckit-extensions:constitution-from-confluence https://mycompany.atlassian.net/wiki/spaces/PROJ/pages/123456789/Home
/speckit-extensions:constitution-from-confluence https://mycompany.atlassian.net/wiki/spaces/PROJ/pages/123456789/Home focus on the authentication domain
The skill parses the space key and page ID from the URL, recursively fetches all descendant pages depth-first via the Atlassian MCP server, and invokes /speckit.constitution once per page. If additional input is provided, it is passed as a final separate invocation.
Authentication: The Atlassian MCP server requires authentication with your Atlassian account.
specify-from-jiraFetches a Jira ticket and uses it as context for /speckit.specify.
/speckit-extensions:specify-from-jira <jira-ticket-id> [additional-input]
Arguments:
| Argument | Required | Description |
|---|---|---|
jira-ticket-id | Yes | Jira issue key, e.g. PROJ-123 |
additional-input | No | Extra context or instructions to include alongside the ticket |
Example:
/speckit-extensions:specify-from-jira PROJ-123
/speckit-extensions:specify-from-jira PROJ-123 focus on the mobile experience
plan-from-confluenceFetches a Confluence page and its full child hierarchy, feeding each page individually into /speckit.plan.
/speckit-extensions:plan-from-confluence <confluence-url> [additional-input]
Arguments:
| Argument | Required | Description |
|---|---|---|
confluence-url | Yes | URL to a Confluence page, e.g. https://mycompany.atlassian.net/wiki/spaces/PROJ/pages/123456789/Page+Title |
additional-input | No | Extra context or instructions passed as a separate invocation of /speckit.plan |
Example:
/speckit-extensions:plan-from-confluence https://mycompany.atlassian.net/wiki/spaces/PROJ/pages/123456789/HLD
/speckit-extensions:plan-from-confluence https://mycompany.atlassian.net/wiki/spaces/PROJ/pages/123456789/HLD focus on the data access layer
The skill parses the space key and page ID from the URL, recursively fetches all descendant pages depth-first via the Atlassian MCP server, and invokes /speckit.plan once per page. If additional input is provided, it is passed as a final separate invocation.
Authentication: The Atlassian MCP server requires authentication with your Atlassian account.
plan-from-lucidFetches a Lucidchart diagram page and uses it as context for /speckit.plan.
/speckit-extensions:plan-from-lucid <lucid-url> [additional-input]
Arguments:
| Argument | Required | Description |
|---|---|---|
lucid-url | Yes | URL to a Lucidchart document page, including the page query parameter |
additional-input | No | Extra context or instructions to include alongside the diagram |
Example:
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claim