consolidate-notes

Promotes provisional research notes into stable canonical articles with supersedes audit trails.

3.9k|256|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/inkeep/open-knowledge --skill consolidate-notes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: consolidate-notes
Source: https://github.com/inkeep/open-knowledge/tree/main/packages/server/assets/skills/packs/knowledge-base/consolidate
Command: npx skills add https://github.com/inkeep/open-knowledge --skill consolidate-notes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams accumulate exploratory research notes that never get turned into a trusted source of truth, so future readers and AI agents cannot tell what was actually decided. This Skill converts decided research into a stable canonical article while preserving the evidence trail.

Core Features & Use Cases

  • Decision-confirmation gate: Blocks consolidation until the user confirms the actual decision, rejected alternatives, and rationale, preventing false certainty from being written down.
  • Canonical article generation: Writes a structured article under articles/ with Summary, Context, Decision, Rationale, Trade-offs, Alternatives considered, and Further reading sections, using status: stable frontmatter.
  • Supersedes audit trail: Adds supersedes: links in the new article and marks old research as status: deprecated with a superseded_by pointer, without deleting the original research.
  • Use Case: After the team decides to adopt Yjs for CRDT-based editing, consolidate three provisional research notes into one canonical article at articles/editor/crdt-architecture.md and deprecate the originals.

Quick Start

Ask the agent to consolidate the research notes on your chosen topic into a canonical article now that the team has made a decision.

Frequently Asked Questions about consolidate-notes

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

FAQPage Schema
How do I consolidate research notes into a canonical article?▼

Confirm the decision, alternatives, and rationale with the user first, then load all related research and sources, write a structured article with status stable frontmatter under the articles directory, and mark the old research as deprecated with a superseded_by pointer.

When should I not consolidate research into an article?▼

Do not consolidate when the team has not actually made a decision, since the output would falsely present open questions as settled. Also avoid consolidating without reading the underlying sources, and never delete the original research notes.

What frontmatter does a canonical knowledge base article need?▼

A canonical article needs title, description, type article, status stable, date, tags including article and canonical, and a supersedes list pointing at the research articles it replaces. The superseded research gets status deprecated and a superseded_by path.

Does consolidating delete the original research notes?▼

No, research articles are kept as historical context showing how the decision was reached. They are only edited to add status deprecated and a superseded_by field pointing to the new canonical article, preserving the audit trail.

What is the difference between research and canonical articles?▼

Research articles are exploratory and provisional, capturing options and open questions. Canonical articles use a direct, decided voice, state the chosen path with rationale and trade-offs, and serve as the standalone source of truth for future readers.