Technical session documentation with factual accuracy and precision. Provides systematic guidance for capturing decisions, outcomes, and next steps. Use when user asks to create conversation logs for technical work, reviews, architecture discussions, or implementation sessions.
/plugin marketplace add axivo/claude/plugin install axivo-framework@axivo/claudeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
LICENSETechnical 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.
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 quality improves through consistent application of these principles:
Apply technical writing standards to all conversation log sections.
src/auth/middleware.ts modified" not "authentication code updated"Include these technical details when documenting sessions:
Technical sessions typically use these tag patterns:
#infrastructure, #systems, #software, #architecture, #operations#review, #debugging, #implementation, #refactoring, #design#completed, #blocked, #research-needed, #follow-up-requiredEach session type has specific focus areas that guide documentation content. Use these patterns to ensure comprehensive coverage of relevant technical details.
Focus on:
Focus on:
Focus on:
Focus on:
Before creating a conversation log:
A well-documented session includes:
[!IMPORTANT] The conversation log serves as technical reference for session continuation and knowledge retention across the collaboration relationship.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.