← ClaudeAtlas

dhpk-next-steplisted

Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.
hmj1026/dhpk · ★ 2 · AI & Automation · score 71
Install: claude install-skill hmj1026/dhpk
# Next Step Advisor ## When NOT to Use - Auto-loop already handling review/precommit flow (hooks track and assist) - User gave a clear, specific instruction (just do it) - Mid-execution of a skill workflow (follow that skill's progression) ## Procedure 1. Run `bash "${CLAUDE_PLUGIN_ROOT}/scripts/run-skill.sh" dhpk-next-step analyze.js` to collect deterministic findings 2. Parse the JSON output — findings, gates, diff summary, phase, feature_context, next_actions, backlog 3. **If P0/P1 findings exist** → format top 3 as actionable suggestions (Findings Mode) 4. **If mid-pipeline** (gates not all passed, no P0/P1) → use progression tables to suggest next step 5. **If phase = post_precommit** → suggest doc sync + request update (use next_actions) 6. **If phase = feature_complete** → output feature complete summary with backlog 7. **If all gates pass and no P0/P1** → output session summary with commit seed (Summary Mode, P2/P3 shown as oversights) ## Script Integration The analyze script runs 17 deterministic heuristics against git state, review state, and feature context: | Priority | Heuristics | Meaning | |----------|-----------|---------| | P0 | Gate missing (code review, doc review, precommit), state drift | Required steps not completed | | P1 | Test gap, security hotspot, migration risk, doc-sync-needed, request-stale | Important oversights | | P2 | README missing, skill-lint needed, locale drift, mixed concerns, ac-incomplete | Quality improvements | | P3 | Main bra