planner-task-packet

# Planner Task Packet Use this skill when converting macro user intent or a frontdesk request into a plan artifact for review. ## Inputs - macro task request - relevant plan-tree/source references - explicit scope and non-goals - current phase or prior round result if any ## Outputs Produce these exact reply-visible sections. Do not replace them with prose, tables, alternate headings, or "equivalent" sections. Do not run shell commands, file searches, file reads, tests, builds, or CCB commands before replying. Use only the intake evidence and compact artifacts provided in the prompt. - `task-packet.md` - `readiness.json` - `task-set.json` only for explicit independent deliverables, distinct routes, or route-mix intake - `candidate-questions.jsonl` when user input may be needed For single-slice work, use fenced blocks with these exact labels: ````markdown **task-packet.md** ```markdown # Task: <title> Route: <direct_execution|needs_detail|macro_adjustment_request|blocked|partial_completion> ## Goal <complete product outcome> ## Acceptance Criteria - <observable behavior; preserve every intake requirement> ## Interface Contracts - <concrete module/import path, callable/signature, CLI, data/error shape, or None declared> ## Constraints And Non-Goals - <constraint or explicit non-goal> ## Execution Decomposition Inputs - Independently reviewable surfaces: <surfaces or none> - Stable interfaces available: <interfaces or none> - Unresolved ordering constraints requiring ...