jira-daily-pm-radar

Jira Daily PM Radar

This skill answers daily PM questions:

1. What changed since yesterday?
2. Where is the current sprint stuck?
3. Who may have forgotten to move/update issues?
4. What in the next sprint is not ready?
5. What in the backlog smells?
6. What should the PM do today?

Prerequisites

Only uv is required. Install it once:

• Linux/macOS: curl -LsSf https://astral.sh/uv/install.sh | sh
• Windows: powershell -c "irm https://astral.sh/uv/install.ps1 | iex"

Verify: uv --version

Running CLI

Run directly via uvx - no clone needed:

# Daily report (mock mode, no real Jira needed)
uvx --from git+https://github.com/letya999/jira-daily-pm-radar.git \
  jira-radar daily --project DEMO --mock --out reports/

# Daily report (real Jira)
uvx --from git+https://github.com/letya999/jira-daily-pm-radar.git \
  jira-radar daily --project PROJ --board-id 123 --since yesterday --out reports/

# Check connectivity
uvx --from git+https://github.com/letya999/jira-daily-pm-radar.git \
  jira-radar doctor

Environment variables (set before calling or pass via shell):

• JIRA_BASE_URL - https://your-domain.atlassian.net
• JIRA_EMAIL - your Atlassian email
• JIRA_API_TOKEN - your Jira API token

MCP client config

{
  "mcpServers": {
    "jira-daily-pm-radar": {
      "command": "uvx",
      "args": [
        "--from", "git+https://github.com/letya999/jira-daily-pm-radar.git[mcp]",
        "jira-radar-mcp"
      ],
      "env": {
        "JIRA_BASE_URL": "<YOUR_JIRA_URL>",
        "JIRA_EMAIL": "<YOUR_JIRA_EMAIL>",
        "JIRA_API_TOKEN": "<YOUR_JIRA_API_TOKEN>"
      }
    }
  }
}

First run downloads and caches the package. Subsequent runs use the cache.

Installing this skill

npx skills add -g letya999/jira-daily-pm-radar

After install, ensure uv is available (see Prerequisites). No other setup required.

Recommended operator flow

1. daily_report(...) to generate a batch report and get the summary.
2. sprint_report(...) or backlog_report(...) for focused checks.
3. issue_context(...) to drill down into a specific issue's history and comments.
4. search_issues(...) for custom JQL queries if standard reports are insufficient.