Update to taskplane

{
  "name": "tp-help",
  "description": "Explain Taskplane capabilities, commands, and existing workflow state when the user asks for help. Does not initialize or activate a workflow.",
  "included_files": [],
  "skill_md_contents": "---\nname: tp-help\ndescription: Explain Taskplane capabilities, commands, and existing workflow state when the user asks for help. Does not initialize or activate a workflow.\n---\n\n# Taskplane help\n\nAnswer the user's question directly. Use only the relevant installed documentation\nor a command's `--help` output. Do not run onboarding, inventory tools, activate a\ncontract, or render a setup dashboard just to explain the product.\n\nOrdinary code review uses native tools and [engineering](../tp-engineering/SKILL.md).\nThe orchestrator prepares delivery; humans accept checkpoints by default.\nExplicit user instructions can authorize run-bound automatic phase approvals. Hooks\nseparate mandatory workflow refusals from advisory usage. The default native_workflow\nprofile uses local state and observed human provenance. Host-wide protections are\nunavailable; protected_host requires a verified owner. Native permissions remain separate. Use `flow report`\nfor human decisions, recorded milestones and available token usage.\nFor actual setup or a concrete installation failure, consult\n[onboarding](../../docs/onboarding.md) and [CLI reference](../../docs/cli-reference.md).\nExplain only the requested concept; load no full manuals or hook manifests as a tour.\nFor a question about phase policy, consult [the shared flow](../tp-go/references/shared-flow.md).\n\nExplain that plugin installation, hook trust, phase acceptance and host tool permissions\nare separate. Automatic mode requires explicit additional instructions; show a concise\nexample and how to return to manual mode when requested.\n"
}