Update to taskplane

{
  "name": "tp-design",
  "description": "Design how a requested change should work before implementation, with proportionate alternatives, dependencies, trade-offs, and validation.",
  "included_files": [],
  "skill_md_contents": "---\nname: tp-design\ndescription: Design how a requested change should work before implementation, with proportionate alternatives, dependencies, trade-offs, and validation.\n---\n\n# Design the requested change\n\nBefore substantive work, resolve this installed plugin's runtime and run\n`flow activate --workspace <checkout> --phase tp-design --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\nInspect the relevant requirements and current code with native tools. Reuse\nexisting decisions. Describe the smallest workable approach, the interfaces and\ndata it changes, meaningful alternatives, risks, and how success will be tested.\nUse a diagram or mockup only if it makes a decision easier.\n\nFollow [the shared flow](../tp-go/references/shared-flow.md) for standalone Design\nand delivery alike. Start/reuse the relevant run at Design, inspect dependencies\nand source decomposition, attach the design task decomposition and evidence, and\nrender the shared dashboard. Reuse Product criteria or Engineering findings.\n\nKeep detail proportionate to the change. Do not require a lens quota, signed\nartifact, or separate designer. The root\norchestrator owns the handoff and assesses readiness from the actual design.\nA design-only request ends with the design; it does not authorize implementation.\nPresent the design and resolve this checkpoint through the shared approval policy before continuing\nvia [delivery](../tp-go/SKILL.md). Reuse an existing valid Design approval.\n\nRecord useful milestones and refresh the shared dashboard throughout Design.\nMissing observations are advisory and do not invalidate the design.\n\n## Shared delivery state\n\nStandalone and delivery Design use the same run, task decomposition, dependency\ngraph and dashboard defaults. Return evidence to that run; the root orchestrator\nowns stage advancement and respects Design-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"
}