rcode-sprint-status

Summarize sprint progress, blockers, and next actions from phase planning files.

2|1|Updated Apr 10, 2026

Search Tags:#workflow #blockers #phase tracking #scrum #delivery planning #sprint status

Ready to run

npx skills add https://github.com/hanzlahabib/rcode --skill rcode-sprint-status

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rcode-sprint-status
Source: https://github.com/hanzlahabib/rcode/tree/main/rcode/skills/actions/4-implementation/rcode-sprint-status
Command: npx skills add https://github.com/hanzlahabib/rcode --skill rcode-sprint-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of checking sprint files, phase state, and delivery artifacts to understand where a project stands and what should happen next.

Core Features & Use Cases

Sprint Visibility: Summarizes todo, in-progress, and done work for the active phase.
Risk Detection: Flags blocked sprints, missing artifacts, and phases that have not started execution yet.
Next-Step Guidance: Recommends the most appropriate follow-up workflow such as execution, debugging, verification, or milestone completion.
Use Case: A project lead asks for a current sprint update and gets a concise status table plus the next recommended action based on real file state.

Quick Start

Ask the assistant to generate the current sprint status for this project and return the active phase summary, blockers, and next recommended action.

Frequently Asked Questions about rcode-sprint-status

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

FAQPage Schema

How do I get sprint status and identify blockers for an active software delivery phase?▼

To get sprint status, the Skill reads phase planning files and .rcode state to summarize todo, in-progress, and done work. It validates frontmatter, classifies sprints by summary status, and outputs a status table flagging blocked sprints and missing artifacts.

What is the best way to track scrum sprint progress and recommend the next workflow step?▼

Tracking scrum sprint progress is handled by summarizing active phase artifacts and detecting delivery risks. The Skill recommends the most appropriate follow-up workflow, such as execution, debugging, verification, or milestone completion, based on real file state.

Can I use phase tracking to detect missing artifacts in sprints that have not started execution?▼

Yes, phase tracking validates sprint frontmatter and flags missing artifacts. It specifically detects phases that have not started execution yet and classifies blocked sprints, providing risk detection alongside the active phase summary status table.

How do I generate a delivery planning status table with next-action recommendations?▼

Generating a delivery planning status table requires reading .rcode state and phase sprint artifacts. The Skill classifies sprints by summary status, validates frontmatter, and outputs a concise table with identified risks and a recommended next workflow action.

Does sprint status reporting work without external dependencies for Scrum workflow phases?▼

Sprint status reporting works without external dependencies, relying entirely on local .rcode state and phase planning files. It classifies active software delivery phases, validates frontmatter, and outputs blockers and next-step guidance without requiring additional components.

Why does my sprint status show missing artifacts when checking phase planning files?▼

Sprint status shows missing artifacts because the Skill validates frontmatter and reads phase sprint artifacts to detect delivery risks. If expected files are absent from the .rcode state, it flags the phase as blocked or not started to prompt corrective action.