skills.rest
duongtdn
duongtdnCOMMUNITY
Explore all skills by this author →
GitHub

status

Aggregate local sprint files and GitHub issue data into a status report.

Updated Jul 6, 2026
Search Tags:#automation#github#status#sprint#tracking#devloop
One-click install
npx skills add https://github.com/duongtdn/devloop --skill status-duongtdn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/duongtdn/devloop/tree/main/skills/status
Command: npx skills add https://github.com/duongtdn/devloop --skill status-duongtdn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the need to manually cross-reference GitHub issues, local state files, and lock files to understand the current health and progress of your development sprint.

Core Features & Use Cases

  • Unified Sprint Snapshot: Aggregates data from local sprint files, GitHub issue statuses, and active process locks into a single, readable report.
  • Health Monitoring: Automatically detects stale locks, identifies issues closed on GitHub while a run was active, and tracks milestone progress.
  • Use Case: Use this when you need to quickly check which tasks are in progress, which are blocked by stale processes, and whether your current sprint is on track to meet its milestone deadline.

Quick Start

Ask the status skill to show the progress of the current sprint by typing the command to display the sprint snapshot.

Frequently Asked Questions about status

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

FAQPage Schema
How do I get a unified snapshot of sprint progress from GitHub issues and local state files?▼

A sprint progress snapshot aggregates local state files and live GitHub issue data into a single read-only report. It automatically identifies active, stale, or completed tasks and verifies overall milestone health for your development sprint.

Can I track GitHub milestone progress without manually cross-referencing local lock files?▼

Tracking GitHub milestone progress can be automated by aggregating GitHub issue statuses and local lock files into a unified report. This detects stale locks and identifies issues closed on GitHub while a run was active.

Does generating a sprint status report require access to local configuration files?▼

Generating a sprint status report requires access to local sprint configuration files and the GitHub MCP. These components synchronize issue and pull request states to produce the final read-only snapshot.

How do I detect stale process locks during an active development sprint?▼

Detecting stale process locks is handled by health monitoring features within a sprint snapshot report. It identifies blocked tasks by cross-referencing active local process locks against current GitHub issue states.

What is the best way to monitor active development tasks across local environments and GitHub?▼

Monitoring active development tasks is best achieved through a unified sprint snapshot. It cross-references local sprint files, GitHub issue statuses, and active process locks to show which tasks are in progress or blocked.

Related Skills

Explore More Software Engineering Skills→
duongtdnduongtdn

replan

Synchronize GitHub milestones with local sprint tracking files.

Community
Advanced
FrancisVargaFrancisVarga

sprint-status

Compute sprint progress tables and risk flags from plan and story files.

Community
Intermediate
duongtdnduongtdn

abort

Terminate devloop executions by cleaning locks, state files, and optionally preserving work as draft pull requests.

Community
Advanced
AcurioustractorAcurioustractor

act-sprint-workflow

Automate sprint planning, standups, and health checks across ACT projects.

Community
Advanced