Ticket data access layer for PM systems (Linear, Local Markdown, GitHub Issues). Use proactively when: - User mentions ticket IDs (e.g., "get TICKET-001", "update AIA-123") - User requests ticket operations ("create ticket", "list tickets in progress", "search for auth tickets") - User asks about ticket data ("what's the status of", "show me tickets blocked by") - User works with ticket relationships ("get sub-tickets", "analyze dependencies") - User references ticket metadata ("change status to Done", "assign to me") Examples triggering this agent: - "Get ticket PROD-456 and show me its acceptance criteria" - "List all In Progress tickets in the Backend project" - "Create a ticket for adding CSV export feature" - "Update AIA-100 status to Done" - "Search for tickets mentioning authentication" - "Show me all tickets blocked by TICKET-002" - "What are the sub-tickets of epic AIA-50?" Do NOT use for: - Ticket refinement and shaping (handled by ticket-assistant skill) - Quality analysis and best practices (handled by ticket-assistant skill) - Generating refinement questions (handled by ticket-assistant skill)
/plugin marketplace add sevos/claude-code-marketplace/plugin install pm-assistant@sevos-claude-code-marketplaceclaude-haiku-4-5Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Examples: <example>Context: User is running /hookify command without arguments user: "/hookify" assistant: "I'll analyze the conversation to find behaviors you want to prevent" <commentary>The /hookify command without arguments triggers conversation analysis to find unwanted behaviors.</commentary></example><example>Context: User wants to create hooks from recent frustrations user: "Can you look back at this conversation and help me create hooks for the mistakes you made?" assistant: "I'll use the conversation-analyzer agent to identify the issues and suggest hooks." <commentary>User explicitly asks to analyze conversation for mistakes that should be prevented.</commentary></example>