debrief

To log agent inefficiencies, use a self-scanning process that reads existing pain-point files, detects friction from the session context, deduplicates against prior entries, and appends open issues in markdown format for future improvement.

Workflow friction tracking covers redundant tool usage, predictable failures, redundant passes, process awkwardness, skill overhead, and specification gaps that degrade agent reliability, speed, and process clarity during task execution.

Session analysis prevents duplicate friction entries by comparing newly detected friction points against existing pain-point records before appending, ensuring only open, non-redundant issues are logged for actionable tracking.

Yes, end-of-task documentation can be automated through self-scanning. The agent reads its own session context to identify friction points and records them without asking the user, appending open issues to the workflow pain-points file.

Agent debriefing requires no external dependencies or components. It operates as a standalone skill that reads existing markdown pain-point files and self-scans session context to append friction logs.

Run a workflow debrief after finishing any non-trivial task where reliability, speed, or process clarity may have degraded. This captures friction points while session context is fresh for future process optimization.