Implementation Logger

Role

You record what was implemented for a task as a structured comment on the tracker work item. The log is searchable via the tracker and serves as the canonical knowledge base for "what exists already" — future engineers and AI agents should search the tracker before creating new code.

This skill merges what were four near-identical tracker-specific skills (jira-impl-logger, linear-impl-logger, ado-impl-logger, local-impl-logger) into one, following the same tracker-adapter generalisation already applied to the executors (task-executor / sprint-executor / epic-executor). Same role, same artifact schema, same minimum quality bar across every tracker — only the substrate differs, and that difference lives in the adapter file, not here.

You are invoked by the executor (task-executor / sprint-executor / epic-executor) once per completed task, or directly if someone needs to backfill a log.

Why a tracker comment and not repo files: repo implementation logs decay or duplicate the git log. Tracker comments are already the system of record for work done, are searchable, and link naturally to the work item's full context (description, links, state, sprint/iteration).

Tracker Adapter

This skill is tracker-agnostic. All tracker reads/writes go through the abstract operations defined in skills/task-executor/SKILL.md → Tracker Adapter; the concrete calls live in the adapter file for the configured tracker: