Walk a contributor through proposing a change to the LeanCode AI plugins marketplace — tweaking an existing plugin, adding a new one, and opening a PR against `leancodepl/ai-plugins`. Use when the user invokes `/lean-contribute`, asks how to contribute, asks how to add a plugin, or wants to propose an improvement. Manual-only entry point — does not auto-fire.
📖 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.
🩺 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.
📋 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.
📊 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.
☕ BRIEFING: Morning catch-up — scan Slack, Jira, Fireflies, Gmail & Google Calendar to produce a scannable briefing of what happened since you last worked, plus a prep rundown of today's meetings with sourced context. Perfect for Monday mornings, after a holiday, or at the start of any workday. Triggers: "what did I miss", "catch me up", "morning briefing", "what happened while I was away", "what's new since Friday", "co się działo", "co powinienem wiedzieć", "zrób mi briefing", "poranny briefing", "co nowego", "nadgonię", "co pominąłem", "zacznijmy dzień", "prepare me for today's meetings", "what's on my calendar today", "jakie mam dziś spotkania", or any variation of wanting a situational summary before starting work. Also trigger when someone says "good morning", mentions it's Monday, or asks to "start the day". Scans all sources automatically — no project required. Output: complete digest of everything important, no fluff, only signal.
Explain what the `admin-app` plugin does and how to use it. Use when the user invokes `/admin-app-usage`, asks what this plugin covers, or needs help with React + Ant Design + TanStack Router admin-panel work (forms, tables, auth, intl, routing) using @leancodepl libs.