Flow Status

flow-status — sprint dashboard

Pure status output. No reasoning, no recommendation. Just renders what sprint-status.yaml says.

When to use

• User wants a quick visual of the sprint progress
• Need to surface what is done / in-progress / blocked
• After any flow-* skill, to confirm a state transition landed
• Cheap alternative to /flow-help when orientation isn't needed

Inputs

• .agents/implementation/sprint-status.yaml (required — error out if missing)

Process

1. Read .agents/implementation/sprint-status.yaml.
2. Parse the development_status block (BMAD-style flat map of key: status).
3. Group entries by epic in declaration order. Recognize keys:

• epic-NNN → epic header
• story-NNN-MM → story line
• epic-NNN-retrospective → retrospective marker (after the epic block)

1. Render with one symbol per story status:

| Symbol | Status | |---|---| | ✓ | done | | ▶ | in-progress / review | | ◆ | ready-for-dev | | ○ | backlog | | ✗ | blocked / cancelled |

1. Aggregate epic status (shown in parentheses after Epic N):

• done — all stories of the epic are done
• in-progress — at least one story is in-progress, review, or ready-for-dev
• backlog — no story started, but the epic key in development_status says backlog
• not-started — all stories backlog

1. Sprint summary at the top (one line):

Sprint: | Stories: | Done: | In progress: | Backlog:

Output format (strict)

Sprint:  | Stories:  | Done:  | In progress:  | Backlog: 

Epic 1 (done)
  ✓ story-001-01   done
  ✓ story-001-02   done

Epic 2 (in-progress)
  ✓ story-002-01   done
  ▶ story-002-03   in-progress
  ○ story-002-04   backlog
  ...

Epic 3 (not-started)
  ○ story-003-01   backlog
  ...

Alignment: pad story ids to the longest id width + 2 spaces so status columns align.

Compact mode for very long sprints (> 50 stories): collapse fully-done epics into a one-liner Epic N (done — 8 stories) instead of listing each story.

What this skill does NOT do

• No recommendation. No "next command". No reasoning. → use /flow-help.
• No risk surfacing. No retrospective hints. → use /flow-retro at end of epic.
• No artifact creation. Pure read-only.

Output is text

Don't write to any file. Pure stdout for the user.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: edouard-claude
• Source: edouard-claude/pi-flow-skills
• License: MIT

Install and usage instructions live in the source repository linked above.