Verified:GitHub

insight-recording

Capture and review development insights from autonomous work transcripts.

2|Updated Jan 16, 2026

Search Tags:#deduplication #hook #review-workflow #marker-based #insight-recording #development-insights #code-transcript

Ready to run

npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill insight-recording

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: insight-recording
Source: https://github.com/MysMon/Spec-Workflow-Toolkit/tree/main/skills/workflows/insight-recording
Command: npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill insight-recording

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This protocol standardizes the capture and review of development insights generated during autonomous work, ensuring consistent markers and easy retrospection.

Core Features & Use Cases

Insight Markers: defines PATTERN, ANTIPATTERN, LEARNED, DECISION, and INSIGHT with examples for quick identification.
Automated extraction & workflow: the insight_capture hook reads transcripts, extracts assistant messages, filters content, deduplicates insights, and stores them as pending items for review via /review-insights.
Observability & lifecycle: supports status directories (pending, applied, rejected, archive) and enforces atomic write operations to ensure data integrity.

Quick Start

Enable the insight_capture hook to automatically extract marked insights from transcripts during autonomous work.

Frequently Asked Questions about insight-recording

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

FAQPage Schema

How do I automatically extract development insights from code transcripts?▼

To automatically extract development insights from code transcripts, enable the insight_capture hook to read transcripts, filter assistant messages, extract marked content, and deduplicate insights for review.

What markers should I use to tag development insights during autonomous work?▼

Use specific markers like PATTERN, ANTIPATTERN, LEARNED, DECISION, and INSIGHT to tag development insights during autonomous work for quick identification and standardized extraction.

How does the review workflow handle pending insights?▼

The review workflow stores extracted insights as pending items in dedicated status directories, allowing users to review them via /review-insights and move them to applied, rejected, or archive states.

Does this insight-recording approach enforce data integrity during the capture process?▼

Yes, the insight capture process enforces data integrity by applying atomic write operations when storing pending insights, ensuring safe transitions between status directories.

Can I use marker-based extraction for retrospective analysis of autonomous coding sessions?▼

Yes, marker-based extraction supports retrospective analysis by automatically filtering transcripts for defined markers, ensuring consistent tagging and easy retrospection of autonomous work sessions.