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.6 KiB

Raw Blame History

Smoke Test — PM Discovery Agent

Verify your installation is working before running a real discovery synthesis.

Step 1: Verify connector setup

cd templates/pm-discovery-agent

# Check which connector you've set up
ls connectors/notion.json connectors/google-drive.json 2>/dev/null

# At least one should exist

Step 2: Verify credentials

For Notion:

echo "NOTION_INTEGRATION_TOKEN length: ${#NOTION_INTEGRATION_TOKEN}"
# Should print a non-zero number (typically 50+ characters)

For Google Drive:

echo "GOOGLE_APPLICATION_CREDENTIALS: $GOOGLE_APPLICATION_CREDENTIALS"
# Should print the path to your service account JSON
ls -la $GOOGLE_APPLICATION_CREDENTIALS
# Should show the file exists and you can read it

Step 3: Run the dry-run

bash orchestrate.sh \
  --research-question "Smoke test of agent setup" \
  --interview-source notion \
  --dry-run

(Or --interview-source google-drive if that's what you set up.)

Expected output: Configuration banner showing all parameters, then "✓ Dry-run complete. Configuration is valid."

Step 4: Run a real synthesis against test interviews

If you have access to a test database/folder with at least 5 interviews:

bash orchestrate.sh \
  --research-question "Test discovery synthesis" \
  --interview-source notion \
  --interview-count 5

Expected output: Seven steps complete with ✓ indicators. Output file created at output/discovery-[date].md.

What to do if a step fails

Failure	Likely cause	Fix
"No connector configured"	Missing `connectors/notion.json` or `connectors/google-drive.json`	Copy the `.example.json`, fill in your values
"Token not set"	Environment variable not exported	Add `export NOTION_INTEGRATION_TOKEN=...` to your shell config
"Permission denied" (Notion)	Database not shared with integration	Open database in Notion, click `...`, "Add connections", select your integration
"File not found" (Drive)	Folder not shared with service account	Share the folder with the service account email (Viewer access)
"Skills not found"	Main library not installed	Run `/plugin marketplace add mohitagw15856/pm-claude-skills`
"No interviews returned"	Filters too restrictive or wrong database	Check the `database_id` or `folder_id` matches what you intended

Reporting issues

If the smoke test fails and you can't resolve it, open an issue with:

The exact command you ran
The full error output
Which connector you're using
Your operating system

Don't include credentials or tokens in the issue.

2.6 KiB Raw Blame History