---
name: pmo-project-usage
description: >
  📖 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.
---

# pmo-project plugin — usage guide

## What this plugin is for

`pmo-project` gives a PM or tech lead an AI assistant that knows a specific software project
inside out — pulling context from Jira, Confluence, Slack, Fireflies, and Google Calendar
in real time instead of asking you to repeat yourself.

All skills in this plugin work **per project**. You'll get the most value when you tell
Claude your project name (or Jira key) once at the start of a conversation, or better yet —
add a short project prompt to your Claude project with the key constants (see Setup below).

---

## Skills in this plugin

| Skill | Trigger phrase examples |
|---|---|
| `/meetings-prep` | "prepare me for my call with [client]", "brief me before the refinement" |
| `/jira-create-ticket` | "create a ticket for this", "add to backlog", "break this into stories" |
| `/jira-shadow-refinement` | "stress-test this user story", "attack my ticket before refinement" |
| `/projects-health-check` | "what's the status of [project]?", "catch me up on [project]" |
| `/confluence-sync-decision-log` | "update the decision log", "sync decisions since last week" |
| `/reports-client-status` | "write the weekly update for [client]", "generate the sprint summary" |

---

## Required connectors

All skills in this plugin require the following MCP connectors to be active in Claude:

| Connector | Used by |
|---|---|
| **Atlassian** (Jira + Confluence) | all skills that touch tickets or docs |
| **Slack** | meetings-prep, projects-health-check, reports-client-status |
| **Fireflies** | meetings-prep, projects-health-check |
| **Google Calendar** | meetings-prep |
| **Gmail** | meetings-prep |

---

## Setup — project prompt (recommended)

Skills work without a project prompt, but they'll ask fewer questions and run faster if
you add a short block of constants to your Claude project instructions:

```
## Project context

- Project: <your project name>
- Jira project key: <KEY>
- Atlassian Cloud ID: <yourorg.atlassian.net>
- Slack channels:
  - main: <channel-id>        # e.g. C01234ABCDE
  - client-facing: <channel-id>
- Confluence space key: <SPACE>
- My email: <your@email.com>
```

**Why channel IDs instead of names?** Claude resolves them without an extra search call,
which makes every Slack-heavy skill noticeably faster and more reliable.

---

## Example prompts to try

```
/meetings-prep I have a refinement with the client in 30 minutes

/jira-create-ticket The payment flow needs a retry mechanism when the gateway times out

/projects-health-check What's the status of [project]?

/reports-client-status Write the weekly update for [client], sprint 24

/jira-shadow-refinement [paste user story here]

/confluence-sync-decision-log Sync decisions from the last two weeks
```