feat: add skill for scrum of scrums summary

[juandspy]

Results and price in https://redhat-internal.slack.com/archives/C01A4DTTZN1/p1781085910720499

Based on https://github.com/lenasolarova/skills/blob/main/epic-status-update/SKILL.md

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 5201a6f9-f527-4b08-a27e-63d384d71cd8

📥 Commits

Reviewing files that changed from the base of the PR and between 7638082 and 19ef14a.

📒 Files selected for processing (1)

• skills/scrum-of-scrums/skill.md

✅ Files skipped from review due to trivial changes (1)

• skills/scrum-of-scrums/skill.md

---

Summary by CodeRabbit

• Documentation
  • Added new skill documentation for generating weekly scrum-of-scrums reports for processing teams
  • Includes comprehensive workflows and templates for epic status reporting with completion tracking and summary tables
  • Specifies required report structure and output guidelines for consistent team reporting

Walkthrough

A new skills/scrum-of-scrums/skill.md document defines a skill that generates weekly Processing team Scrum of Scrums reports. The skill queries Jira for in-progress epics via JQL, aggregates per-epic status updates (reusing detailed reports or generating new ones), and formats a structured markdown report with completion percentages, activity summaries, a summary table, and output constraints.

Changes

Scrum of Scrums Skill Documentation

Layer / File(s)	Summary
Skill metadata and overview skills/scrum-of-scrums/skill.md (lines 1–17)	Front-matter metadata and description define the skill's purpose: generating a weekly Scrum of Scrums report for CCX Core - Processing epics with a 7-day scope, typically run on Wednesdays.
Prerequisites and Atlassian MCP setup skills/scrum-of-scrums/skill.md (lines 18–25)	Documents Atlassian MCP server requirements, authentication retry behavior for unavailable tools, and guidance for obtaining cloudId via getAccessibleAtlassianResources.
Epic discovery and status handling skills/scrum-of-scrums/skill.md (lines 26–54)	Step 1 uses JQL to discover in-progress epics with specific labels and due-date ordering; Steps 2–3 define branching: reuse existing detailed status reports or generate new updates via the epic-status-update skill without adding comments unless requested.
Report structure and output rules skills/scrum-of-scrums/skill.md (lines 55–95)	Step 4 defines per-epic section template (period, completion %, required bullets for summary/status/7-day movement, and nested lists for closed vs. in-progress/review issues). Output rules govern summary table content, highlights, Jira linking format, factual-only reporting, completion % re-checks, handling of epics with no child issues, truncation behavior, and prohibition on creating/editing Jira issues unless explicitly requested.
Trigger phrases and quick reference skills/scrum-of-scrums/skill.md (lines 96–120)	Specifies markdown file export, provides example trigger phrases for invoking the skill, and maps MCP calls to their expected outputs for report generation.

Sequence Diagram(s)

sequenceDiagram
  participant User
  participant ProcessingSkill
  participant MCP
  participant EpicStatusSkill
  User->>ProcessingSkill: request weekly scrum-of-scrums
  ProcessingSkill->>MCP: getAccessibleAtlassianResources (cloudId)
  ProcessingSkill->>MCP: searchJiraIssuesUsingJql (discover epics)
  alt detailed status exists
    ProcessingSkill->>MCP: getJiraIssue (expanded changelog/comments)
  else generate status
    ProcessingSkill->>EpicStatusSkill: invoke epic-status-update (per-epic)
    EpicStatusSkill-->>ProcessingSkill: status text (no comments added)
  end
  ProcessingSkill->>User: export markdown report (per-epic sections, summary table)

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: adding a new skill for scrum of scrums summary generation.
Description check	✅ Passed	The description is related to the changeset by referencing discussion context and the skill it's based on.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch add-skill-scrum-of-scrums

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

skills/scrum-of-scrums/skill.md (1)

107-112: 💤 Low value

Add language identifier to fenced code block.

Markdownlint recommends specifying a language identifier for fenced code blocks. Since this block contains plain text reference information, consider adding text as the language identifier.

♻️ Proposed fix

 ## Quick reference — MCP calls
 
-```
+```text
 getAccessibleAtlassianResources → cloudId
 searchJiraIssuesUsingJql       → epic list (Step 1)
 searchJiraIssuesUsingJql       → child issues, one epic per call, paginate

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@skills/scrum-of-scrums/skill.md` around lines 107 - 112, The fenced code
block with the Jira call notes (lines containing
getAccessibleAtlassianResources, searchJiraIssuesUsingJql, getJiraIssue) lacks a
language identifier; update the block to use a language tag (use "text") by
changing the opening fence to ```text so the markdown linter recognizes it as
plain text.

Source: Linters/SAST tools

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@skills/scrum-of-scrums/skill.md`:
- Around line 44-47: The sentence in "Step 2: Check if the epic has a detailed
status report" currently ends with "jump to step."—update that sentence to
explicitly say "jump to Step 4" so it reads something like "use that and jump to
Step 4." Locate the heading "Step 2: Check if the epic has a detailed status
report" and the trailing phrase "jump to step." and replace it with the
clarified phrase referencing "Step 4".

---

Nitpick comments:
In `@skills/scrum-of-scrums/skill.md`:
- Around line 107-112: The fenced code block with the Jira call notes (lines
containing getAccessibleAtlassianResources, searchJiraIssuesUsingJql,
getJiraIssue) lacks a language identifier; update the block to use a language
tag (use "text") by changing the opening fence to ```text so the markdown linter
recognizes it as plain text.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 0dcf32a8-7e43-4be8-83c0-373316f09b77

📥 Commits

Reviewing files that changed from the base of the PR and between 2da99cb and e9fa68b.

📒 Files selected for processing (1)

• skills/scrum-of-scrums/skill.md