gpd-record-insight

Record project learnings to .gpd/INSIGHTS.md with duplicate detection and git commits.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/MichaelsEngineering/get-physics-done-test --skill gpd-record-insight-michaelsengineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gpd-record-insight
Source: https://github.com/MichaelsEngineering/get-physics-done-test/tree/main/.agents/skills/gpd-record-insight
Command: npx skills add https://github.com/MichaelsEngineering/get-physics-done-test --skill gpd-record-insight-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Record project-specific learnings and patterns to the insights ledger to preserve institutional knowledge and avoid repeating mistakes.

Core Features & Use Cases

  • Automated recording of insights discovered during research using the record-insight workflow.
  • Duplicate detection, section mapping, and structured table entries into .gpd/INSIGHTS.md.
  • Integration with git commits to version-control insights for traceability and collaboration.

Quick Start

To record a new insight, trigger the record-insight workflow and provide the brief description of the insight and phase context.

Frequently Asked Questions about gpd-record-insight

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

FAQPage Schema
How do I record project insights and learnings to preserve institutional knowledge?

You record project insights by triggering the workflow to append structured table entries into the .gpd/INSIGHTS.md ledger, preserving institutional knowledge to avoid repeating mistakes.

How does duplicate detection work when adding research notes to an insights ledger?

Duplicate detection checks the existing .gpd/INSIGHTS.md ledger before adding new research notes, preventing redundant entries and ensuring your project insights remain distinct and manageable.

Can I version-control my insights ledger with git commits automatically?

Yes, the workflow integrates with git commits to version-control your insights ledger, providing traceability and collaboration when recording project-specific learnings and patterns.

What is the best way to map project insights into structured categories?

The best way to map project insights is using the workflow's section mapping feature, which categorizes learnings into structured table entries within the .gpd/INSIGHTS.md file automatically.

Do I need any specific dependencies or components to start recording project learnings?

No specific dependencies or components are required to start recording project learnings; the workflow reads your project state and updates the Insights file directly.

Why should I use a structured insights ledger instead of plain research notes?

A structured insights ledger provides duplicate detection, category mapping, and git version control, offering superior traceability and institutional knowledge preservation compared to plain research notes.