project-standalo-note-to-app/.claude/commands/workflow/status.md

5.2 KiB

description allowed-tools
Show workflow status and task summary Read, Bash

Workflow Status

Display current workflow status and task breakdown.

Steps

1. Check Active Workflow

python3 skills/guardrail-orchestrator/scripts/workflow_manager.py status

If active workflow exists, display workflow state. If no workflow, continue with manual task scan.

2. Read Project Manifest

Check project_manifest.json for:

  • Current phase
  • Entity counts by status

3. Scan Tasks

Get the version-specific tasks directory:

TASKS_DIR=$(python3 skills/guardrail-orchestrator/scripts/version_manager.py tasks-dir)

Read all $TASKS_DIR/*.yml files and count by:

  • Status (pending, in_progress, review, approved, completed, blocked)
  • Agent (frontend, backend, reviewer)
  • Type (create, update, delete, review)

4. Display Summary

╔══════════════════════════════════════════════════════════════╗
║                    WORKFLOW STATUS                           ║
╠══════════════════════════════════════════════════════════════╣
║ Active Workflow: <workflow_id> | None                        ║
║ Feature: <feature_name>                                      ║
║ Phase: <current_phase>                                       ║
╠══════════════════════════════════════════════════════════════╣
║ APPROVAL GATES                                               ║
║   🛑 Design:         <pending|approved|rejected>             ║
║   🛑 Implementation: <pending|approved|rejected>             ║
╠══════════════════════════════════════════════════════════════╣
║ TASKS BY STATUS                                              ║
║   ⏳ Pending:     X                                          ║
║   🔄 In Progress: X                                          ║
║   🔍 Review:      X                                          ║
║   ✅ Approved:    X                                          ║
║   ✓  Completed:   X                                          ║
║   🚫 Blocked:     X                                          ║
╠══════════════════════════════════════════════════════════════╣
║ TASKS BY AGENT                                               ║
║   🎨 Frontend: X pending, X completed                        ║
║   ⚙️  Backend:  X pending, X completed                        ║
║   🔍 Reviewer: X pending                                     ║
╠══════════════════════════════════════════════════════════════╣
║ NEXT ACTIONS                                                 ║
║   /workflow:frontend --next   (X tasks available)            ║
║   /workflow:backend --next    (X tasks available)            ║
║   /workflow:review --next     (X tasks to review)            ║
║   /workflow:resume            (continue workflow)            ║
╚══════════════════════════════════════════════════════════════╝

5. Show Design Visualization

If in DESIGNING or AWAITING_DESIGN_APPROVAL phase, display visual design:

python3 skills/guardrail-orchestrator/scripts/visualize_design.py --manifest project_manifest.json

This shows:

  • 📱 Page flow diagram
  • 📄 Page details with components
  • 🧩 Component hierarchy
  • 🔌 API endpoints
  • 🔄 Data flow architecture

5b. Show Implementation Visualization

If in REVIEWING, SECURITY_REVIEW, or AWAITING_IMPL_APPROVAL phase, display what was built:

python3 skills/guardrail-orchestrator/scripts/visualize_implementation.py --manifest project_manifest.json

This shows:

  • 📱 Page structure with routes
  • 🧩 Component hierarchy and relationships
  • 🔌 API endpoints with HTTP methods
  • 📊 Implementation statistics (lines, hooks, types)
  • 🌳 Component tree view

6. List Pending Tasks

Show table of tasks ready to work on:

Task ID Type Agent Priority Dependencies

7. Show Approval Instructions

If AWAITING_DESIGN_APPROVAL:

🛑 Design approval required. Review the entities and tasks, then:
   - Approve: /workflow:approve design
   - Reject:  /workflow:reject design "reason"

If AWAITING_IMPL_APPROVAL:

🛑 Implementation approval required. Review the code, then:
   - Approve: /workflow:approve implementation
   - Reject:  /workflow:reject implementation "reason"