sg-status

Read planning files and output the next super-gsd command.

2|Updated May 15, 2026
One-click install
npx skills add https://github.com/gyuha/super-gsd --skill sg-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sg-status
Source: https://github.com/gyuha/super-gsd/tree/main/.agents/skills/sg-status
Command: npx skills add https://github.com/gyuha/super-gsd --skill sg-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes uncertainty about where the super-gsd loop is currently paused by showing the active phase, the latest handoff timestamp, and the next recommended command.

Core Features & Use Cases

  • Workflow stage visibility: Reads .planning/HANDOFF.md and renders the current Stage mapping into a user-readable state.
  • Phase awareness: Uses the Phase line from .planning/STATE.md to contextualize progress within the loop.
  • Forward guidance: Computes and outputs the correct next /super-gsd:sg-* command by inspecting both current stage and whether additional phases exist in .planning/ROADMAP.md.
  • Team quick view: With the --team flag, aggregates recent HANDOFF activity by user from HANDOFF.md and prints a team status table.

Quick Start

Run sg-status to display the current phase, stage, last handoff time, and the next recommended command.

Frequently Asked Questions about sg-status

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

FAQPage Schema
How do I check the current stage of my workflow and find the next command to run?

Phase awareness uses the Phase line from .planning/STATE.md to contextualize progress within the loop, while forward guidance computes the next command by inspecting both the current stage and remaining phases in .planning/ROADMAP.md.

How do I resume a paused planning loop safely without manual command sequencing?

By reading .planning/HANDOFF.md and .planning/ROADMAP.md, the system performs deterministic stage-to-command routing to compute the exact next step, enabling safe resumption of planning or execution.

Can I view a team status table for recent handoff activity during workflow execution?

Using the --team flag aggregates recent handoff activity by user from HANDOFF.md and prints a team status table, providing a quick view of workflow execution progress across the team.

What files do I need to set up before tracking workflow status and next-step suggestions?

You need .planning/HANDOFF.md, .planning/STATE.md, and .planning/ROADMAP.md to provide the handoff timestamps, phase lines, and remaining phases required for deterministic stage-to-command routing and next-step suggestions.

Does next-step suggestion work if there are no additional phases left in the roadmap?

Next-step suggestion checks whether additional phases exist in .planning/ROADMAP.md; if the roadmap is exhausted, the deterministic routing will not output a new planning or execution command.