← KnowzCodeCONTENT HISTORY

Update to KnowzCode

Snapshot Sep 30, 2026 · 23:16 UTC · version 1.0.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Detect pause, wrap-up, handoff, or clear-context intent and offer a KnowzCode regroup handoff. Triggers when the user says they need to stop, step away, clear context, start fresh, hand off, or resume later.",
  "included_files": [],
  "name": "regroup-trigger",
  "skill_md_contents": "---\nname: regroup-trigger\ndescription: \"Detect pause, wrap-up, handoff, or clear-context intent and offer a KnowzCode regroup handoff. Triggers when the user says they need to stop, step away, clear context, start fresh, hand off, or resume later.\"\n---\n\n# KnowzCode Regroup Trigger — Intent router\n\nUse this as a lightweight router into `/knowzcode:regroup`. It never writes handoffs directly.\n\n## Instructions\n\n1. Trigger only when the user's message clearly signals pause, wrap-up, handoff, or context clearing:\n   - \"wrap up\", \"pause here\", \"stop here\"\n   - \"I need to step away\", \"take a break\"\n   - \"clear context\", \"new context\", \"fresh session\", \"start a new chat\"\n   - \"handoff\", \"resume later\", \"continue later\", \"pick this back up\"\n   - \"context is getting long\", \"summarize so we can continue later\"\n2. Do not trigger for normal questions or active implementation requests.\n3. Do not trigger during explicit `/knowzcode:*` or `/knowz` command execution.\n4. Check that `knowzcode/` exists. If not, do nothing.\n5. Read `knowzcode/knowzcode_tracker.md` when available to detect active WorkGroups, but do not block if the read fails and the user's handoff intent is explicit.\n6. Offer exactly once:\n   ```text\n   This looks like a good checkpoint. Want me to run `/knowzcode:regroup` with the current goal and next step so you can resume cleanly after clearing context?\n   ```\n7. If the user agrees, hand off to the same workflow as `/knowzcode:regroup`, passing any explicit next-step hint.\n8. If the user declines or ignores the offer, do nothing.\n9. Never auto-regroup, never save workflow state to Knowz, and never write the handoff directly from this trigger.\n"
}

SHA-256 of public snapshot: 3b0ca52e8012182f2d5d2d1da04263975d3cb3cfe3b83fcdea59fdaba42485e8