Update to KnowzCode

{
  "description": "Research a codebase area before implementation. Use when the user wants investigation, architectural context, prior art, or options before changing code.",
  "included_files": [],
  "name": "explore",
  "skill_md_contents": "---\nname: explore\ndescription: \"Research a codebase area before implementation. Use when the user wants investigation, architectural context, prior art, or options before changing code.\"\n---\n\n# /knowzcode:explore — Research before implementing\n\nInvestigate a topic and stop with findings and recommendations. Knowz MCP is optional and never blocks exploration.\n\n## Instructions\n\n1. Classify the exploration question and resolve any selected WorkGroup, capsule, reusable specification, and current phase **before vault retrieval, parallel delegation, or file writes**. Record the exact unresolved question and relevant subsystem boundaries.\n2. Load context progressively. Start with that selected WorkGroup/capsule and goal-relevant spec headings/`VERIFY:` criteria. If neither exists, search the topic first; read only the relevant project, architecture, spec, or prior-WorkGroup sections needed to answer the recorded question.\n3. Search the codebase for relevant files and patterns using targeted reads.\n4. If the topic spans 2 or more independently useful subsystems, parallelize read-only explorers within the active runtime's capacity. Do not create overlapping scopes and do not implement code in this mode.\n5. If the local evidence leaves a named prior-decision or convention question **and** Knowz MCP is available, use a targeted `mcp__knowz__search_knowledge` or `mcp__knowz__ask_question` call. Do not issue a broad baseline vault query. If tools are missing, continue with local evidence only.\n6. Produce the **Exploration Deliverable** in chat. Write it to `knowzcode/explore/<topic-slug>/summary.md` only when writes are authorized and durable exploration output is requested or materially useful for recovery.\n7. Do not implement changes unless the user explicitly asks to move into `/knowzcode:work` or `/knowzcode:fix`.\n\n## Parallel explorer dispatch\n\nEach explorer must:\n\n- Receive exactly one subsystem boundary. No two explorers share files.\n- Stay read-only — do not edit or implement code.\n- Default to `ephemeral` output (bounded findings in chat). Use `durable` files only when writes are authorized and recovery needs them.\n\nSkip parallel dispatch when the topic touches a single subsystem.\n\n## Exploration Deliverable\n\n```markdown\n# Exploration: {topic}\n\n## Current State\n{what exists today, with file:line citations}\n\n## Constraints\n{rules, conventions, dependencies that must hold}\n\n## Options\n1. {option name} — {one-paragraph description}\n2. {option name} — {one-paragraph description}\n\n## Risks\n{risk → mitigation, one per bullet}\n\n## Recommendation\n{one option from the list above, with rationale}\n\n## Suggested Next Skill\n{`/knowzcode:work` for full build or `/knowzcode:fix` for a single-file change — pick one}\n```\n\nThe `<topic-slug>` is the topic in 2-4 word kebab-case.\n"
}