mohitagw15856
59c4510055
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.
79 lines
2.0 KiB
Markdown
79 lines
2.0 KiB
Markdown
# Smoke Test — PM Stakeholder Communications Agent
|
|
|
|
## Step 1: Verify connector setup
|
|
|
|
```bash
|
|
cd templates/pm-stakeholder-comms-agent
|
|
|
|
# Check at least one ticketing connector is configured
|
|
ls connectors/linear.json connectors/jira.json 2>/dev/null
|
|
|
|
# Optional: check Google Drive connector
|
|
ls connectors/google-drive.json 2>/dev/null
|
|
```
|
|
|
|
## Step 2: Verify credentials
|
|
|
|
```bash
|
|
# Linear
|
|
echo "LINEAR_API_KEY: ${LINEAR_API_KEY:+set}"
|
|
|
|
# Jira
|
|
echo "JIRA_EMAIL: ${JIRA_EMAIL:+set}"
|
|
echo "JIRA_API_TOKEN: ${JIRA_API_TOKEN:+set}"
|
|
|
|
# Google Drive (optional)
|
|
echo "GOOGLE_APPLICATION_CREDENTIALS: ${GOOGLE_APPLICATION_CREDENTIALS:+set}"
|
|
```
|
|
|
|
## Step 3: Run dry-run for each audience type
|
|
|
|
```bash
|
|
bash orchestrate.sh \
|
|
--audience executive \
|
|
--period "last 30 days" \
|
|
--your-name "Test User" \
|
|
--dry-run
|
|
|
|
bash orchestrate.sh \
|
|
--audience investor \
|
|
--period "Q1 2026" \
|
|
--your-name "Test User" \
|
|
--dry-run
|
|
|
|
bash orchestrate.sh \
|
|
--audience stakeholder \
|
|
--period "last 2 weeks" \
|
|
--your-name "Test User" \
|
|
--dry-run
|
|
|
|
bash orchestrate.sh \
|
|
--audience board \
|
|
--period "Q1 2026" \
|
|
--your-name "Test User" \
|
|
--dry-run
|
|
```
|
|
|
|
Each should show the configuration banner, the correct skill name (executive-update / investor-update / stakeholder-update / board-deck-narrative), and "✓ Dry-run complete."
|
|
|
|
## Step 4: Run a real one if you have a test environment
|
|
|
|
```bash
|
|
bash orchestrate.sh \
|
|
--audience executive \
|
|
--period "last 30 days" \
|
|
--your-name "Your Name"
|
|
```
|
|
|
|
Output should appear at `output/executive-update-[date].md`.
|
|
|
|
## Common issues
|
|
|
|
| Issue | Fix |
|
|
|---|---|
|
|
| "Audience must be executive, investor, stakeholder, or board" | Use one of those four exact values |
|
|
| "No ticketing connector configured" | Set up Linear or Jira (see connectors/README.md) |
|
|
| "API key not set" | Export the right environment variable |
|
|
| Empty output despite activity in your tools | Check the period filter — typo in the date format will return zero results |
|
|
| Items showing that should be private | Add the `internal-only` label in your ticketing system |
|