gds-sprint-status

Summarize sprint status and surface risks from sprint-status.yaml.

1|Updated Aug 3, 2025

Search Tags:#workflow #planning #development #agile #status #sprint #risk

Ready to run

npx skills add https://github.com/MazenMrad/Obsidio --skill gds-sprint-status

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gds-sprint-status
Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/gds-sprint-status
Command: npx skills add https://github.com/MazenMrad/Obsidio --skill gds-sprint-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow summarizes sprint status and surfaces risks to keep teams aligned and guide next steps.

Core Features & Use Cases

Automated visibility: Condenses sprint-status.yaml into a concise overview of stories and epics across backlog, in-progress, review, and done.
Risk detection & recommendations: Identifies stale statuses, orphaned work, and in-progress epics without stories, proposing actionable next actions.
Decision-ready outputs: Produces a recommended next workflow and identifiers for the next story, plus optional risk notes for stakeholders.

Quick Start

Ask the agent to run the sprint-status workflow to generate a live sprint report from sprint-status.yaml.

Frequently Asked Questions about gds-sprint-status

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

FAQPage Schema

How do I summarize sprint status and identify risks from a YAML file?▼

To summarize sprint status and identify risks, the workflow reads a sprint-status.yaml file, validates development statuses against known values, and outputs a concise overview of backlog, in-progress work, and optional risk notes.

What do I need to generate an automated sprint report for agile teams?▼

Generating an automated sprint report requires a sprint-status.yaml file containing specific fields like generated, project, project_key, tracking_system, and development_status to map epics and stories accurately.

How does automated risk detection work for in-progress epics and backlog items?▼

Automated risk detection works by scanning the sprint-status.yaml for stale statuses, orphaned work, and in-progress epics without stories, then surfacing these as actionable risk notes and recommending a next workflow.

Can I use this workflow to get decision-ready next actions for sprint planning?▼

Yes, you can use this workflow to get decision-ready next actions for sprint planning, as it produces a recommended next workflow and identifiers for the next story based on your current development_status.

What happens if my sprint-status.yaml has invalid development statuses?▼

If your sprint-status.yaml has invalid development statuses, the workflow validates statuses against known values and flags anomalies like stale statuses or orphaned work as risks to guide corrections.

What is the best way to surface orphaned work and stale statuses during a sprint review?▼

The best way to surface orphaned work and stale statuses during a sprint review is to run the workflow to condense sprint-status.yaml into a risk-detection overview that proposes actionable next steps.