configure-pm-pilot

What problem does it solve?

Many PM Pilot installations require manual configuration across multiple tools and repositories; this skill automates detection of connected MCP tools, sets organization-level settings, seeds a memory file, and verifies that required skill and agent files are present so users can start using PM Pilot immediately.

Core Features & Use Cases

• Automatic MCP detection: Scans for connected MCP servers (Atlassian, Slack, GitHub, Gmail/Calendar, Playwright) and prompts the user to confirm or add missing integrations.
• Organization configuration: Collects and writes the company/org name into the ask-company skill configuration to personalize outputs.
• Memory seeding and validation: Copies a MEMORY-TEMPLATE.md when no MEMORY.md exists, prompts the user for 1-2 active projects and key people, and verifies repository file counts for skills, rules, agents, and commands.
• Use Case: Run during first-time setup or after adding MCP servers to ensure meeting-prep and weekly-status skills have the context and connections they need.

Quick Start

Run the interactive command configure pm-pilot to detect connected tools, set company information, seed a MEMORY.md with projects and people, and validate the installation.