generate-tasklisted

# Generate Task Document Decompose a plan document into fine-grained, directly executable tasks by reading the actual codebase. Three phases: Analyze, Confirm, Verify. ## Trigger Phrases Use this skill when the user explicitly asks to **create a task document from a plan**, using phrases like: "generate tasks", "break down tasks", "create task document", "decompose the plan", "拆任务", "生成任务", "任务分解", "帮我拆任务", or invokes `/kenspc-task` directly. Avoid triggering this skill when the user: - Asks to create a plan (use generate-plan instead). - Asks to implement tasks (use task-implement instead). - Wants to discuss task priorities without generating a document. - Asks a question about an existing task document. ## Quality bar A useful task document covers every plan Implementation Step, gives each task a single clear objective and concrete acceptance criteria (no vague language like "as appropriate", "if needed", "properly"), and orders tasks so that no task starts before its dependencies are DONE. ## Prerequisites - A plan document generated by generate-plan (or following the same structure). - A project with actual code to analyze. ## Arguments $ARGUMENTS format: PLAN_PATH [PHASE] [CUSTOM_INSTRUCTIONS] - PLAN_PATH: path to the plan document (e.g., docs/plans/notification-plan.md). - PHASE: optional, specifies which phase(s) to decompose (e.g., "Phase 1", "Phase 1 and 2"). If omitted, decompose the entire plan. - CUSTOM_INSTRUCTIONS: optional free-text that narrows s