How this command is triggered — by the user, by Claude, or both
Slash command
/jsf:statusThe summary Claude sees in its command listing — used to decide when to auto-load this command
Read factory memory via Bash (`memory.py list-keys`, then `memory.py read --key <key>` for relevant keys). Display: - Project: `initial_request` summary - Clarification: confirmed / pending - Plan: number of phases, phase names - Each phase: complete / in-progress / not-started, with commit SHA if complete - Pending validations: any `phase_complete` without `validation_confirmed` - Memory keys: count of live entries, file location
Read factory memory via Bash (memory.py list-keys, then memory.py read --key <key> for relevant keys). Display:
initial_request summaryphase_complete without validation_confirmednpx claudepluginhub jmeagher/software-factory --plugin jsf/statusDisplay Conductor project status including overall progress, active tracks summary, and next actions. Optional [track-id] [--detailed] for per-track task details and blockers.
/statusDisplays compact planning status from task_plan.md: current phase and progress, phase list with icons, error count, and planning file checks.
/statusShows active and recent Codex jobs for this repository in a compact Markdown table, including review-gate status. Pass job ID for full details; supports --wait, --timeout-ms, --all.
/statusChecks current session status and measures goal drift to assess alignment and progress in the conversation.
/statusDisplays status of tasks in the orchestration system, including summaries, distributions, detailed views, timelines, and velocity reports with filters for date, status, agent, priority, and type.
/statusDisplays status of tasks in the orchestration system, including summaries, distributions, detailed views, timelines, and velocity reports with filters for date, status, agent, priority, and type.