sprint-confluence-pages

Creates Confluence sprint status and implementation guide pages plus a Teams review message from PRs and Jira tickets.

Updated May 11, 2026
One-click install
npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill sprint-confluence-pages-thachrocky12345
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-confluence-pages
Source: https://github.com/thachrocky12345/local-agent-train-workstation/tree/main/.claude/skills/sprint-confluence-pages
Command: npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill sprint-confluence-pages-thachrocky12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Publishing sprint documentation manually means copying ticket details, PR links, and QA steps into Confluence and then writing a separate Teams announcement. This Skill automates that entire workflow so reviewers get consistent, complete documentation every sprint. ## Core Features & Use Cases - Sprint Status Root Page: Generates a Confluence page with a Jira-linked ticket table, consolidated PR link, key facts, and a call to action for reviewers. - Implementation Guide Sub-Page: Creates a detailed technical sub-page with endpoint tables, migrations, environment variable requirements, and an interactive QA checklist. - Teams Review Message: Outputs a concise, paste-ready Teams message summarizing what shipped and critical findings. - Use Case: After consolidating multiple Jira tickets into a single PR targeting main, invoke the Skill to discover the PR, fetch ticket details from Jira, publish both Confluence pages, and produce the review request message. ## Quick Start Ask the assistant to publish sprint docs for the current open PR and it will create the Confluence pages and Teams message automatically.

Frequently Asked Questions about sprint-confluence-pages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create Confluence sprint pages from a GitHub PR?

Invoke the Skill with a PR number or let it discover the most recent open PR targeting main. It extracts ticket numbers from the PR body or branch commits, fetches Jira details, and creates a sprint status root page plus an implementation guide sub-page.

How to generate a Teams review request message for a sprint?

After both Confluence pages are created, the Skill outputs a paste-ready Teams message under 150 words. It summarizes what shipped, lists each Jira ticket with links, and highlights three critical findings reviewers should know.

Does the Skill work without specifying a PR number?

Yes, the PR number argument is optional. Without it, the Skill uses the GitHub CLI to list open PRs and selects the most recent one targeting the main branch, then infers tickets from the branch commit history.

What Jira and Confluence configuration does the Skill require?

It uses a fixed Atlassian cloud ID, the Team Hub space (ID 98447), and homepage parent ID 98566. Jira links follow the reallyhq.atlassian.net/browse format, and pages are created via the Confluence markdown content format.

What are the limitations of the sprint documentation output?

The Skill targets a specific Jira/Confluence workspace and GitHub organization, so constants must be edited for other environments. It also depends on PR bodies or commit messages containing recognizable ticket keys like RGDEV-123.