sync-prep

Analyze Jira board data for blockers, health, and scope changes.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/SenzoStack/product-delivery-skills --skill sync-prep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-prep
Source: https://github.com/SenzoStack/product-delivery-skills/tree/main/skills/sync-prep
Command: npx skills add https://github.com/SenzoStack/product-delivery-skills --skill sync-prep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Sync Prep skill transforms Jira board data into a compact, action-oriented briefing that surfaces delivery risks and blockers before daily ceremonies.

Core Features & Use Cases

  • Analyzes Scrum sprints and Kanban boards to detect anti-patterns, blockers, burnout signals, and scope changes.
  • Generates a concise, prioritised briefing with ticket references, assignees, and recommended focus items for the team.
  • Supports integration visibility: indicates when Jira or GitHub access is unavailable and gracefully skips non-critical checks.

Quick Start

Ensure Jira tools are connected, choose a board and mode, then ask me to generate today’s sync briefing.

Frequently Asked Questions about sync-prep

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

FAQPage Schema
How do I generate a daily standup briefing from Jira board data?

Analyze Jira board health by examining Scrum sprints and Kanban boards to detect anti-patterns, blockers, burnout signals, and scope changes before your daily sync.

What should I do if Jira access is unavailable for sprint analysis?

If Jira access is unavailable, the sprint analysis gracefully skips non-critical checks and returns a briefing that indicates missing integration visibility while surfacing remaining delivery risks.

Can I use this daily sync prep for both Scrum sprints and Kanban boards?

Yes, daily sync prep applies to both Scrum sprints and Kanban boards, analyzing attached boards to surface actionable insights and recommended focus items for the team.

How are delivery risks and blockers prioritized in the standup briefing?

Delivery risks and blockers are prioritized by analyzing anti-patterns and scope changes across attached boards, returning a compact brief with ticket references, assignees, and recommended focus items.

Does GitHub integration visibility affect the Jira sync briefing output?

GitHub integration visibility affects the Jira sync briefing by indicating when access is unavailable, allowing the system to gracefully skip non-critical checks while maintaining core delivery risk analysis.