Update to KnowzCode

{
  "description": "Create a local KnowzCode handoff before clearing context. Use when the user wants to pause, wrap up, step away, clear context, or resume an active WorkGroup later without losing workflow state.",
  "included_files": [],
  "name": "regroup",
  "skill_md_contents": "---\nname: regroup\ndescription: \"Create a local KnowzCode handoff before clearing context. Use when the user wants to pause, wrap up, step away, clear context, or resume an active WorkGroup later without losing workflow state.\"\n---\n\n# /knowzcode:regroup — Local workflow handoff\n\n**Purpose**: Preserve local workflow continuity before the user clears context. Regroup writes operational state to KnowzCode local files. It does not store session handoffs in Knowz vaults.\n\nKnowz MCP is optional and never blocks regroup.\n\n## Ownership boundary\n\n- KnowzCode owns workflow state: active WorkGroup, phase, branch, dirty files, blockers, next steps, autonomy mode, and resume instructions.\n- Knowz owns durable knowledge: decisions, patterns, workarounds, conventions, architecture findings, audit findings, and completion records.\n- Do not write the handoff itself to Knowz. If durable learnings are discovered, list them as extraction candidates or route them through `/knowz-save`.\n\n## Instructions\n\n### Step 1: Prerequisite check\n\n1. Check that `knowzcode/` exists.\n2. Check for `knowzcode/knowzcode_tracker.md`.\n3. If missing, stop and suggest `/knowzcode:setup`.\n\n### Step 2: Resolve WorkGroup\n\n1. If the user supplied a WorkGroup ID or path, use it.\n2. Else read `knowzcode/knowzcode_tracker.md` for active `[WIP]` entries.\n3. If one active WorkGroup exists, use it.\n4. If multiple active WorkGroups exist, choose the one clearly referenced by the current session; otherwise ask the user to choose.\n5. If none exist, create a standalone handoff with `WorkGroupID: none` and point the user toward `/knowzcode:work` after resume.\n\nRead the selected WorkGroup file when available: `knowzcode/workgroups/{WorkGroupID}.md`.\n\n### Step 3: Collect local resume state\n\nKeep it dense and actionable:\n\n- Goal and current phase\n- Completed work or findings\n- Current blockers and unresolved questions\n- Next step from the user's argument, if supplied\n- Active autonomy mode: `Active` | `Inactive` | `Unspecified`\n- Important files, commands, and references\n- Current branch, commit, and dirty-file summary from `git branch --show-current`, `git rev-parse --short HEAD`, and `git status --short`\n\nDo not paste raw transcript text.\n\n### Step 4: Write handoff file\n\nCreate `knowzcode/handoffs/` if it does not exist. Write:\n\n```text\nknowzcode/handoffs/{YYYYMMDD-HHMM}-{slug}.md\n```\n\nUse a 2-5 word kebab-case slug from the goal or WorkGroup. If a file already exists, append `-2`, `-3`, etc.\n\n```markdown\n# KnowzCode Handoff: {short goal}\n\n**Created:** {ISO timestamp}\n**WorkGroupID:** {id or none}\n**WorkGroup File:** {path or none}\n**Current Phase:** {phase or unknown}\n**Autonomous Mode:** {Active|Inactive|Unspecified}\n**Branch:** {branch}\n**Commit:** {short sha}\n**Status:** Active\n\n## Goal\n{exact goal to resume}\n\n## Session Summary\n{<=100 words}\n\n## Current State\n{completed work, current status, blockers; <=180 words}\n\n## Next Step\n{immediate next actions; <=80 words}\n\n## Dirty Files\n{git status --short summary; omit generated noise unless relevant}\n\n## References\n- file:{path} | {why useful}\n- cmd:{command} | {why useful}\n- kz:{knowledge-id} | {title} | {why useful}\n- url:{href} | {why useful}\n\n## Durable Learning Candidates\n{Only decisions, patterns, workarounds, conventions, architecture findings, audit findings, or completion records that may belong in Knowz. Use \"None\" if there are no durable learnings.}\n\n## Fresh Context Prompt\nResume this KnowzCode work.\n\nRead:\n- {handoff path}\n- {WorkGroup file or \"no active WorkGroup\"}\n- knowzcode/knowzcode_loop.md\n\nGoal: {goal}\nContinue from the saved state. Preserve Autonomous Mode only if the user confirms it in the new session.\n```\n\n### Step 5: Link from WorkGroup\n\nIf an active WorkGroup file exists, append or update a `## Handoffs` section with:\n\n```markdown\n- {timestamp}: `knowzcode/handoffs/{file}.md` - {next step summary}\n```\n\n### Step 6: Durable knowledge extraction\n\nDo not save the whole handoff to Knowz.\n\nFor `## Durable Learning Candidates`:\n\n- Include only durable learnings that should survive outside this local workflow.\n- If no capture path is active, leave candidates in the handoff for Phase 3 capture or explicit `/knowz-save`.\n- If MCP is unavailable, do not block regroup. The local handoff is the primary artifact.\n\n### Step 7: Report\n\n```markdown\nKnowzCode handoff saved.\n\nPath: {handoff path}\nWorkGroup: {id or none}\nNext: {next step}\nAutonomous Mode: {Active|Inactive|Unspecified}\n```\n\nThen provide the `Fresh Context Prompt` from the file for copy/paste.\n\n## Related skills\n\n- `/knowzcode:continue` — Load the latest handoff or active WorkGroup and resume\n- `/knowzcode:work` — Start a WorkGroup if there is no active workflow\n- `/knowz-save` — Capture durable learnings, not workflow handoffs (requires the Knowz plugin)\n"
}