capture_insight

Append classified insights to a dated markdown daily log.

2|1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/FourthWiz/claude_dev_workflow --skill capture-insight-fourthwiz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capture_insight
Source: https://github.com/FourthWiz/claude_dev_workflow/tree/main/dev-workflow/skills/capture_insight
Command: npx skills add https://github.com/FourthWiz/claude_dev_workflow --skill capture-insight-fourthwiz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often notice patterns, gotchas, or decisions while working but have no fast way to record them without breaking focus.

Core Features & Use Cases

  • Instant capture: Log an insight with a single command.
  • Automatic classification: The skill tags the insight as pattern, gotcha, decision‑rationale, surprise, or workflow‑friction and marks its promotion status.
  • Structured daily log: Appends a markdown entry to .workflow_artifacts/memory/daily/insights-<YYYY‑MM‑DD>.md for later review.
  • Use case: While refactoring, you notice that the API returns 200 on auth failure; invoking the skill records this gotcha for future reference.

Quick Start

Capture insight: the API returns 200 on auth failure.

Frequently Asked Questions about capture_insight

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

FAQPage Schema
How do I log a development insight to a daily scratchpad without interrupting my workflow?

To log a development insight to a daily scratchpad without interrupting your workflow, invoke the skill with a single command to append a structured markdown entry with classification and promotion flags to your daily insights file.

What is the best way to record workflow frictions and gotchas during coding?

The best way to record workflow frictions and gotchas during coding is to use an instant capture tool that automatically classifies the observation as a pattern, gotcha, or decision-rationale and appends it to a structured daily markdown log.

How does automatic classification work for daily developer notes?

Automatic classification for daily developer notes works by tagging each captured entry as a pattern, gotcha, decision-rationale, surprise, or workflow-friction, and marking its promotion status for later review.

Where are captured insights and decision rationales stored on disk?

Captured insights and decision rationales are stored as structured markdown entries appended to a daily log file located at `.workflow_artifacts/memory/daily/insights-<YYYY-MM-DD>.md`.

Do I need any dependencies to append structured markdown entries for daily observations?

You do not need any dependencies to append structured markdown entries for daily observations, as the skill operates independently to format and save your development logs.

When should I use an instant capture scratchpad over a standard note-taking app?

You should use an instant capture scratchpad over a standard note-taking app when you need to rapidly record development observations, decisions, or workflow frictions in a structured markdown format without breaking your coding focus.