Technical conversation log with factual accuracy and precision tailored specifically for DEVELOPER and ENGINEER profiles. Provides systematic guidance for capturing decisions, outcomes, and next steps. Use when user asks to create technical conversation logs for reviews, architecture discussions, or implementation sessions.
View on GitHubJanuary 21, 2026
Select agents to install to:
npx add-skill https://github.com/axivo/claude/blob/main/plugins/conversation-log/skills/conversation-log/SKILL.md -a claude-code --skill conversation-logInstallation paths:
.claude/skills/conversation-log/# Conversation Log Technical session documentation with factual accuracy and precision. Captures decisions, outcomes, and next steps for technical work, reviews, architecture discussions, and implementation sessions. > [!IMPORTANT] > Framework observations provide complete document structure and file paths. Always read the conversation log template instructions specified in framework observations before creating conversation logs. ## Skill Methodology Systematic documentation for technical sessions with factual accuracy and precision. Extends DEVELOPER and ENGINEER profiles with technical writing guidance for session documentation. > [!IMPORTANT] > The skill embodies Observe → Capture → Document → Archive > > - Process skill instructions systematically > - Take time to read, understand, and apply each section's logic carefully > - Rushing past documented procedures causes **fatal** execution errors ### Documentation Principles - **Factual Accuracy** - Document what actually happened, not idealized versions - **Technical Precision** - Capture specific decisions, paths, and implementation details - **Editorial Autonomy** - Write independently without performative language - **Outcome Focus** - Emphasize completed work and identified next steps - **Technical Context** - Structure content for technical reference and continuation ### Systematic Approach Documentation quality improves through consistent application of these principles: - **DO read template first** - Framework observations specify structure and requirements - **DO document while working** - Capture technical details as they emerge - **DO write factually** - Record actual outcomes without editorial enhancement - **DO NOT defer documentation** - Session details fade quickly from working memory - **DO NOT idealize outcomes** - Document problems and blocks honestly ## Technical Writing Style Apply technical writing standards to all conversation log sections. ### Style Guidelines - **Declarative**