mkhelplisted

# Navigation Help Answers "What should I do next?" by scanning project state and mapping to the 7-phase pipeline. ## How It Works `mk:help` is the FORWARD-looking navigator (what to do next). Backward-looking delivery analysis stays with `/mk:status` (project-manager) — this skill never reproduces it. Collect candidates from ALL scan sources below, then RANK them and emit the top 3 — do NOT stop at the first hit. The rank-1 candidate equals what the old "stop at first actionable hit" behavior would have returned (back-compat); ranks 2–3 are alternates with one-line rationale. This skill is read-only: it reads state, never writes it. ### 1. Paused Step-File Workflows Check `session-state/*-progress.json` for any in-progress step-file workflow. - Found → "Resume [skill] at step [N]. Run `/mk:[skill]` to continue." ### 2. In-Progress Plans Check `tasks/plans/` for plan files without matching review verdicts. - Plan exists, no tests → "Plan approved. Next: run tester agent (Phase 2 — RED)" - Plan exists, tests failing → "Tests failing. Next: run developer agent (Phase 3 — GREEN)" - Plan exists, tests passing, no review → "Tests green. Next: run reviewer agent (Phase 4 — Review)" ### 3. Pending Reviews Check `tasks/reviews/` for verdict files with WARN or action items. - WARN verdict → "Review has warnings. Acknowledge and approve for Gate 2, or fix findings." - FAIL verdict → "Review failed. Fix required changes, then re-run reviewer." ### 4. Uncommitted Changes Check `gi