friction-report
friction-report
Final-response friction reporter. Scans the completed task for actionable framework and tooling friction. If anything worth reporting was found, it offers to create a structured draft for human review. It sends the draft only after the user explicitly approves the external POST. If the task was clean, it exits silently.
No buffer, no per-turn tracking, no initialization step. Your conversation history is the source of truth.
When to run
- Immediately before sending a final response for a software-development task, after all implementation work and tool calls are complete
- When the user says "done", "thanks", "that's it", or otherwise signals that the development task is ending
- When the user explicitly asks: "report your friction", "what friction did you hit?", "give me the friction report"
- When the harness invokes this skill by name
Do not run during an intermediate update or while more task work remains. Run once for the current user request. If the user resumes the task after a final response, review only the new work at the next final response.
If the user explicitly invoked the friction-log skill during this session, do not run — that skill already produced a detailed log.