starting-tasklisted

# Starting Task Use this skill when new work arrives and you need to decide whether it should become a tracked task. ## Purpose This skill decides when durable task tracking is worthwhile. `pi-task` provides direct task-file operations; `context-task` defines document-quality policy. ## When To Use This Skill Use this skill when: - the user asks to start or track a task - a request is substantial enough to benefit from durable tracking - the work will likely need research, planning, review, or multiple sessions Usually do not use it for tiny one-shot edits, purely informational questions, or throwaway exploration. ## Decision Rule Create a tracked task when one or more of these is true: - the work is multi-step or spans multiple files - the work may take multiple sessions - the work benefits from explicit notes, planning, or completion history - the user explicitly asks to track it If none apply, proceed without task initialization. ## Start The Record Use `task_start` to create the record. Supply a concise title and all stable information known from the request: ID when one is supplied, ticket reference, focused goal, concrete acceptance criteria, and created date when known. Prefer a safe inferred first draft over unnecessary follow-up questions. Generate a concise title, focused goal, and concrete acceptance criteria when the user did not provide them; ask only when the request is too ambiguous for a safe default. `task_start` creates the active task record.