knowledge

Extract topics, decisions, and changes from Amp threads into project documentation.

172|136|Updated Feb 18, 2025
One-click install
npx skills add https://github.com/hoangnb24/storage --skill knowledge-hoangnb24
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge
Source: https://github.com/hoangnb24/storage/tree/main/knowlegde
Command: npx skills add https://github.com/hoangnb24/storage --skill knowledge-hoangnb24

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual effort of capturing decisions, topics, and changes from Amp threads and updating project docs accordingly.

Core Features & Use Cases

  • Knowledge extraction: Pulls key topics, decisions, and changes from threads.
  • Documentation sync: Updates AGENTS.md and related docs to reflect latest work.
  • Use Case: After finishing an epic, run this Skill to summarize thread history and align documentation across the project.

Quick Start

Use the knowledge skill to extract information from recent Amp threads and refresh the project's documentation from thread history.

Frequently Asked Questions about knowledge

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

FAQPage Schema
How do I extract knowledge and decisions from Amp thread history?

To extract knowledge from Amp thread history, this Skill uses a six-phase pipeline to pull key topics, decisions, and changes, then applies them directly to your project documentation. It automates the capture of recent work from threads.

How do I keep AGENTS.md updated with recent project changes?

You can update AGENTS.md with recent project changes by running this Skill to sync documentation from thread history. It reconciles extracted thread topics and decisions directly into your existing project docs.

Can I automatically summarize thread history and map it to project documentation?

Yes, you can automatically summarize thread history and map it to project documentation. The Skill maps extracted topics through a Discover, Extract, Verify, Map, Reconcile, and Apply pipeline to align docs with recent work.

What is the best way to sync epic documentation after finishing a project phase?

The best way to sync epic documentation after finishing a project phase is to use this Skill. It extracts decisions and changes from Amp threads, summarizing the thread history to align documentation across the project.

Does this documentation sync tool require any external dependencies?

No, this documentation sync tool requires no external dependencies to operate. It uses built-in tools like find_thread, read_thread, Grep, and edit_file to locate, extract, and apply thread knowledge to your docs.

What limitations exist when mapping extracted topics to existing project docs?

A key limitation when mapping extracted topics is ensuring accurate reconciliation with existing project docs. The Skill relies on the Verify and Reconcile phases to prevent conflicts, but complex thread histories may require manual review.