Update to taskplane

{
  "description": "Define the requested product outcome, scope, acceptance criteria, and material dependencies without changing implementation.",
  "included_files": [],
  "name": "tp-product",
  "skill_md_contents": "---\nname: tp-product\ndescription: Define the requested product outcome, scope, acceptance criteria, and material dependencies without changing implementation.\n---\n\n# Define what should be built\n\nBefore substantive work, resolve this installed plugin's runtime and run\n`flow activate --workspace <checkout> --phase tp-product --request-reference <actual-user-request>`.\nInspect `flow report`: reuse the matching active visit or initialize the appropriate\nscoped run before continuing. This requirement includes standalone work and resumed\nstages; loading a skill alone grants no phase approval. See the shared flow for\nbootstrap, native dashboard handoff and legitimate user waits.\n\nUse the user's request and relevant existing product context. State the problem,\nintended user behavior, scope, acceptance criteria, material dependencies, and\nunresolved decisions. Reuse settled answers and keep the artifact proportionate\nto the task. Write a document when requested or useful for downstream work.\n\nFollow [the shared flow](../tp-go/references/shared-flow.md) even for Product-only\nwork. Start/reuse the relevant run at Product, inspect the dependency graph and\nsource decomposition, record a proportionate task decomposition, attach criteria,\nand render the shared dashboard. If Engineering initiated the work, use its findings\nand evidence to define the problem and acceptance criteria; preserve finding IDs\nand prior decisions rather than restarting discovery.\n\nDistinguish product readiness from delivered implementation. A completed spec\nmeans the outcome is defined; it does not mean the product has been built or\nvalidated. Surface only questions that materially affect the result.\n\nUse native tools for inspection and document authoring. Product-only work does\nnot authorize implementation. For an already authorized delivery, return the\ncriteria and dashboard for Product checkpoint acceptance under the shared policy before\ncontinuing through [delivery](../tp-go/SKILL.md). Reuse a valid prior acceptance.\nA completed document or telemetry receipt cannot authorize advancement.\n\n## Shared delivery state\n\nStandalone and delivery Product use the same run, task decomposition, dependency\ngraph and dashboard defaults. Return evidence to that run; the root orchestrator\nowns stage advancement and respects Product-only scope.\n\nThe shared flow defaults to explicit human approval at each phase checkpoint.\nA recorded, explicit run policy may authorize automatic approval as described there. Use\nthe dependency graph with source component decomposition, task DAG and shared\ndashboard throughout. Unsupported host authority must be reported, never bypassed.\n\n## Consume bounded context\n\nAfter activation, start, advancement or resumption, use the installed runtime's\n`flow context --workspace <checkout> --run <run>` and consume the returned\nhandoff with `--consume <handoff-ref-sha256>`. Use `--task <current-task-id>` for\nfocused work. Read every omitted required input using `--read <ref-sha256>`;\nfollow index children and page cursors until all required bodies are returned.\nA fresh consumer receives these bodies, scoped source and relevant findings;\ndo not copy the predecessor conversation or tool history into its instructions.\nNo context operation authorizes dispatch or a phase transition.\n\nFor phase submission, obtain a current whole-phase receipt (without `--task`)\nand include the returned `context_receipt` object in the phase output. Renew it\nafter source, scope, revision or accepted input changes. New bounded/v1 runs\nreject missing, partial, foreign or stale receipts. Legacy runs keep their\noriginal evidence contract. A receipt proves returned data, not model attention.\n\nRoutine command summaries preserve the current gate and reference full details.\nExpand specific references when needed; request `--full` only for a consumer that\nrequires the complete legacy report. Native dashboards retain complete evidence.\nReuse a prior passing check only when its verification record matches current\nsource/dependency, tests, runtime, environment, command and criteria fingerprints.\nRetain failed/unknown results and findings; reuse never transfers approval.\n\n## Scoped native workers\n\nWhen authorized, use the installed native dispatch protocol: root prepares a run-bound\ntask grant, the observed worker claims its identity and consumes its own task context,\nand root verifies the joined result before satisfying dependencies. Fill observed\ncapacity with useful independent work; two is only the minimum live acceptance test.\nWorkers return evidence and cannot operate root phase controls or publish task definitions.\nRequire actual loaded-runtime and native execution evidence for live claims.\n"
}