Status

Name: Status
Author: rterakedis

ASecurity

Show current epic and story progress via GitHub milestones and issues. Use when the user says "status", "sprint status", or "show progress".

2 stars
0 votes
0 copies
3 views
Added September 19, 2026

ai-agentsgocode-reviewgitapi

Works with

Security analysis

A100/100

Scanned September 19, 2026

npx -y skills add rterakedis/leanwheel-skills --skill status --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Status?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rterakedis-status/badge)](https://www.skillsdirectory.com/skills/rterakedis-status)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: status
description: Show current epic and story progress via GitHub milestones and issues. Use when the user says "status", "sprint status", or "show progress".
---

# Status Skill

**Goal:** Show epic/story progress via GitHub.

Activation: Check auth (`gh auth status`, `gh repo view`). If fails: show story Status fields from `docs/epics/`.

1. Fetch milestones: `gh api repos/.../milestones --jq 'sort_by(.number) | ...'`. If none: "Run `/create-story`."
2. Fetch all issues: `gh issue list --state all --limit 200 --json number,title,labels,milestone,state --jq 'sort_by(...)'`
3. Render dashboard: group by milestone (epic). Issues with no milestone under "⚠ Untracked".

Format:
```
PROJECT STATUS  {repo}  {date}
Epic {N}: {title}  [{closed}/{total} done]
  #{issue}  {icon} {label}  {epic}.{story}: {title}
OVERALL  {closed}/{total} stories done
```

Icons: 📋 ready-for-dev | 🔄 in-progress | 👀 review | ✅ done | 🔲 not created (in epics.md, no issue).

For 🔲: read `docs/epics.md` for stories without GitHub issue.

4. Next action:
   - Any `review` → `/code-review` on {N.M}
   - Any `in-progress` → `/dev-story` continue {N.M}
   - Any `ready-for-dev` → `/dev-story` start {N.M}
   - 🔲 exists → `/create-story` spec {N.M}
   - All done → `/retrospective`

   For routing beyond the dev loop (planning gaps, epic boundaries, post-MVP), suggest `/next`.