How this command is triggered — by the user, by Claude, or both
Slash command
/cairn:statusThe summary Claude sees in its command listing — used to decide when to auto-load this command
Run in the project root and present the output to the user: Summarize the goal, active tasks, active decisions and any live agents. If the user asks "what changed?", follow up with `cairn timeline`.
Run in the project root and present the output to the user:
cairn status
Summarize the goal, active tasks, active decisions and any live agents. If the user
asks "what changed?", follow up with cairn timeline.
/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.
/statusDisplays current design system state from .interface-design/system.md including direction, foundation, depth, tokens, patterns, and last updated time. Suggests setup options if no system found.
/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.
npx claudepluginhub abhishekxdg/cairn --plugin cairn