atlassian-pm
v3.17.1Agile Jira/Confluence automation: story creation, sprint planning, quality gates, HR enforcement
By TathepLicense: MIT1 GitHub starsUpdated 6 months ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 3 skill or MCP entries
- Source updated
- Apr 19, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install atlassian-pm for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install atlassian-pm@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/wasikarn/atlassian-pmClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.
Plugin files
├── .claude-plugin/plugin.json├── skills/apm-doctor/SKILL.md├── skills/apm-setup/SKILL.md└── .mcp.json
Included Skills2
Health check for atlassian-pm environment — runs 11 checks and reports status. Checks: acli install, acli auth, uv install, atlassian-cache venv, mcp-atlassian config, project-config valid, board_id non-zero, git filters, CLAUDE.md block, run-mcp.sh launcher, board_monitor daemon (optional). Never stops on failure — shows complete picture. Run after setup or after updates. Triggers: "apm doctor", "atlassian-pm health check", "check apm setup", "diagnose atlassian", "/apm-doctor", "ตรวจสอบ apm setup" Use when: verifying plugin health and configuration after setup or after issues arise Do NOT use for: initial setup (use apm-setup); creating issues (use create-epic or create-task)
First-time setup for atlassian-pm plugin — installs dependencies, collects Jira config, creates ~/.config/atlassian/.env, authenticates acli, registers mcp-atlassian, and validates. Idempotent: detects what is already configured and skips those steps. Re-running is safe — will ask before overwriting existing config. Config-file mode: create ~/.atlassian-pm.yaml with --init, fill it in, then run setup for zero-question installation. Triggers: "setup atlassian-pm", "apm setup", "/apm-setup", "install atlassian-pm", "configure atlassian plugin" Use when: performing initial plugin setup — acli, MCP, credentials, git filters Do NOT use for: daily operation (all other skills handle that); upgrading the plugin
MCP servers1
- command
- bash
- args
- ${CLAUDE_PLUGIN_ROOT}/mcp-servers/atlassian-cache/run.sh
- env.UV_PROJECT_ENVIRONMENT
- ${CLAUDE_PLUGIN_DATA}/venv
MCP configuration uses runtime-provided plugin path placeholders such as ${PLUGIN_ROOT} or ${CLAUDE_PLUGIN_ROOT}. Review the manifest for the runtime-specific expansion rules.
Plugin manifests1
{
"name": "atlassian-pm",
"version": "3.17.1",
"description": "Agile Jira/Confluence automation: story creation, sprint planning, quality gates, HR enforcement",
"author": {
"name": "Tathep"
},
"homepage": "https://github.com/wasikarn/atlassian-pm",
"repository": "https://github.com/wasikarn/atlassian-pm",
"license": "MIT",
"keywords": [
"jira",
"confluence",
"atlassian",
"agile",
"sprint"
],
"mcpServers": "./.mcp.json",
"skills": [
"./skills/apm-setup/",
"./skills/apm-doctor/",
"./skills/epic/",
"./skills/story/",
"./skills/task/",
"./skills/sprint/",
"./skills/confluence/",
"./skills/utilities/"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[atlassian-pm on Agent Plugins Marketplace](https://pluginsmp.com/plugins/atlassian-pm)