Update to KnowzCode

{
  "description": "Route implementation intent into KnowzCode workflow mode. Use for 'start building', 'go ahead', 'implement this plan', or 'build this now' requests.",
  "included_files": [],
  "name": "start-work",
  "skill_md_contents": "---\nname: start-work\ndescription: \"Route implementation intent into KnowzCode workflow mode. Use for 'start building', 'go ahead', 'implement this plan', or 'build this now' requests.\"\n---\n\n# KnowzCode Start Work — Intent router\n\nUse this as a lightweight router into `/knowzcode:work`.\n\n## Instructions\n\n1. Trigger only when the user's message clearly expresses implementation intent such as \"implement this plan\", \"go ahead\", \"start work\", \"build this now\".\n2. Do not trigger for questions, hypotheticals, or pure discussion.\n3. Recover the best available goal from:\n   - the user's current message\n   - a recently discussed plan or investigation in the thread\n   - an active WorkGroup in `knowzcode/workgroups/`\n4. Summarize the goal in one sentence and hand off to `/knowzcode:work` using the contract below.\n5. If there is not enough context to identify the goal safely, ask the user what should be implemented.\n\n## Handoff payload\n\nWhen invoking `/knowzcode:work`, pass a structured payload so the workflow can skip re-discovery:\n\n| Field | Type | Required | Description |\n|-------|------|----------|-------------|\n| `goal` | string | yes | One-sentence imperative summary of what to build |\n| `source_path` | string | no | Path to the plan or investigation file the goal came from |\n| `tier` | `\"micro\" \\| \"light\" \\| \"full\"` | no | Pre-classified scope hint; `/knowzcode:work` may override |\n| `flags` | string | no | Pass-through flags such as `--autonomous` or `--tier full` |\n| `prior_findings_summary` | string | no | 2-3 sentences summarizing key constraints/decisions from the source |\n\nAlways include `goal`. Include `source_path` whenever a plan/investigation was the trigger.\n"
}