status

/mk:status — Delivery Status Report

Usage

/mk:status
/mk:status <plan-dir>
/mk:status <plan-slug>

Behavior

Generates a classified, evidence-based delivery status report for the active plan via the project-manager agent. Report is co-located inside the plan dir at {plan-dir}/status-reports/{YYMMDD}-status.md.

This is the foreground entry point for the project-manager agent. Use it when the agent's background auto-invocation (via post-phase-delegation.md rule) is not applicable — e.g., when asking on demand or when disambiguation between multiple active plans is needed.

For "what should I do next" advice, use /mk:help instead. PM is backward-looking ("what's done, what's blocked"); mk:help is forward-looking.

Execution Steps

1. Resolve the plan

• If an argument is given → treat as {plan-dir} or {plan-slug}:
  • If it's an absolute or relative path to a plan dir → use directly
  • If it's a slug → resolve via ls -d tasks/plans/*{slug}*
  • If not found → print "Plan not found: {arg}. Use tasks/plans// form." → exit
• If no argument → Glob tasks/plans/*/plan.md filtered by frontmatter status not in {completed, cancelled, archived}:
  • 0 results → print "No active plan. Run /mk:plan to create one." → exit (no file written)
  • 1 result → use it
  • 2+ results → prompt via AskUserQuestion:
    • header: "Active plan"
    • question: "Which plan should I report on?"
    • options: one per plan (label = title + created date from frontmatter)

2. Delegate to project-manager

Invoke the project-manager agent with the resolved plan dir:

@project-manager Generate delivery status for plan at <plan-dir>.
Write report to <plan-dir>/status-reports/{YYMMDD}-status.md
(create the status-reports/ subdir if absent).
Load template from tasks/templates/pm-status-template.md.

Foreground invocation — do NOT include "run in the background" in the prompt. The command must wait for PM to return the report path before step 3.