jumpstart-mode 1.1.13 → 1.1.14

package/.jumpstart/skills/atlassian-generate-status-report/SKILL.md

@@ -0,0 +1,335 @@
+---
+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:**
+```jql
+project = "PROJECT_KEY" AND status != Done ORDER BY priority DESC, updated DESC
+```
+
+**Issues updated in last week:**
+```jql
+project = "PROJECT_KEY" AND updated >= -7d ORDER BY priority DESC
+```
+
+**High priority and blocked issues:**
+```jql
+project = "PROJECT_KEY" AND (priority IN (Highest, High) OR status = Blocked) AND status != Done ORDER BY priority DESC
+```
+
+**Completed in reporting period:**
+```jql
+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
+
+**Keep it brief** - This is a quick sync, not comprehensive analysis.
+
+## Step 5: Publish to Confluence
+
+**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 `createConfluencePage` tool to publish the report.
+
+**Page creation:**
+```
+createConfluencePage(
+    cloudId="[obtained from getConfluenceSpaces or URL]",
+    spaceId="[numerical space ID]",
+    title="[Project Name] - Status Report - [Date]",
+    body="[formatted report in Markdown]",
+    contentFormat="markdown",
+    parentId="[optional - parent page ID if nesting under another page]"
+)
+```
+
+**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. The tool will convert it to Confluence format. 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
+
+### Finding the Right Space
+
+If the user doesn't specify a Confluence space:
+
+1. Use `getConfluenceSpaces` to list available spaces
+2. Look for spaces related to the project (matching project name or key)
+3. If unsure, ask the user which space to use
+4. Default to creating in the most relevant team or project space
+
+### Updating Existing Reports
+
+If updating an existing page instead of creating new:
+
+1. Get the current page content:
+```
+getConfluencePage(
+    cloudId="...",
+    pageId="123456",
+    contentFormat="markdown"
+)
+```
+
+2. Update the page with new content:
+```
+updateConfluencePage(
+    cloudId="...",
+    pageId="123456",
+    body="[updated report content]",
+    contentFormat="markdown",
+    versionMessage="Updated with latest status - Dec 8, 2025"
+)
+```
+
+## Complete Example Workflow
+
+**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:**
+```python
+# 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:**
+```python
+# Find appropriate space
+getConfluenceSpaces(cloudId="...")
+
+# Create page
+createConfluencePage(
+    cloudId="...",
+    spaceId="12345",
+    title="Project Phoenix - Weekly Status - Dec 3, 2025",
+    body="[formatted markdown report]",
+    contentFormat="markdown"
+)
+```
+
+## Tips for Quality Reports
+
+**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
+
+## Resources
+
+### scripts/jql_builder.py
+Python utility for programmatically building JQL queries. Use this when you need to construct complex or dynamic queries. Import and use the helper functions rather than manually concatenating JQL strings.
+
+### references/jql-patterns.md
+Quick reference of common JQL query patterns for status reports. Use this for standard queries or as a starting point for custom queries.
+
+### references/report-templates.md
+Detailed templates for different report types and audiences. Reference this to select the appropriate format and structure for your report.

package/.jumpstart/skills/atlassian-generate-status-report/references/jql-patterns.md

@@ -0,0 +1,82 @@
+# JQL Query Patterns
+
+Common JQL patterns for status report generation.
+
+## Basic Project Queries
+
+**All open issues in a project:**
+```jql
+project = "PROJECT_KEY" AND status != Done
+```
+
+**Open issues by status:**
+```jql
+project = "PROJECT_KEY" AND status IN ("To Do", "In Progress", "In Review")
+```
+
+## Priority-Based Queries
+
+**High priority open issues:**
+```jql
+project = "PROJECT_KEY" AND status != Done AND priority IN ("Highest", "High")
+```
+
+**Blocked issues:**
+```jql
+project = "PROJECT_KEY" AND status = Blocked
+```
+
+## Time-Based Queries
+
+**Updated in last week:**
+```jql
+project = "PROJECT_KEY" AND updated >= -7d
+```
+
+**Completed in reporting period:**
+```jql
+project = "PROJECT_KEY" AND status = Done AND resolved >= -7d
+```
+
+**Created this sprint:**
+```jql
+project = "PROJECT_KEY" AND created >= -14d
+```
+
+## Assignee Queries
+
+**Unassigned issues:**
+```jql
+project = "PROJECT_KEY" AND assignee is EMPTY AND status != Done
+```
+
+**Issues by team member:**
+```jql
+project = "PROJECT_KEY" AND assignee = "user@example.com" AND status != Done
+```
+
+## Combined Queries for Reports
+
+**Current sprint overview:**
+```jql
+project = "PROJECT_KEY" AND status IN ("To Do", "In Progress", "In Review", "Done") AND updated >= -7d ORDER BY priority DESC, updated DESC
+```
+
+**Risk items (high priority blocked or overdue):**
+```jql
+project = "PROJECT_KEY" AND (status = Blocked OR (duedate < now() AND status != Done)) AND priority IN ("Highest", "High") ORDER BY priority DESC
+```
+
+## Epic and Component Queries
+
+**Issues by epic:**
+```jql
+parent = "EPIC_KEY" AND status != Done
+```
+
+Note: Older Jira instances may use `"Epic Link" = "EPIC_KEY"` instead of `parent`.
+
+**Issues by component:**
+```jql
+project = "PROJECT_KEY" AND component = "ComponentName" AND status != Done
+```

