agent-log-writing

name	agent-log-writing
description	Write agent_logs entries correctly in KanbAgent. Activates when an agent needs to log an action, when completing a task, starting a session, or when agent_logs entries are missing. Triggers on "log this", "insert agent_log", "add a log", or any task_started/task_done/session_end event.

Agent Log Writing Skill

Correct insertion of agent_logs entries for KanbAgent. Mandatory at minimum for 2 events per task.

Mandatory Events (minimum per task)

Event	When	level
task_started	Right after UPDATE tasks SET status='in_progress'	info
task_done	Right before UPDATE tasks SET status='done'	info
session_start	In agent-session-starting Step 1b (all agents)	info

Additional Events (situational)

Event	When	level
session_start	review/devops: start of session	info
task_archived	review: after archiving a ticket	info
task_rejected	review: after rejecting a ticket	warn
task_created	review/task-creator: after creating a ticket	info
session_end	review/devops: just before closing session	info

SQL Pattern

INSERT INTO agent_logs (session_id, agent_id, level, action, detail, created_at) VALUES (<session_id>, <agent_id>, '', '', '', CURRENT_TIMESTAMP);

Concrete Examples

-- task_started INSERT INTO agent_logs (session_id, agent_id, level, action, detail, created_at) VALUES (42, 3, 'info', 'task_started', 'T912: feat(ipc): add agent-groups handler', CURRENT_TIMESTAMP);

-- task_done INSERT INTO agent_logs (session_id, agent_id, level, action, detail, created_at) VALUES (42, 3, 'info', 'task_done', 'T912: feat(ipc): add agent-groups handler', CURRENT_TIMESTAMP);

-- review: task_archived INSERT INTO agent_logs (session_id, agent_id, level, action, detail, created_at) VALUES (55, 4, 'info', 'task_archived', 'T912 archived: implementation correct', CURRENT_TIMESTAMP);

-- review: task_rejected INSERT INTO agent_logs (session_id, agent_id, level, action, detail, created_at) VALUES (55, 4, 'warn', 'task_rejected', 'T912 rejected: missing input validation in handler', CURRENT_TIMESTAMP);

-- review: session_end INSERT INTO agent_logs (session_id, agent_id, level, action, detail, created_at) VALUES (55, 4, 'info', 'session_end', 'Session done. Archived:2 Rejected:1', CURRENT_TIMESTAMP);

Hard Rules

• session_id and agent_id are NOT NULL, always populate them
• files = NULL unless the action is specifically about a file
• Never omit task_started + task_done, review will flag missing logs
• For chained tasks (multiple tickets in one session): one pair per ticket
• Use heredoc syntax for detail strings containing backticks or quotes

Chained Task Pattern

When chaining multiple tasks in one session without /clear:

-- End of task 1 INSERT INTO agent_logs (...) VALUES (, , 'info', 'task_done', 'T910: ...', CURRENT_TIMESTAMP); UPDATE tasks SET status='done' ... WHERE id=910;

-- Start of task 2 (immediately after) INSERT INTO agent_logs (...) VALUES (, , 'info', 'task_started', 'T911: ...', CURRENT_TIMESTAMP); UPDATE tasks SET status='in_progress' ... WHERE id=911;

Same session_id throughout, only task_id changes.