mkhelplisted

# Navigation Help Answers "What should I do next?" by scanning project state and mapping to the 7-phase pipeline. ## How It Works Scan these sources in order, stop at the first actionable recommendation: ### 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 `git status` for staged/unstaged changes. - Changes exist + review approved → "Ready to ship. Run `/mk:ship` (Phase 5)" - Changes exist, no review → "Changes detected but no review. Run reviewer first." ### 5. Clean State No plans, no reviews, no changes. - "Everything clean. Options: start a new task with planner, run `/mk:retro`, or ask me anything." For skill suggestions based on task type, see `mk:agent-detector` (its `references/l