context-recording

Record architectural decisions, failures, and meeting outcomes with automated IDs and semantic embedding.

3|1|Updated Feb 12, 2026

Search Tags:#documentation #knowledge management #adr #decision logging #meeting notes #incident management

Ready to run

npx skills add https://github.com/standard-librarian/context-engineer --skill context-recording

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: context-recording
Source: https://github.com/standard-librarian/context-engineer/tree/main/skills/user/context-recording
Command: npx skills add https://github.com/standard-librarian/context-engineer --skill context-recording

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of capturing and organizing critical organizational knowledge, ensuring that decisions, failures, and meeting outcomes are systematically recorded and accessible for future reference and learning.

Core Features & Use Cases

Record Architectural Decisions (ADRs): Document technology choices, patterns, and infrastructure decisions.
Log Failure Incidents: Capture details of errors, root causes, and resolutions for learning and prevention.
Document Meeting Outcomes: Record key decisions and action items from discussions.
Automated ID Generation: The system automatically assigns unique IDs (e.g., ADR-xxx, FAIL-xxx) for easy referencing.
Semantic Search Integration: Recorded data is embedded for semantic search, allowing agents to find relevant context.

Quick Start

Use the context-recording skill to document the decision to use PostgreSQL for the primary database, including the title, decision, and context.

Frequently Asked Questions about context-recording

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

FAQPage Schema

How do I record architectural decisions and log failures for knowledge management?▼

To record architectural decisions and log failures, use structured endpoints for ADRs and incidents that automatically generate unique IDs and apply semantic embedding for future searchability.

What is the best way to document meeting outcomes and capture incident resolutions?▼

Documenting meeting outcomes and capturing incident resolutions requires structured recording endpoints that store key decisions, action items, and root causes while generating semantic embeddings for context retrieval.

Can I automate decision logging through event-driven triggers like deployments and errors?▼

Yes, automated decision logging supports event-driven triggers to capture errors and deployments, alongside standard CRUD-based recording methods for diverse data capture needs.

Does automated ID generation work for both meeting notes and failure incident logs?▼

Automated ID generation works for meeting notes and failure incident logs by systematically assigning unique identifiers like FAIL-xxx or ADR-xxx for easy referencing.

How do architectural decision records integrate with semantic search?▼

Architectural decision records integrate with semantic search by embedding the recorded data, allowing agents to find relevant context and historical decisions during future tasks.

Do I need a specific environment setup to capture failure incidents and meeting outcomes?▼

Capturing failure incidents and meeting outcomes requires no external dependencies, utilizing internal scripts and references to facilitate systematic knowledge management within the Context Engineering System.