friction-report

End-of-session friction reporter. Scans the conversation you just had for build failures, doc gaps, SDK surprises, misleading errors, and training-data fallbacks. If anything worth reporting was found, drafts a structured report for human review. If the session was clean, exits silently.

No buffer, no per-turn tracking, no initialization step. Your conversation history is the source of truth.

When to run

• At the end of a dev session — when the user says "done", "thanks", "that's it", or when the task is clearly complete
• 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

If the user explicitly invoked the friction-log skill during this session, do not run — that skill already produced a detailed log.

Payload

Matches the same schema the visualizer validates. All top-level fields: