context-tasklisted

# Context Task Use this skill with the task workflow skills to keep one tracked work item's durable record useful and accurate. It defines document semantics and agent judgment; `pi-task` provides direct task-file operations. Use it together with `writing-plans`, `executing-plans`, `subagent-driven-development`, and `requesting-code-review`. Use `context-memory` for durable knowledge that belongs across tasks. ## Task Documents A tracked task has these durable documents: - `task.md` — stable task brief: title, ID, ticket, created date, status, goal, acceptance criteria, and relevant PR links. - `notes.md` — append-only task-specific research, discoveries, decisions, dead ends, constraints, and open questions. - `plan.md` — the current coherent, rewriteable execution plan. - `outcome.md` — a concise factual summary of what happened, written only for a user-directed completed task. Use `task_read` to read task documents by task ID. It reads the selected document directly. Use `task_list` to find task IDs or filter tasks by status. ## Document Quality Rules ### Stable brief (`task.md`) Keep the goal and acceptance criteria concrete. Update stable brief sections when the task meaning changes or a relevant ticket/PR reference becomes available. Use `task_write` (`document: "task"`) to rewrite the full stable brief while preserving the sections that remain accurate. Do not use it for transient progress notes. ### Notes (`notes.md`) Keep notes append-only under a date hea