package/.jumpstart/skills/atlassian-generate-status-report/references/report-templates.md

@@ -0,0 +1,120 @@
+# Status Report Templates
+
+This file provides templates for different report formats based on audience and context.
+
+## Executive Summary Format
+
+For delivery managers and executives who need high-level overview:
+
+```markdown
+# [Project Name] - Status Report
+**Date:** [Date]
+**Reporting Period:** [Period]
+
+## Executive Summary
+[2-3 sentences summarizing overall status, major accomplishments, and critical blockers]
+
+## Overall Status
+🟢 On Track | 🟡 At Risk | 🔴 Blocked | ⚪ Not Started
+
+## Key Metrics
+- **Total Issues:** [number]
+- **Completed This Period:** [number]
+- **In Progress:** [number]
+- **Blocked:** [number]
+
+## Highlights
+- [Major accomplishment 1]
+- [Major accomplishment 2]
+- [Major accomplishment 3]
+
+## Critical Blockers
+- **[Blocker Title]** - [Brief description and impact]
+- **[Blocker Title]** - [Brief description and impact]
+
+## Upcoming Priorities
+- [Priority 1]
+- [Priority 2]
+- [Priority 3]
+```
+
+## Detailed Technical Format
+
+For team-level reports with more technical detail:
+
+```markdown
+# [Project Name] - Status Report
+**Date:** [Date]
+**Reporting Period:** [Period]
+
+## Summary
+[Overall project status and key takeaways]
+
+## Progress This Period
+
+### Completed
+- [Issue Key] - [Summary]
+- [Issue Key] - [Summary]
+
+### In Progress
+- [Issue Key] - [Summary] ([Assignee], [Priority])
+- [Issue Key] - [Summary] ([Assignee], [Priority])
+
+### Blocked
+- [Issue Key] - [Summary]
+  - **Blocker:** [Description of blocker]
+  - **Impact:** [How this affects timeline/deliverables]
+  - **Action Needed:** [What needs to happen to unblock]
+
+## Risks and Issues
+- [Risk/Issue description with mitigation plan]
+
+## Next Period Priorities
+- [Planned work item 1]
+- [Planned work item 2]
+
+## Dependencies
+- [External dependency description]
+```
+
+## Daily Standup Format
+
+For daily status updates:
+
+```markdown
+# Daily Status - [Date]
+**Project:** [Project Name]
+
+## Completed Yesterday
+- [Issue Key] - [Brief summary]
+
+## Planned for Today
+- [Issue Key] - [Brief summary]
+
+## Blockers
+- [Blocker description] (Assigned to: [name])
+
+## Notes
+[Any additional context or observations]
+```
+
+## By Priority Breakdown
+
+For priority-focused reporting:
+
+```markdown
+# [Project Name] - Status by Priority
+**Date:** [Date]
+
+## Highest Priority (P0/Blocker)
+- [Issue Key] - [Summary] - Status: [status]
+
+## High Priority (P1/Critical)
+- [Issue Key] - [Summary] - Status: [status]
+
+## Medium Priority (P2/Major)
+- [Issue Key] - [Summary] - Status: [status]
+
+## Low Priority (P3/Minor)
+[Summary count only unless specifically requested]
+```