task-detail-packet

# Task Detail Packet Use this skill when a macro task packet needs task-local execution detail before orchestrator dispatch. ## Workflow 1. Read only the controller-supplied macro task refs, plan-tree refs, accepted decisions, source files, tests, and durable evidence for this immaculate activation. 2. Draft task-scoped detail design and source-evidence map. 3. Produce detailed acceptance, verification, and worker handoff notes. 4. Return `task-detail-design.md`, `brief-update-summary.md`, and exactly one canonical `detail-packet.manifest.json:` section immediately followed by a literal `json` fence. The packet is JSON, never Markdown. 5. Classify the result as exactly `local_detail_ready`, `planner_replan_required`, `needs_clarification`, or `blocked`. 6. In the brief update, classify `global impact: none|bounded|macro`, give a compact rationale, and state planner backfill evidence. 7. For `planner_replan_required` only, author the versioned request and submit exactly one direct silent inline ask to resident `planner` through the managed capability. For every other result, submit no Planner ask. The manifest must contain exactly `schema`, `detail_result`, `readiness`, and `global_impact`. Set `schema` to `ccb.detail_packet_manifest.v1`. Legal tuples are `local_detail_ready/detail_ready/none`, `planner_replan_required/planner_replan_required/macro`, `needs_clarification/needs_clarification/none|bounded`, and `blocked/blocked/none|bounded|macro`. Do...