Update to KnowzCode

{
  "description": "Resume an interrupted KnowzCode workflow. Use when the user wants to continue an active WorkGroup, load the latest local handoff, or advance the next pending phase.",
  "included_files": [],
  "name": "continue",
  "skill_md_contents": "---\nname: continue\ndescription: \"Resume an interrupted KnowzCode workflow. Use when the user wants to continue an active WorkGroup, load the latest local handoff, or advance the next pending phase.\"\n---\n\n# /knowzcode:continue — Resume workflow\n\nResume the most relevant active KnowzCode WorkGroup from local files. Knowz MCP is optional and never blocks resume.\n\n## Instructions\n\n1. Check `knowzcode/handoffs/*.md`.\n   - If the user supplied a handoff path or slug, load that handoff.\n   - If no explicit path was supplied, find the newest handoff by filename timestamp.\n   - Handoffs are local operational state. Do not search Knowz vaults for workflow handoffs.\n2. Read `knowzcode/knowzcode_tracker.md` and locate active `[WIP]` work.\n3. If multiple active WorkGroups exist, ask the user which one to resume unless the selected handoff clearly names a WorkGroup.\n4. Read the selected WorkGroup file.\n5. If a handoff was loaded, parse `## Goal`, `## Current State`, `## Next Step`, `## References`, and `## Durable Learning Candidates`. Use the handoff as the freshest local state. Do not run `cmd:` references automatically.\n6. Resume at the next ordinary step:\n   - unfinished Change Set\n   - spec drafting or approval\n   - implementation\n   - read-only audit\n   - finalization\n7. Keep the workflow aligned with `knowzcode/knowzcode_loop.md` and do not skip quality gates unless the user explicitly asked for autonomous execution.\n8. Hand off execution to the same contract as `/knowzcode:work` for the current phase.\n"
}