s-status

name	s-status
description	Show current project status - active phase, completed tasks, blockers, and recent activity

/s:status - Project Status Dashboard

Show the user a comprehensive but concise snapshot of their project's current state.

Instructions

Step 1: Check for project initialization

Check if .planning/STATE.md exists in the project root.

If it does NOT exist:

• Display: "No project state found. Run /s:new to initialize a project."
• Stop here. Do not continue.

Step 2: Read state files

Read these files to gather project context:

1. .planning/STATE.md - Current project state, active phase, blockers, decisions
2. .planning/ROADMAP.md - Overall project roadmap with phases and tasks

If ROADMAP.md does not exist, note that planning has not been done yet.

Step 3: Gather recent git activity

Run git log --oneline -10 to get the 10 most recent commits. Run git status --short to see uncommitted changes.

Step 4: Calculate progress

From ROADMAP.md, count:

• Total tasks across all phases (lines matching - [ ] and - [x])
• Completed tasks (lines matching - [x])
• Calculate completion percentage: (completed / total) * 100

If no tasks are defined yet, report "No tasks defined - run /s:plan to create a roadmap."

Step 5: Determine time since last update

From STATE.md, read the Last Updated field. Calculate how long ago the last update was relative to today's date.

Step 6: Display the status dashboard

Present the following summary in a clean, structured format:

=== PROJECT STATUS ===

Status:        {status from STATE.md}
Active Phase:  {phase number and name}
Active Task:   {current task description, or "None" if between tasks}

Progress:      {completed}/{total} tasks ({percentage}%)
               [=====>          ] (visual bar)

Blockers:
- {blocker 1, or "None"}
- {blocker 2}

Recent Commits (last 5):
- {commit hash} {message}
- {commit hash} {message}
- ...

Uncommitted Changes: {count of changed files, or "Working tree clean"}

Last Updated:  {date} ({relative time, e.g., "2 hours ago", "3 days ago"})

Step 7: Suggest next action

Based on the current state, suggest the most logical next action:

• If no requirements exist: "Next: Run /s:discuss to define requirements"
• If no roadmap exists: "Next: Run /s:plan to create implementation roadmap"
• If a phase is in progress: "Next: Run /s:build to continue implementing"
• If a phase is complete but not reviewed: "Next: Run /s:review to review the implementation"
• If blockers exist: "Blockers detected. Consider running /s:debug or /s:brainstorm to address them"
• If all phases are complete: "Next: Run /s:verify to verify, then /s:ship to ship"

Important Notes

• Keep output concise. This is a dashboard, not a report.
• Do NOT modify any files. This skill is read-only.
• If any file is missing or unreadable, gracefully skip that section rather than failing.
• Always show the git activity section even if .planning/ files are incomplete.
• Use the exact format above for consistency across sessions.