finishing-tasklisted

# Finishing Task Use this skill only when the user explicitly asks to close, finish, or complete a tracked task. It defines the completion quality gate; `task_finish` performs the task completion operation. Do not invoke this skill automatically at the end of implementation, review, or a session. ## Preconditions Before proposing or performing completion, confirm as applicable that: - requested work is actually implemented - relevant verification has passed - important review feedback is resolved or explicitly accepted - the stable brief, plan, and task notes accurately preserve useful history - durable docs and durable memory have been checked for required updates Do not mark a task complete because coding started, implementation seems done, or the user paused. Finishing the task record does not create a PR or close an external ticket; those remain separate human actions and require explicit user instruction. ## Done Standard The durable record must reflect what actually happened. Before finishing, explicitly check: - the outcome will factually describe what was delivered - existing architecture or durable docs need updates, or a durable doc is needed for a lasting change - a root cause, invariant, workflow trap, decision, or architecture fact should be promoted to `context-memory` Required durable documentation and durable memory updates are part of finishing, not optional follow-up. Search existing `.my-context/` documentation first; update the best existing docu