Before planning new work, verify whether the previous task is completed from GitHub issue/PR state. Use when the user asks to plan, scope, or define the next task and wants continuity checks.
Run this check before drafting a new plan.
Use this skill when the user asks to:
let's plan Xlet's plan issue #<n>Determine whether the previous task is completed, then gate planning:
completed: proceed with planningnot_completed: ask whether to continue anywayunknown: ask for clarification or confirmationDelegate classification to the workflow precheck script (which delegates to the completion auditor):
gh-csi workflow precheck-previous-task \
--issue "<issue or url, optional>" \
--pr "<pr or url, optional>" \
--json
The script is authoritative for precheck classification.
When the user includes an issue reference (for example issue #11), pass it via --issue.
Always return a short, structured precheck before any planning content:
Precheck: previous task <completed|not_completed|unknown>
Task: <github issue/pr ref>
Evidence:
- GitHub: <issue/pr state summary>
- GH-CSI: <supporting status or n/a>
Decision: <proceed|hold_for_confirmation>
If status is not_completed or unknown, ask a single confirmation question before planning.