📖 PMO-PROJECT PLUGIN: Explains what this plugin covers, when to use each skill, and what connectors are required. Trigger when someone asks "what can this plugin do", "how do I use pmo-project", "what skills are available", or when they seem unsure which skill to reach for. Also trigger proactively at the start of a new project context to help the user set up correctly.

📖 CONFLUENCE: Sync decision log — scan Fireflies, Slack & Jira for new decisions, then propose precise additions and status updates to a project's Confluence Decision Log. Use whenever asked to update, review, or audit a project's decision log. Triggers include: "update the decision log", "check what's new for the decision log", "scan for decisions since last update", "what decisions have been made recently", "sync the decision log", "audit the decision log", "zaktualizuj decision log", or any time new decisions or major updates on a project need to be captured in Confluence. Proposes all changes with full rationale for review — nothing is written to Confluence without explicit approval.

🎫 JIRA: Create tickets — generate well-structured Jira tickets (Task, Story, Bug, Epic + Sub-tasks) for any project based on Slack conversations, Fireflies meeting transcripts, manual notes, or existing Jira tickets. Shows a draft for approval, then creates tickets directly in Jira after confirmation. Trigger whenever asked to "create a ticket", "generate a user story", "add to backlog", "log a bug", "break this into tickets", "create an epic", "dodaj do backloga", "stwórz ticket", or when a clear scope of work appears in conversation without tickets. Also trigger proactively when feature descriptions or problem statements appear that clearly need Jira tickets but none have been created yet.

🔍 JIRA: Shadow Refinement — act as a sceptical Senior Developer to stress-test a User Story before it goes to the team. Finds edge cases, flags missing error handling, and exposes gaps in business logic so you arrive at Grooming/Refinement with answers, not questions. Trigger whenever someone says "attack my user story", "stress-test this ticket", "review before grooming", "play devil's advocate", "shadow refinement", "what would a senior dev say about this", "find edge cases", "what am I missing in this story", "check my ticket before refinement", or when a user story or ticket draft appears in the conversation and the user signals they want pre-meeting preparation. Also trigger proactively when someone pastes a user story or Jira ticket and asks for feedback.

📅 MEETINGS: Prep — full multi-source brief before any meeting. Finds the meeting in Google Calendar, then scans Fireflies, Slack, Jira, Gmail & Confluence to produce a structured prep card: what was decided last time, recent threads, suggested talking points, attendee context, and open blockers. Use whenever asked to prepare for a meeting by name or timing. Triggers include: "prepare me for [meeting]", "prep for my call with [person/client]", "I have a meeting with X in 30 minutes", "what should I know before [meeting]", "przygotuj mnie na [spotkanie]", "mam call za 30 minut", "co powinienem wiedzieć przed spotkaniem z [klientem]", "przygotuj mnie na rozmowę z [osobą]", "brief me before [meeting]", or any variation of wanting context before a specific meeting. Also trigger proactively when someone mentions an upcoming meeting or call and seems to want to be prepared. Always ask to confirm which meeting before scanning if there's any ambiguity.

🩺 PROJECTS: Health check — instant multi-source snapshot of any project's velocity, blockers, decisions, and open threads. Use whenever anyone asks about the current state, health, or status of a specific project — especially ad-hoc or before a client call. Triggers include: "jaki jest stan [projektu]", "jak idzie [projekt]", "co słychać na [projekcie]", "zrób health check [projektu]", "sprawdź co się dzieje w [projekcie]", "mam call z klientem — przypomnij mi co się dzieje", "co powinienem wiedzieć przed spotkaniem z [klientem]", "czy coś blokuje [projekt]", "what's the status of [project]", "catch me up on [project]", or any variation of a quick project situational awareness check. Also trigger proactively when a Jira project key, Slack channel name, or client name is mentioned with a follow-up implying a need for current context. Scans Fireflies, Slack, Jira, and Confluence in parallel and returns a structured snapshot.

📊 REPORTS: Generate client-facing status updates — auto-scan Fireflies, Slack, Jira & Gmail to produce a short, precise, ready-to-send project status update for any cadence. Use whenever asked to prepare or generate a status update for any client project. Triggers include: "prepare the weekly update", "bi-weekly update", "sprint summary", "sprint status update", "end of sprint report", "monthly status", "monthly summary for [client]", "status update for [person]", "napisz weekly update", "napisz sprint summary", "co się działo w tym tygodniu", "podsumowanie sprintu", "miesięczny update", "dwutygodniowy update", or any variation of summarising a period's progress for a client or stakeholder. Auto-scans all live sources and produces a short, precise, client-ready text covering dev progress, design progress, decisions made, and blockers. Output is shown in chat for review and copy — never posted automatically.

📋 SETUP: Create a Claude Project custom instruction — guides the user section by section to produce a complete, structured project instruction ready to paste into Claude.ai Projects. Use whenever asked to "create a project instruction", "set up a Claude project", "write project context for Claude", "help me configure a new project", "stwórz instrukcję projektu", "skonfiguruj projekt w Claude", "napisz custom instruction dla projektu", "zdefiniuj kontekst projektu", or any variation of wanting to define a new project workspace in Claude. Works for any software delivery project. Runs section by section: language → your role → project identity → what you're building → users & markets → tech stack → team → client stakeholders → other stakeholders → links → slack channels → communication rules → upsell signals → key dates. Everything is optional — user decides what to include. At the end, outputs a ready-to-paste instruction and explains how to add it in Claude.ai.