generate-status-report

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.

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

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

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

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)

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

After generating the report, ALWAYS offer to publish to Confluence (unless user explicitly said not to).

If user hasn't specified Confluence details yet, ask:

• "Would you like me to publish this report to Confluence?"
• "Which Confluence space should I use?"
• "Should this be nested under a specific parent page?"

Use the createConfluenceContent tool to publish the report.

Before authoring the body, load the authoring guidance. getContentFormatGuide is not a primary tool, so run it through execute (see Calling non-primary tools). Note that toolName takes the content key createConfluencePage, not the name of the tool you are about to call:

executeRead(   # or execute(...) if your client exposes a single execute tool
    name="getContentFormatGuide",
    inputs={"toolName": "createConfluencePage"}
)

Never skip the body because the guidance failed to load — load it first, then build a real body.

Then load the space instructions. Spaces can carry durable authoring guidance that is authoritative and overrides authoring defaults on conflict. Apply this decision rule:

1. Skip this step only if a getConfluenceContent call for content in the target space returned metadata.hasSpaceInstructions=false.
2. Otherwise — true or unknown — call getConfluenceSpace once before authoring:

executeRead(   # or execute(...) if your client exposes a single execute tool
    name="getConfluenceSpace",
    cloudId="...",
    inputs={"spaceIdOrKey": "[space ID or key]"}
)

3. Apply any returned spaceInstructions. If a successful response omits them, no instructions are configured — author with defaults and do not block.

Reuse the result for the rest of the task: do not call getConfluenceSpace again for the same space, and do not follow it with a separate getConfluenceSpaceInstructions call.

Page creation:

createConfluenceContent(
    cloudId="[obtained from listConfluenceSpaces or URL]",
    parent={"spaceId": "[numerical space ID]"},
    contentType="page",
    title="[Project Name] - Status Report - [Date]",
    body={"format": "markdown", "value": "[formatted report]"}
)

To nest the report under an existing page, add parentContentId to parent:

    parent={"spaceId": "[numerical space ID]", "parentContentId": "[parent page ID]"},

Title format examples:

• "Project Phoenix - Weekly Status - Dec 3, 2025"
• "Engineering Sprint 23 - Status Report"
• "Q4 Initiatives - Status Update - Week 49"

Body formatting: Write the report content in Markdown and pass it as body={"format": "markdown", "value": ...}, following the spec returned by getContentFormatGuide. Use:

• Headers (#, ##, ###) for structure
• Bullet points for lists
• Bold (**text**) for emphasis
• Tables for metrics if needed
• Links to Jira issues: [PROJ-123](https://yourinstance.atlassian.net/browse/PROJ-123)

Best practices:

• Include the report date prominently
• Link directly to relevant Jira issues
• Use consistent naming conventions for recurring reports
• Consider creating under a "Status Reports" parent page for organization

User request: "Generate a status report for Project Phoenix and publish it to Confluence"

Step 1 - Identify scope:

• Project: Phoenix (need to find project key)
• Time period: Last week (default)
• Audience: Not specified, assume executive level
• Destination: Confluence, need to find appropriate space

Step 2 - Query Jira:

# Find project key first
searchJiraIssuesUsingJql(
    cloudId="...",
    jql='project = "PHOENIX" OR project = "PHX"',
    maxResults=1
)

# Query completed issues
searchJiraIssuesUsingJql(
    cloudId="...",
    jql='project = "PHX" AND status = Done AND resolved >= -7d',
    maxResults=50
)

# Query blocked issues
searchJiraIssuesUsingJql(
    cloudId="...",
    jql='project = "PHX" AND status = Blocked',
    maxResults=50
)

# Query in-progress high priority
searchJiraIssuesUsingJql(
    cloudId="...",
    jql='project = "PHX" AND status IN ("In Progress", "In Review") AND priority IN (Highest, High)',
    maxResults=50
)

Step 3 - Analyze:

• 15 issues completed (metrics)
• 3 critical blockers (key insight)
• Major accomplishment: API integration completed (highlight)

Step 4 - Format: Use Executive Summary Format from templates. Create concise report with metrics, highlights, and blockers.

Step 5 - Publish:

# Find appropriate space (not a primary tool - run it through execute)
executeRead(name="listConfluenceSpaces", cloudId="...")

# Load authoring guidance before composing the body
executeRead(name="getContentFormatGuide", inputs={"toolName": "createConfluencePage"})

# Load space instructions (skip only if hasSpaceInstructions was false for this space)
executeRead(name="getConfluenceSpace", cloudId="...", inputs={"spaceIdOrKey": "PHX"})

# Create page
createConfluenceContent(
    cloudId="...",
    parent={"spaceId": "12345"},
    contentType="page",
    title="Project Phoenix - Weekly Status - Dec 3, 2025",
    body={"format": "markdown", "value": "[formatted markdown report]"}
)

Be data-driven:

• Include specific numbers and metrics
• Reference issue keys directly
• Show trends when possible (e.g., "completed 15 vs 12 last week")

Highlight what matters:

• Lead with the most important information
• Flag blockers prominently
• Celebrate significant wins

Make it actionable:

• For blockers, state what action is needed and from whom
• For risks, provide mitigation options
• For priorities, be specific about next steps

Keep it consistent:

• Use the same format for recurring reports
• Maintain predictable structure
• Include comparable metrics week-over-week

Provide context:

• Link to Jira for details
• Explain the impact of blockers
• Connect work to business objectives when possible

The Atlassian Rovo MCP server exposes only a small set of primary tools directly in your tool list. Everything else lives in the catalog and is reached through meta-tools:

• discover — describe the goal in natural language when you do not know an operation's name. It returns the exact name and inputs to use. Do not call discover for an operation you already have as a primary tool.
• An execute-family tool — run a catalog operation by name. Check your tool list: some clients expose a single execute, others expose executeRead / executeWrite / executeDestructive and expect the tier matching the operation. The arguments are identical:

executeRead(   # or execute(...) if your client exposes a single execute tool
  name="<operationName>",
  cloudId="...",
  inputs={"param": "value"}
)

Rules that matter:

• cloudId is a top-level argument, a sibling of name and inputs — never put it inside inputs. Operations declared omitCloudId (such as getContentFormatGuide) take no cloudId.
• inputs is a flat object. The server routes each parameter to path, query, or body itself.
• Use the exact parameter names from the live tool schema. Unrecognized parameters are dropped rather than reported as an error, so a wrong name fails silently — the call succeeds and your value is simply ignored. When in doubt, read the schema or discover result first.
• If the call reports an unknown operation, run discover with different keywords and use the name it returns rather than guessing.