pm-setup

Create and update product context files under .claude/product-context/ for PM workflows.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill pm-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-setup
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/agents/plugins/ai-pm-copilot/skills/pm-setup
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill pm-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of setting up a consistent product knowledge base for PM workflows by creating and validating the essential files under .claude/product-context/ so PM agents can work without repeated questions.

Core Features & Use Cases

  • Bootstraps PM agent context: Creates the required product-info.md and tech-stack.md plus optional strategic, metrics, and team files when applicable.
  • Optional codebase-assisted discovery: Detects an existing codebase and (if enabled) uses a context-scanner subagent to auto-discover features, tech stack, integrations, and scale, then prompts for user validation.
  • Supports refresh and incremental updates: Provides an update mode (--update) to re-run questions for selected files and keep timestamps current.

Use it when you want your PM toolkit to immediately start answering product questions using your real product details (especially after spinning up a new project or after the codebase/roadmap changes).

Quick Start

Run the setup command /ai-pm-copilot:pm-setup and follow the prompts to generate the essential product and tech stack context files.

Frequently Asked Questions about pm-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up product context for PM agents in a new project?

Product context setup creates required product-info and tech-stack files under .claude/product-context/ by running an initialization command and following interactive prompts. This generates a validated knowledge base so PM agents operate without repeated configuration questions.

Can I auto-discover tech stack and features by scanning an existing codebase?

Yes, optional codebase-assisted discovery uses a context-scanner subagent to detect an existing codebase and auto-discover features, tech stack, and integrations. The scanned details are then presented for user validation before being committed to the product context files.

What is the best way to refresh product onboarding context after roadmap or codebase changes?

The best way to refresh product context after codebase or roadmap changes is to run the update mode using the --update flag. This re-runs questions for selected files, applies incremental updates, and keeps timestamps current for ongoing PM workflows.

Do I need any specific dependencies or components installed to initialize PM product context?

No specific dependencies or components are required to initialize PM product context. The setup operates independently to create and validate essential product-info, tech-stack, and optional strategic files directly within the .claude/product-context directory.

What files are required for a PM agent product context setup?

Product context setup requires product-info.md and tech-stack.md as mandatory files. It also optionally creates strategic, metrics, and team files when applicable to provide deeper business and operational context for PM workflows.

When should I not use automated codebase scanning for tech stack capture?

You should not use automated codebase scanning when your project lacks an existing codebase or when tech stack details are highly sensitive. In these cases, manual entry through interactive prompts ensures accurate product context without exposing proprietary architecture.