[PR #75] [MERGED] feat: add /plan:status command for quick progress check #77

New issue

Closed

opened 2026-03-03 18:50:28 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 18:50:28 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/OthmanAdi/planning-with-files/pull/75
Author: @jonthebeef
Created: 2/8/2026
Status: ✅ Merged
Merged: 2/8/2026
Merged by: @OthmanAdi

Base: master ← Head: feat/status-command

📝 Commits (1)

eec3a44 feat: add /plan:status command for quick progress check

📊 Changes

1 file changed (+49 additions, -0 deletions)

View changed files

➕ commands/status.md (+49 -0)

📄 Description

Summary

Adds a /plan:status command that displays planning progress at a glance - no need to read through all planning files just to see where you are.

The Problem

When using file-based planning, checking your current status requires reading task_plan.md and parsing it mentally. For a quick "where am I?" check, this is more friction than necessary.

The Solution

A new /plan:status command that outputs a compact summary:

📋 Planning Status

Current: Phase 2 of 5 (40%)
Status: 🔄 in_progress

  ✅ Phase 1: Requirements & Discovery
  🔄 Phase 2: Planning & Structure ← you are here
  ⏸️ Phase 3: Implementation
  ⏸️ Phase 4: Testing & Verification
  ⏸️ Phase 5: Delivery

Files: task_plan.md ✓ | findings.md ✓ | progress.md ✓
Errors logged: 2

What's Included

commands/status.md - Command definition with output format specification
Status icons for different states (pending, in_progress, complete, failed/blocked)
Graceful handling when no planning files exist

Why This Helps

Quick orientation - See where you are without context switching
Error awareness - Know if there are logged errors at a glance
File verification - Confirm which planning files exist
Low cognitive load - Visual icons make status immediately clear

🤖 Generated with Claude Code

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/OthmanAdi/planning-with-files/pull/75 **Author:** [@jonthebeef](https://github.com/jonthebeef) **Created:** 2/8/2026 **Status:** ✅ Merged **Merged:** 2/8/2026 **Merged by:** [@OthmanAdi](https://github.com/OthmanAdi) **Base:** `master` ← **Head:** `feat/status-command` --- ### 📝 Commits (1) - [`eec3a44`](https://github.com/OthmanAdi/planning-with-files/commit/eec3a44c720e257fbb3ce30cf973da8f0d071a12) feat: add /plan:status command for quick progress check ### 📊 Changes **1 file changed** (+49 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `commands/status.md` (+49 -0) </details> ### 📄 Description ## Summary Adds a `/plan:status` command that displays planning progress at a glance - no need to read through all planning files just to see where you are. ## The Problem When using file-based planning, checking your current status requires reading `task_plan.md` and parsing it mentally. For a quick "where am I?" check, this is more friction than necessary. ## The Solution A new `/plan:status` command that outputs a compact summary: ``` 📋 Planning Status Current: Phase 2 of 5 (40%) Status: 🔄 in_progress ✅ Phase 1: Requirements & Discovery 🔄 Phase 2: Planning & Structure ← you are here ⏸️ Phase 3: Implementation ⏸️ Phase 4: Testing & Verification ⏸️ Phase 5: Delivery Files: task_plan.md ✓ | findings.md ✓ | progress.md ✓ Errors logged: 2 ``` ## What's Included - `commands/status.md` - Command definition with output format specification - Status icons for different states (pending, in_progress, complete, failed/blocked) - Graceful handling when no planning files exist ## Why This Helps - **Quick orientation** - See where you are without context switching - **Error awareness** - Know if there are logged errors at a glance - **File verification** - Confirm which planning files exist - **Low cognitive load** - Visual icons make status immediately clear --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>