From 23e9466cb821a08ad6a2feeb9dc02fd66f6d50d1 Mon Sep 17 00:00:00 2001 From: Justin Gordon Date: Sat, 27 Jun 2026 15:20:45 -1000 Subject: [PATCH 01/10] skills: add portable continue and status session-discipline skills Add two small, portable skills that carry the same finish-cleanly discipline the PR workflows already use, but for any task: - continue: resume with a checkpoint (where we are / what is next / definition of done) instead of a bare "continue", so resumed work does not drift or repeat. - status: report done / in progress / blocked / next without starting new work. Both are repo-agnostic (no consumer-repo commands) and honor AGENTS.md boundaries. Listed in the README skill inventory. Co-Authored-By: Claude Opus 4.8 --- README.md | 2 ++ skills/continue/SKILL.md | 27 +++++++++++++++++++++++++++ skills/status/SKILL.md | 21 +++++++++++++++++++++ 3 files changed, 50 insertions(+) create mode 100644 skills/continue/SKILL.md create mode 100644 skills/status/SKILL.md diff --git a/README.md b/README.md index cddbfaf..c0af902 100644 --- a/README.md +++ b/README.md @@ -113,6 +113,7 @@ ongoing host installs and upgrades. | `address-review` | Fetch and triage GitHub PR review comments. | | `adversarial-pr-review` | Run a skeptical pre-merge or post-merge PR review. | | `autoreview` | Run a structured second-model local diff review. | +| `continue` | Resume an in-progress task with a structured checkpoint. | | `evaluate-issue` | Decide whether an issue or proposed fix is worth doing. | | `plan-issue-triage` | Produce a ready prompt for review-only issue triage. | | `plan-pr-batch` | Shape candidate issues or PRs before launching a batch. | @@ -121,6 +122,7 @@ ongoing host installs and upgrades. | `replicate-ci` | Reproduce hosted-CI/local parity gaps. | | `run-ci` | Choose and run repo-local CI checks. | | `spec` | Turn vague implementation intent into requirements, design, and tasks. | +| `status` | Report tight progress (done/next/blocked) without starting new work. | | `tdd` | Drive test-first red-green-refactor loops for features and bug fixes. | | `triage` | Build a whole-surface issue/PR inventory and batch split. | | `update-changelog` | Classify merged PRs and update a repo changelog. | diff --git a/skills/continue/SKILL.md b/skills/continue/SKILL.md new file mode 100644 index 0000000..087008c --- /dev/null +++ b/skills/continue/SKILL.md @@ -0,0 +1,27 @@ +--- +name: continue +description: Resume an in-progress task with a structured checkpoint instead of a bare "continue", re-establishing what is done, what is next, and how done is verified. Use when resuming work after an interruption, handoff, or a vague "keep going". +--- + +# Continue + +Resume the current task. Before doing any new work, re-establish context so work does not drift or +repeat: + +1. **Where we are** - Summarize in 2-4 lines what is already done (cite files, commits, or PRs) and + the current goal. If the goal is unclear, state your best inference and proceed; do not stop to + ask unless you are genuinely blocked. +2. **What is next** - List the remaining steps to reach done, then pick the next concrete one. +3. **Definition of done** - Restate the overall success criteria in one line, plus the command or + test that will verify it. +4. Continue working on the next step. + +If the user supplied focus text or arguments, treat it as additional direction or a narrowed scope +for what to continue. + +- Do not re-do completed work, and do not ask the user to repeat context you can reconstruct from + the conversation, open files, or git state. +- Honor `AGENTS.md` boundaries and safety rules while resuming; never push or take irreversible + actions unless the task already authorized them. +- End with a short status line: what changed, how it was verified, what is left. Use `/status` to + produce that report without starting new work. diff --git a/skills/status/SKILL.md b/skills/status/SKILL.md new file mode 100644 index 0000000..5896524 --- /dev/null +++ b/skills/status/SKILL.md @@ -0,0 +1,21 @@ +--- +name: status +description: Report tight progress on the current work - done, in progress, blocked, and next - without starting new work. Use when asked for a status update or "where are we / anything needed from me". +--- + +# Status + +Give a tight status update on the current work. **Do not start new work.** + +Report: + +- **Done** - what is complete and verified. Cite files, commits, or test results, and only claim + "verified" if the check was actually run. +- **In progress** - what is mid-way through. +- **Blocked / needs input** - anything that genuinely needs a decision, credentials, or an external + unblock. If nothing, say "nothing needed - proceeding". +- **Next** - the next one to three concrete steps. + +Keep it to roughly ten lines. If you are waiting on a long-running command or a background agent, +name it and the signal you are waiting for. Do not run another review or build solely to produce a +nicer status. From f9de6ad16ecf00520ed4294e387372b0456e269f Mon Sep 17 00:00:00 2001 From: Justin Gordon Date: Tue, 30 Jun 2026 00:49:15 -1000 Subject: [PATCH 02/10] Address continue status review notes --- README.md | 2 +- skills/continue/SKILL.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index c0af902..edba685 100644 --- a/README.md +++ b/README.md @@ -122,7 +122,7 @@ ongoing host installs and upgrades. | `replicate-ci` | Reproduce hosted-CI/local parity gaps. | | `run-ci` | Choose and run repo-local CI checks. | | `spec` | Turn vague implementation intent into requirements, design, and tasks. | -| `status` | Report tight progress (done/next/blocked) without starting new work. | +| `status` | Report tight progress (done/in-progress/blocked/next) without starting new work. | | `tdd` | Drive test-first red-green-refactor loops for features and bug fixes. | | `triage` | Build a whole-surface issue/PR inventory and batch split. | | `update-changelog` | Classify merged PRs and update a repo changelog. | diff --git a/skills/continue/SKILL.md b/skills/continue/SKILL.md index 087008c..7c3e171 100644 --- a/skills/continue/SKILL.md +++ b/skills/continue/SKILL.md @@ -23,5 +23,5 @@ for what to continue. the conversation, open files, or git state. - Honor `AGENTS.md` boundaries and safety rules while resuming; never push or take irreversible actions unless the task already authorized them. -- End with a short status line: what changed, how it was verified, what is left. Use `/status` to - produce that report without starting new work. +- End with a short status line: what changed, how it was verified, and what is left -- without + starting new work. From f4eed3f9fae672ca9d6e8641b9e4648295a9c1be Mon Sep 17 00:00:00 2001 From: Justin Gordon Date: Tue, 30 Jun 2026 01:10:57 -1000 Subject: [PATCH 03/10] Clarify continue and status boundaries --- skills/continue/SKILL.md | 5 +++-- skills/status/SKILL.md | 4 ++-- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/skills/continue/SKILL.md b/skills/continue/SKILL.md index 7c3e171..e89c28f 100644 --- a/skills/continue/SKILL.md +++ b/skills/continue/SKILL.md @@ -23,5 +23,6 @@ for what to continue. the conversation, open files, or git state. - Honor `AGENTS.md` boundaries and safety rules while resuming; never push or take irreversible actions unless the task already authorized them. -- End with a short status line: what changed, how it was verified, and what is left -- without - starting new work. +- End with a short status line using the same generic labels as a status report: Done, In progress, + Blocked / needs input, and Next. Treat this closing summary as a report of the resumed work, not as + a separate trigger to start additional work beyond step 4. diff --git a/skills/status/SKILL.md b/skills/status/SKILL.md index 5896524..73ed953 100644 --- a/skills/status/SKILL.md +++ b/skills/status/SKILL.md @@ -13,8 +13,8 @@ Report: "verified" if the check was actually run. - **In progress** - what is mid-way through. - **Blocked / needs input** - anything that genuinely needs a decision, credentials, or an external - unblock. If nothing, say "nothing needed - proceeding". -- **Next** - the next one to three concrete steps. + unblock. If nothing, say "nothing blocked". +- **Next** - the next one to three concrete steps, without starting them. Keep it to roughly ten lines. If you are waiting on a long-running command or a background agent, name it and the signal you are waiting for. Do not run another review or build solely to produce a From aaf206ce5e0b12c641b9159910f95287f6a28dca Mon Sep 17 00:00:00 2001 From: Justin Gordon Date: Tue, 30 Jun 2026 01:38:25 -1000 Subject: [PATCH 04/10] Clarify continue cold start handling --- skills/continue/SKILL.md | 8 +++++--- skills/status/SKILL.md | 4 ++-- 2 files changed, 7 insertions(+), 5 deletions(-) diff --git a/skills/continue/SKILL.md b/skills/continue/SKILL.md index e89c28f..4c032d1 100644 --- a/skills/continue/SKILL.md +++ b/skills/continue/SKILL.md @@ -9,8 +9,10 @@ Resume the current task. Before doing any new work, re-establish context so work repeat: 1. **Where we are** - Summarize in 2-4 lines what is already done (cite files, commits, or PRs) and - the current goal. If the goal is unclear, state your best inference and proceed; do not stop to - ask unless you are genuinely blocked. + the current goal. If there is no task currently in progress (no prior conversation, no staged + work, and no recent commits on this branch), say so and ask the user what to continue instead of + inferring a goal. If the goal is unclear but prior work exists, state your best inference and + proceed; do not stop to ask unless you are genuinely blocked. 2. **What is next** - List the remaining steps to reach done, then pick the next concrete one. 3. **Definition of done** - Restate the overall success criteria in one line, plus the command or test that will verify it. @@ -23,6 +25,6 @@ for what to continue. the conversation, open files, or git state. - Honor `AGENTS.md` boundaries and safety rules while resuming; never push or take irreversible actions unless the task already authorized them. -- End with a short status line using the same generic labels as a status report: Done, In progress, +- End with a short status line using the same labels as `skills/status/SKILL.md`: Done, In progress, Blocked / needs input, and Next. Treat this closing summary as a report of the resumed work, not as a separate trigger to start additional work beyond step 4. diff --git a/skills/status/SKILL.md b/skills/status/SKILL.md index 73ed953..41b06b5 100644 --- a/skills/status/SKILL.md +++ b/skills/status/SKILL.md @@ -17,5 +17,5 @@ Report: - **Next** - the next one to three concrete steps, without starting them. Keep it to roughly ten lines. If you are waiting on a long-running command or a background agent, -name it and the signal you are waiting for. Do not run another review or build solely to produce a -nicer status. +name it and the signal you are waiting for. Do not start new long-running work solely to produce a +richer status report. From 12116f99f51ee5dd40ecf73988875e7f032b7591 Mon Sep 17 00:00:00 2001 From: Justin Gordon Date: Tue, 30 Jun 2026 01:58:05 -1000 Subject: [PATCH 05/10] Clarify continue skill metadata --- skills/continue/SKILL.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/skills/continue/SKILL.md b/skills/continue/SKILL.md index 4c032d1..1a66ec3 100644 --- a/skills/continue/SKILL.md +++ b/skills/continue/SKILL.md @@ -1,6 +1,7 @@ --- name: continue description: Resume an in-progress task with a structured checkpoint instead of a bare "continue", re-establishing what is done, what is next, and how done is verified. Use when resuming work after an interruption, handoff, or a vague "keep going". +argument-hint: '[focus text or scope]' --- # Continue @@ -25,6 +26,6 @@ for what to continue. the conversation, open files, or git state. - Honor `AGENTS.md` boundaries and safety rules while resuming; never push or take irreversible actions unless the task already authorized them. -- End with a short status line using the same labels as `skills/status/SKILL.md`: Done, In progress, +- End with a short status line using the same labels as `$status`: Done, In progress, Blocked / needs input, and Next. Treat this closing summary as a report of the resumed work, not as a separate trigger to start additional work beyond step 4. From c805ad7b343363ff5638b7ab1be346233463ceb9 Mon Sep 17 00:00:00 2001 From: Justin Gordon Date: Tue, 30 Jun 2026 02:11:42 -1000 Subject: [PATCH 06/10] Tighten continue status guidance --- skills/continue/SKILL.md | 10 +++++----- skills/status/SKILL.md | 4 ++-- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/skills/continue/SKILL.md b/skills/continue/SKILL.md index 1a66ec3..a9671cd 100644 --- a/skills/continue/SKILL.md +++ b/skills/continue/SKILL.md @@ -16,8 +16,8 @@ repeat: proceed; do not stop to ask unless you are genuinely blocked. 2. **What is next** - List the remaining steps to reach done, then pick the next concrete one. 3. **Definition of done** - Restate the overall success criteria in one line, plus the command or - test that will verify it. -4. Continue working on the next step. + test that will verify it. If there is no runnable check, state how completion will be confirmed. +4. Continue working on **that one next step only**. Stop after completing it. If the user supplied focus text or arguments, treat it as additional direction or a narrowed scope for what to continue. @@ -26,6 +26,6 @@ for what to continue. the conversation, open files, or git state. - Honor `AGENTS.md` boundaries and safety rules while resuming; never push or take irreversible actions unless the task already authorized them. -- End with a short status line using the same labels as `$status`: Done, In progress, - Blocked / needs input, and Next. Treat this closing summary as a report of the resumed work, not as - a separate trigger to start additional work beyond step 4. +- End with a short status line using these labels: Done, In progress, Blocked / needs input, and + Next. If there is nothing blocked, say "nothing blocked". Treat this closing summary as a report of + the resumed work, not as a separate trigger to start additional work beyond step 4. diff --git a/skills/status/SKILL.md b/skills/status/SKILL.md index 41b06b5..ba96133 100644 --- a/skills/status/SKILL.md +++ b/skills/status/SKILL.md @@ -9,8 +9,8 @@ Give a tight status update on the current work. **Do not start new work.** Report: -- **Done** - what is complete and verified. Cite files, commits, or test results, and only claim - "verified" if the check was actually run. +- **Done** - what is complete. Note whether it has been verified, cite the check result when one + exists, or mark it as done and awaiting verification when a check has not run yet. - **In progress** - what is mid-way through. - **Blocked / needs input** - anything that genuinely needs a decision, credentials, or an external unblock. If nothing, say "nothing blocked". From d67a76ba65b7db2f2370cb40b9efce2821cb11b0 Mon Sep 17 00:00:00 2001 From: Justin Gordon Date: Tue, 30 Jun 2026 02:28:57 -1000 Subject: [PATCH 07/10] Harden continue resume guidance --- skills/continue/SKILL.md | 26 +++++++++++++++----------- 1 file changed, 15 insertions(+), 11 deletions(-) diff --git a/skills/continue/SKILL.md b/skills/continue/SKILL.md index a9671cd..61e8a62 100644 --- a/skills/continue/SKILL.md +++ b/skills/continue/SKILL.md @@ -9,15 +9,18 @@ argument-hint: '[focus text or scope]' Resume the current task. Before doing any new work, re-establish context so work does not drift or repeat: -1. **Where we are** - Summarize in 2-4 lines what is already done (cite files, commits, or PRs) and - the current goal. If there is no task currently in progress (no prior conversation, no staged - work, and no recent commits on this branch), say so and ask the user what to continue instead of - inferring a goal. If the goal is unclear but prior work exists, state your best inference and - proceed; do not stop to ask unless you are genuinely blocked. -2. **What is next** - List the remaining steps to reach done, then pick the next concrete one. -3. **Definition of done** - Restate the overall success criteria in one line, plus the command or +1. **Repo rules** - Read `AGENTS.md` first so repo-specific commands, formatting, boundaries, and + safety rules are current before acting. +2. **Where we are** - Summarize in 2-4 lines what is already done (cite files, commits, PRs, issues, + or linked planning docs) and the current goal. If there is no task currently in progress (no prior + conversation, no staged work, no recent commits on this branch, and no open PR or issue context), + say so and ask the user what to continue instead of inferring a goal. If the goal is unclear but + prior work exists, state your best inference and proceed only when confidence is reasonable; for + low-confidence inference, state the hypothesis and ask the user to confirm before acting. +3. **What is next** - List the remaining steps to reach done, then pick the next concrete one. +4. **Definition of done** - Restate the overall success criteria in one line, plus the command or test that will verify it. If there is no runnable check, state how completion will be confirmed. -4. Continue working on **that one next step only**. Stop after completing it. +5. Continue working on **that one next step only**. Stop after completing it. If the user supplied focus text or arguments, treat it as additional direction or a narrowed scope for what to continue. @@ -26,6 +29,7 @@ for what to continue. the conversation, open files, or git state. - Honor `AGENTS.md` boundaries and safety rules while resuming; never push or take irreversible actions unless the task already authorized them. -- End with a short status line using these labels: Done, In progress, Blocked / needs input, and - Next. If there is nothing blocked, say "nothing blocked". Treat this closing summary as a report of - the resumed work, not as a separate trigger to start additional work beyond step 4. +- End with a short status line using the companion status format: Done, In progress, Blocked / needs + input, and Next. If there is nothing blocked, say "nothing blocked". Keep this line aligned with + `status/SKILL.md` when editing either skill. Treat this closing summary as a report of the resumed + work, not as a separate trigger to start additional work beyond step 5. From 66b2781dc180743620d785150eace35c4c489dc1 Mon Sep 17 00:00:00 2001 From: Justin Gordon Date: Tue, 30 Jun 2026 02:42:42 -1000 Subject: [PATCH 08/10] Align continue status block wording --- skills/continue/SKILL.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/skills/continue/SKILL.md b/skills/continue/SKILL.md index 61e8a62..32bc502 100644 --- a/skills/continue/SKILL.md +++ b/skills/continue/SKILL.md @@ -29,7 +29,8 @@ for what to continue. the conversation, open files, or git state. - Honor `AGENTS.md` boundaries and safety rules while resuming; never push or take irreversible actions unless the task already authorized them. -- End with a short status line using the companion status format: Done, In progress, Blocked / needs - input, and Next. If there is nothing blocked, say "nothing blocked". Keep this line aligned with - `status/SKILL.md` when editing either skill. Treat this closing summary as a report of the resumed - work, not as a separate trigger to start additional work beyond step 5. +- End with a short status block using the companion status format: Done (note whether verified or + awaiting verification), In progress, Blocked / needs input, and Next. If there is nothing blocked, + say "nothing blocked". Keep this block aligned with `status/SKILL.md` when editing either skill. + Treat this closing summary as a report of the resumed work, not as a separate trigger to start + additional work beyond step 5. From 36681da6ee9c71564009d38b15b7ad4a45a7c3dd Mon Sep 17 00:00:00 2001 From: Justin Gordon Date: Tue, 30 Jun 2026 02:58:44 -1000 Subject: [PATCH 09/10] Delegate continue summary to status --- skills/continue/SKILL.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/skills/continue/SKILL.md b/skills/continue/SKILL.md index 32bc502..f9e003c 100644 --- a/skills/continue/SKILL.md +++ b/skills/continue/SKILL.md @@ -29,8 +29,5 @@ for what to continue. the conversation, open files, or git state. - Honor `AGENTS.md` boundaries and safety rules while resuming; never push or take irreversible actions unless the task already authorized them. -- End with a short status block using the companion status format: Done (note whether verified or - awaiting verification), In progress, Blocked / needs input, and Next. If there is nothing blocked, - say "nothing blocked". Keep this block aligned with `status/SKILL.md` when editing either skill. - Treat this closing summary as a report of the resumed work, not as a separate trigger to start - additional work beyond step 5. +- End with a `$status` report. Treat this closing summary as a report of the resumed work, not as a + separate trigger to start additional work beyond step 5. From 5d4cdacce5dffe6ee4cc32a88f69898a9be6c7e5 Mon Sep 17 00:00:00 2001 From: Justin Gordon Date: Tue, 30 Jun 2026 03:10:31 -1000 Subject: [PATCH 10/10] Clarify status summary fallback --- skills/continue/SKILL.md | 5 +++-- skills/status/SKILL.md | 6 +++--- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/skills/continue/SKILL.md b/skills/continue/SKILL.md index f9e003c..715a0dd 100644 --- a/skills/continue/SKILL.md +++ b/skills/continue/SKILL.md @@ -29,5 +29,6 @@ for what to continue. the conversation, open files, or git state. - Honor `AGENTS.md` boundaries and safety rules while resuming; never push or take irreversible actions unless the task already authorized them. -- End with a `$status` report. Treat this closing summary as a report of the resumed work, not as a - separate trigger to start additional work beyond step 5. +- End with a `$status` report when that companion skill is installed; otherwise use the same four + sections directly: Done, In progress, Blocked / needs input, and Next. Treat this closing summary + as a report of the resumed work, not as a separate trigger to start additional work beyond step 5. diff --git a/skills/status/SKILL.md b/skills/status/SKILL.md index ba96133..c23cf39 100644 --- a/skills/status/SKILL.md +++ b/skills/status/SKILL.md @@ -16,6 +16,6 @@ Report: unblock. If nothing, say "nothing blocked". - **Next** - the next one to three concrete steps, without starting them. -Keep it to roughly ten lines. If you are waiting on a long-running command or a background agent, -name it and the signal you are waiting for. Do not start new long-running work solely to produce a -richer status report. +Keep it concise: one to three lines per section. If you are waiting on a long-running command or a +background agent, name it and the signal you are waiting for. Do not start new long-running work +solely to produce a richer status report.