starting-tasklisted

# Starting Task Use this skill when new work arrives and you need to decide whether it should become a tracked task. ## Why This Skill Exists This skill is the entry point into the current workflow for tracked work. It does not replace `context-task`. Instead, it decides when task tracking is worth creating and then initializes the task record correctly so the rest of the flow has a durable place to work from. ## When To Use This Skill Use this skill when: - the user asks to start a task - a request looks substantial enough to benefit from durable tracking - the work will likely need research, planning, review, or multiple sessions - the work should leave a durable record in `.my-context/tasks/` Usually do not use this skill for: - tiny one-shot edits - purely informational questions - throwaway exploration with no need for durable task state ## Decision Rule Create a tracked task when one or more of these is true: - the work is multi-step - the work will likely span 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 of those are true, proceed without task initialization. ## Relationship To Other Skills - `starting-task` decides whether to create tracked work - `context-task` defines the task folder, files, and `state.json` rules - `context-memory` handles durable cross-task knowledge - `writing-plans` uses the task record to produce `plan.