--- name: next-action-progress-review description: Help users choose what to do next, prioritize limited time, review progress, or resume stalled CuriousCirkits work, including relevant unfinished onboarding and pending updates. --- # Next Action Progress Review Use optional ranking judgment, not required orchestration. Work independently without requiring another skill first. ## Reconstruct the useful next step Read current outcomes, recent progress, deadlines, blockers, durable Recommendations and constraints that can change the choice. Read the underlying review, proposal or domain record before explaining a pending update. A notification, recommendation or previous chat is not proof of completion. For career work, consider relevant foundation gaps alongside opportunities and application deadlines: unclear direction, missing constraints, conflicting experience or an unsupported résumé claim. Inspect only what can change the ranking. An incomplete profile is not automatically the highest priority. Distinguish a prerequisite for the requested action from an optional improvement. Missing strategy classification does not block evaluating a job; missing evidence limits factual claims. Preserve unknown, stale, skipped, conflicting and not-applicable states instead of treating every gap as a blocker. Exclude completed, archived, rejected, cancelled, dismissed, invalid and superseded work. Rank remaining actions by urgency, expected progress, evidence quality, prerequisites, reversibility, constraints and conflicts. Do not repeat settled intake or recreate existing recommendations. Return one feasible action, why it ranks first, what it would produce and any real prerequisite. Ask only when an unknown answer materially changes the choice. Respect a user's chosen focus, time budget, declined questions and stop requests. ## Preserve decisions and progress Keep facts, inference, recommendation, user decision, execution and outcome separate. A read-only review must not change Goals or mark work completed merely because it ranks first. When an agreed follow-up should be durable, reuse or update the existing Recommendation within scope, show its action and rationale, then independently verify the save. Deferred work is not a scheduled reminder. Do not save a global workflow position or an onboarding-complete flag. Explain available relevant findings now; scheduling is not a reason to delay them. Complete supported reviews in chat, using explicit approval and the existing domain actions. Acceptance alone does not apply a proposal. For Inbox work, recover new replies and unresolved work separately. Read the exact item, actual answer and current owner. Ownership grants no additional permissions. Preserve the original operation identity and request after interruptions; reconcile uncertain writes before retrying. Retain partial results and specific blockers. A saved update does not prove another recipient read it. After verified changes, include the authoritative record link when available; do not invent one. Finish with one actionable recommendation and material uncertainty, distinguishing what was saved from what remains proposed.