Files

T

mohitagw15856 59c4510055 feat: v9.0.0 — three new agent templates (Discovery, Stakeholder Comms, Launch)

This release adds three new agent templates to the library, bringing the total to four.

New templates:
- PM Discovery Agent: synthesises customer interviews from Notion or Google Drive,
  identifies cross-interview themes, scores assumption confidence, generates follow-up questions
- PM Stakeholder Comms Agent: detects audience type (executive/investor/stakeholder/board),
  pulls activity from Linear/Jira/Drive, drafts in audience-appropriate format
- PM Launch Agent: end-to-end launch coordination with channel-specific content,
  calendar, success metrics, and launch checklist

Each template follows the established pattern: README, AGENT.md, orchestrate.sh,
2 subagents, connectors with example configs, examples, smoke test.

Total file count: 37 new files across 3 templates.

Updated README to position library as 4-template collection.
Bumped marketplace.json from v8.0.0 to v9.0.0.

2026-05-07 22:30:34 +01:00

2.3 KiB

Raw Blame History

Connectors — PM Stakeholder Communications Agent

This agent reads from your team's tracking systems to compile stakeholder communications. Set up at least one ticketing connector (Linear or Jira). Google Drive is optional but recommended.

Required: Linear OR Jira

The agent needs to know what you've shipped. Set up whichever ticketing system you use.

Linear setup (5 min)

cd templates/pm-stakeholder-comms-agent/connectors
cp linear.example.json linear.json

# Get your API key
# Generate at: https://linear.app/settings/account/security
export LINEAR_API_KEY='lin_api_xxxxxxxxxxxx'

# Edit linear.json — update workspace_url and team_id

Jira setup (5 min)

cd templates/pm-stakeholder-comms-agent/connectors
cp jira.example.json jira.json

# Get your API token
# Generate at: https://id.atlassian.com/manage-profile/security/api-tokens
export JIRA_EMAIL='you@company.com'
export JIRA_API_TOKEN='ATATT3xFfGF0...'

# Edit jira.json — update instance_url and project_key

Optional but recommended: Google Drive

Adding Google Drive lets the agent reference recent docs and documented decisions in stakeholder updates. Without it, the agent only has access to ticketing system activity.

cd templates/pm-stakeholder-comms-agent/connectors
cp google-drive.example.json google-drive.json

# Set up service account (see pm-discovery-agent/connectors/README.md for detailed steps)
export GOOGLE_APPLICATION_CREDENTIALS='/path/to/service-account.json'

# Edit google-drive.json — update folder_id

Tagging strategy: keep some work out of external comms

Both Linear and Jira connectors have an exclude_label field defaulting to internal-only. Apply this label to any tickets you don't want surfacing in stakeholder updates:

Sensitive personnel work
Strategic decisions not yet ready to communicate
Internal cleanup and tech debt without external impact
Customer-specific work where the customer hasn't approved attribution

Tagged items still show in your team's tooling but won't appear in agent-generated communications.

Security notes

Credentials live in environment variables, never in the JSON files
Use read-only credentials where possible — the agent only needs to read activity
Both ticketing system tokens and Google service account keys can be regenerated; rotate every 90 days

2.3 KiB Raw Blame History