/generate-status-report

name: generate-status-report
description: "Generate project status reports from Jira issues and publish to Confluence. When an agent needs to: (1) Create a status report for a project, (2) Summarize project progress or updates, (3) Generate weekly/daily reports from Jira, (4) Publish status summaries to Confluence, or (5) Analyze project blockers and completion. Queries Jira issues, categorizes by status/priority, and creates formatted reports for delivery managers and executives."

Generate Status Report

Keywords

status report, project status, weekly update, daily standup, Jira report, project summary, blockers, progress update, Confluence report, sprint report, project update, publish to Confluence, write to Confluence, post report

Automatically query Jira for project status, analyze issues, and generate formatted status reports published to Confluence.

**CRITICAL**: This skill should be **interactive**. Always clarify scope (time period, audience, Confluence destination) with the user before or after generating the report. Do not silently skip Confluence publishing—always offer it.

Workflow

Generating a status report follows these steps:

1. **Identify scope** - Determine project, time period, and target audience 2. **Query Jira** - Fetch relevant issues using JQL queries 3. **Analyze data** - Categorize issues and identify key insights 4. **Format report** - Structure content based on audience and purpose 5. **Publish to Confluence** - Create or update a page with the report

Step 1: Identify Scope

**IMPORTANT**: If the user's request is missing key information, ASK before proceeding with queries. Do not assume defaults without confirmation for Confluence publishing.

Clarify these details:

**Project identification:**

• Which Jira project key? (e.g., "PROJ", "ENG", "MKTG")
• If the user mentions a project by name but not key, search Jira to find the project key

**Time period:**

• If not specified, ask: "What time period should this report cover? (default: last 7 days)"
• Options: Weekly (7 days), Daily (24 hours), Sprint-based (2 weeks), Custom period

**Target audience:**

• If not specified, ask: "Who is this report for? (Executives/Delivery Managers, Team-level, or Daily standup)"
• **Executives/Delivery Managers**: High-level summary with key metrics and blockers
• **Team-level**: Detailed breakdown with issue-by-issue status
• **Daily standup**: Brief update on yesterday/today/blockers

**Report destination:**

• **ALWAYS ASK** if not specified: "Would you like me to publish this report to Confluence? If so, which space should I use?"
• If user says yes: Ask for space name or offer to list available spaces
• Determine: New page or update existing page?
• Ask about parent page if creating under a specific section

Step 2: Query Jira

Use the `searchJiraIssuesUsingJql` tool to fetch issues. Build JQL queries based on report needs.

Common Query Patterns

For comprehensive queries, use the `scripts/jql_builder.py` utility to programmatically build JQL strings. For quick queries, reference `references/jql-patterns.md` for examples.

**All open issues in project:**

project = "PROJECT_KEY" AND status != Done ORDER BY priority DESC, updated DESC

**Issues updated in last week:**

project = "PROJECT_KEY" AND updated >= -7d ORDER BY priority DESC

**High priority and blocked issues:**

project = "PROJECT_KEY" AND (priority IN (Highest, High) OR status = Blocked) AND status != Done ORDER BY priority DESC

**Completed in reporting period:**

project = "PROJECT_KEY" AND status = Done AND resolved >= -7d ORDER BY resolved DESC

Query Strategy

For most reports, execute multiple targeted queries rather than one large query:

1. **Completed issues**: Get recently resolved tickets 2. **In-progress issues**: Get active work items 3. **Blocked issues**: Get blockers requiring attention 4. **High priority open**: Get critical upcoming work

Use `maxResults: 100` for initial queries. If pagination is needed, use `nextPageToken` from results.

Data to Extract

For each issue, capture:

• `key` (e.g., "PROJ-123")
• `summary` (issue title)
• `status` (current state)
• `priority` (importance level)
• `assignee` (who's working on it)
• `created` / `updated` / `resolved` dates
• `description` (if needed for context on blockers)

Step 3: Analyze Data

Process the retrieved issues to identify:

**Metrics:**

• Total issues by status (Done, In Progress, Blocked, etc.)
• Completion rate (if historical data available)
• Number of high priority items
• Unassigned issue count

**Key insights:**

• Major accomplishments (recently completed high-value items)
• Critical blockers (blocked high priority issues)
• At-risk items (overdue or stuck in progress)
• Resource bottlenecks (one assignee with many issues)

**Categorization:** Group issues logically:

• By status (Done, In Progress, Blocked)
• By priority (Highest → Low)
• By assignee or team
• By component or epic (if relevant)

Step 4: Format Report

Select the appropriate template based on audience. Templates are in `references/report-templates.md`.

For Executives and Delivery Managers

Use **Executive Summary Format**:

• Brief overall status (🟢 On Track / 🟡 At Risk / 🔴 Blocked)
• Key metrics (total, completed, in progress, blocked)
• Top 3 highlights (major accomplishments)
• Critical blockers with impact
• Upcoming priorities

**Keep it concise** - 1-2 pages maximum. Focus on what matters to decision-makers.

For Team-Level Reports

Use **Detailed Technical Format**:

• Completed issues listed with keys
• In-progress issues with assignee and priority
• Blocked issues with blocker description and action needed
• Risks and dependencies
• Next period priorities

**Include more detail** - Team needs issue-level visibility.

For Daily Updates

Use **Daily Standup Format**:

• What was completed yesterday
• What's planned for today
• Current blockers
• Brief notes