Add multi-turn-consistency-check skill for grounding corrected long threads

skills/.curated/multi-turn-consistency-check/LICENSE.txt

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf of
+   any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don\'t include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

skills/.curated/multi-turn-consistency-check/SKILL.md

@@ -0,0 +1,119 @@
+---
+name: "multi-turn-consistency-check"
+description: "Run a deliberate consistency pass over long, correction-heavy conversations to reduce factual drift, unsupported carry-over, and context confusion. Use when a thread spans multiple turns with changing requirements, ambiguous callbacks to earlier context, conflicting dates, names, IDs, paths, or any answer must separate verified facts from inference before concluding. Prefer explicit invocation for targeted checks. Do not trigger for short self-contained requests or purely creative tasks."
+---
+
+# Multi Turn Consistency Check
+
+## Overview
+
+Keep long conversations anchored to the latest confirmed state. Rebuild the active facts from the most recent user instructions, tool outputs, files, and external sources before answering; do not inherit earlier assistant claims as truth.
+
+This skill is single-mode by default: perform an internal consistency pass at answer time. Do not create or maintain a persistent conversation log unless the user explicitly asks for one, or the task is clearly a handoff that benefits from a durable summary.
+
+## Quick Start
+
+1. Rebuild the current state from the latest user turns and fresh evidence.
+2. Create a compact internal fact ledger. Always load `references/fact-ledger.md`.
+3. Scan for conflicts. Load `references/conflict-signals.md` when the thread is long, corrected, or scope-shifting.
+4. Verify unstable claims before concluding.
+5. Answer from the ledger and mark assumptions explicitly.
+
+## Rebuild The Current State
+
+- Prefer the latest explicit user instruction over earlier assistant assumptions or plans.
+- Treat prior assistant messages as unverified unless they are backed by a file read, command output, cited source, or explicit user statement.
+- Re-resolve pronouns and relative references such as "that change", "same as before", "the second option", "today", and "latest" against the current turn.
+- When time is involved, anchor the answer to exact dates instead of relying on relative words alone.
+- When the request depends on code, reread the relevant files before claiming current behavior or status.
+
+## Build A Fact Ledger
+
+Create a short internal ledger before the final answer. Use the categories from `references/fact-ledger.md`:
+
+- user-stated facts
+- verified local facts
+- verified external facts
+- bounded inferences
+- unresolved items
+
+Keep each claim atomic and attach the source mentally or explicitly in the answer when useful. Never silently upgrade an inference into a verified fact.
+
+Do not write this ledger to a markdown file by default. Keep it internal unless the user explicitly requests a written handoff, status record, or persistent working note.
+
+## Check For Conflict Patterns
+
+Use `references/conflict-signals.md` to detect and resolve:
+
+- later user turns that reverse earlier requirements
+- mismatched names, IDs, branches, paths, dates, or numbers
+- stale plans that survived after scope changed
+- assistant claims that were never grounded in evidence
+- references to "current", "latest", or "today" that require verification
+- entity swaps where the thread changes subject but keeps inherited assumptions
+
+When a conflict exists, say so plainly. Either resolve it from evidence or ask one short blocking question if the answer would otherwise be risky.
+
+## Verify Unstable Or High-Risk Claims
+
+Verify before answering when:
+
+- the user asks for "latest", "current", "today", "recent", prices, schedules, laws, versions, or leadership
+- the codebase may have changed since the last read
+- the thread contains corrections, retries, or previous failed attempts
+- the claim would materially change the recommendation, fix, or plan
+- the answer is high-stakes or would spend real time or money
+
+If verification is not possible, say that it is unverified. Do not fill the gap with a confident guess.
+
+## Write The Final Answer
+
+- Lead with the conclusion only after grounding it.
+- Distinguish verified statements from inferences in the wording.
+- Mention the conflict you resolved when it materially affects the result.
+- Keep assumptions short and explicit.
+- Cite files, command results, or sources when they are the basis of the answer.
+- If the user appears confused about dates, include the exact date in the response.
+- Do not repeat a prior assistant error just because it is in the context window.
+
+## Use A Short Correction Pattern
+
+When prior context is wrong or stale:
+
+1. State the conflict.
+2. State the current grounded version.
+3. State what remains uncertain, if anything.
+4. Continue with the answer or next step.
+
+Example phrasing:
+
+- "The thread contains two conflicting branch names. The current repo state shows `release/2026-03`, so I am using that."
+- "Earlier in the conversation `X` was treated as completed, but the file still contains the unfinished marker. I am treating it as unfinished."
+- "I can answer the rest, but the dependency version is still unverified."
+
+## Stay Proportional
+
+- Use full grounding when stale context could cause a wrong answer, bad edit, or incorrect recommendation.
+- Use lighter grounding for short, self-contained, or obviously creative tasks.
+- If a single unresolved point blocks a safe answer, ask one short question instead of forcing a complete response.
+- Avoid adding process overhead when a quick reread of the relevant context is enough.
+
+## Persistent Notes Are Optional
+
+- Do not create `conversation-ledger.md`, `working-state.md`, or similar files by default.
+- Write a persistent note only when the user asks for one, the task requires a handoff, or the thread is long enough that a durable record clearly reduces risk.
+- If you do write one, keep it short, factual, and easy to refresh from current evidence.
+
+## Avoid These Failure Modes
+
+- Propagating a prior assistant mistake because it was said confidently.
+- Treating plans, examples, or hypothetical options as completed work.
+- Assuming the latest user request inherits all earlier constraints when the user has changed direction.
+- Answering relative-date questions without converting to exact dates.
+- Claiming repo state from memory instead of rereading the relevant files.
+- Merging contradictory facts into a single blended answer.
+
+## Reference Map
+
+- `references/fact-ledger.md` -> Use for the minimal ledger format and evidence labels.
+- `references/conflict-signals.md` -> Load when the thread is long, corrected, or scope-shifting.

skills/.curated/multi-turn-consistency-check/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Multi-Turn Consistency Check"
+  short_description: "Reduce factual drift across long threads"
+  default_prompt: "Use $multi-turn-consistency-check to rebuild the active facts in this corrected multi-turn thread, keep an internal fact ledger, call out conflicts, and answer only from the verified current state."
+policy:
+  allow_implicit_invocation: false

skills/.curated/multi-turn-consistency-check/references/conflict-signals.md

@@ -0,0 +1,29 @@
+# Conflict Signals
+
+Load this file when the thread is longer than a few substantive turns, contains corrections, or refers back to earlier work.
+
+## Common Signals
+
+- A later message reverses a prior yes or no decision.
+- Names, IDs, branches, file paths, dates, or numbers differ across turns.
+- The user says "same as before" after the topic or scope has changed.
+- A plan created earlier is being reused after the codebase or requirements changed.
+- An assistant claim is being carried forward without tool evidence.
+- Relative time words such as "today", "tomorrow", or "latest" appear in a thread that already has date confusion.
+
+## Resolution Order
+
+1. Latest explicit user instruction
+2. Fresh local evidence from files, commands, and tools
+3. Fresh external evidence from authoritative sources
+4. Older user context
+5. Earlier assistant text
+6. Model inference
+
+## Action Pattern
+
+- Restate the conflict in one sentence.
+- Resolve it from current evidence when possible.
+- If it cannot be resolved safely, ask one short blocking question.
+- Remove the stale assumption from the next answer instead of blending both versions.
+- Replace relative time words with exact dates when time is part of the conflict.