friction-log

Classify friction observations by theme and log entries via the friction log CLI.

3|1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/netguy204/vibe-engineer --skill friction-log
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: friction-log
Source: https://github.com/netguy204/vibe-engineer/tree/main/.agents/skills/friction-log
Command: npx skills add https://github.com/netguy204/vibe-engineer --skill friction-log

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture friction points quickly for later pattern analysis and improvement across projects.

Core Features & Use Cases

  • Capture a friction point with a concise title, description, and impact.
  • Map friction to existing themes or propose new ones to enable structured analysis.
  • Generate and reference an entry ID to track progress and follow-up.

Quick Start

Describe the friction you observed and run the friction log command to create a new entry.

Frequently Asked Questions about friction-log

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I log UX friction points for pattern analysis during product development?

To log UX friction points, you provide a title, description, and impact observation, which generates a tracked entry ID mapped to existing or new themes in docs/trunk/FRICTION.md for structured pattern analysis.

How does friction logging classify observations by theme?

Friction logging classifies observations by mapping each captured entry to existing themes or proposing new themes, enabling structured pattern analysis across product development and UX research.

What information do I need to capture a friction point?

To capture a friction point, you need a concise title, a description of the observed friction, and its impact, which the system logs with an entry ID for tracking progress and follow-up.

Do I need the ve friction log CLI to track product feedback?

Yes, the ve friction log CLI is required to run the command that creates new friction entries, maps them to themes, and generates entry IDs for tracking product feedback.

Can I use friction logging for engineering reviews?

Yes, friction logging is applicable during engineering reviews to log friction entries and associate them with existing or new themes for structured analysis and follow-up.

What is the best way to track friction entries across projects?

The best way to track friction entries is logging them with a title, description, and impact, then mapping each to themes in docs/trunk/FRICTION.md to generate entry IDs for cross-project pattern analysis.