[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72YZBZEY5CT92QFG3GSGXMF":3,"skill-same:01M72YZBZEY5CT92QFG3GSGXMF":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":45},"01M72YZBZEY5CT92QFG3GSGXMF","pm-setup",null,"Initialize .claude\u002Fproduct-context\u002F with essential product information for all PM agents","enigmaicon-eng\u002FAI-Enterprise-OS","enigmaicon-eng","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269773191?v=4","01M72YXXYN7Q7BYRHV8RAVYNWD","01M72YXXZPW35H56D6F1XSK84D",2,"MIT","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fagents\u002Fplugins\u002Fai-pm-copilot\u002Fskills\u002Fpm-setup\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: pm-setup\ndescription: \"Initialize .claude\u002Fproduct-context\u002F with essential product information for all PM agents\"\nuser-invocable: true\ndisable-model-invocation: true\nargument-hint: \"[--update]\"\nallowed-tools: Read, Glob, Grep, Write, Task, AskUserQuestion\n---\n\n# PM Context Setup\n\nQuick setup wizard to initialize `.claude\u002Fproduct-context\u002F` with essential product information. Takes 5-10 minutes and enables all PM agents, commands, and workflows to work with your product context.\n\n## Usage\n\n```bash\n\u002Fai-pm-copilot:pm-setup\n```\n\nOr update existing context:\n\n```bash\n\u002Fai-pm-copilot:pm-setup --update\n```\n\n---\n\n## Overview\n\nThis command sets up the foundational context that powers the entire PM Toolkit. Instead of asking for everything upfront, **we create the essentials now and let the journey build additional context progressively**.\n\n**What it does:**\n\n- Creates `.claude\u002Fproduct-context\u002F` directory\n- Guides you through 2 required files (product basics, tech stack)\n- Offers optional files if applicable (goals, metrics, team)\n- Explains how agents will create additional context as you progress\n\n**What you get:**\n\n- Context reused across 1 orchestrator + 7 specialists\n- Agents work with YOUR product specifics\n- No repeated questions across tools\n- Progressive context building through your journey\n\n---\n\n## Mode\n\nArguments: $ARGUMENTS\n\nIf arguments contain `--update`, run in update mode. Otherwise run initial setup.\n\n---\n\n## Instructions\n\n### Introduction\n\nDisplay introduction message:\n\n```\n╔═══════════════════════════════════════════════════════════╗\n║   Product Management Context Setup                        ║\n╔═══════════════════════════════════════════════════════════╝\n\nQuick setup to get your PM agents working with your product context.\n\n**How it works:**\nWe'll create the essential INPUT files now (5-10 minutes). As you progress\nthrough your product journey, agents will create additional context files:\n\n- Stage 1 (Validation) → competitive-landscape.md\n- Stage 2 (Understanding) → customer-segments.md\n- Stage 5 (Planning) → current-roadmap.md\n\nYour context grows as your product develops!\n\n**What we'll create now:**\n\nRequired:\n1. product-info.md - Product basics (name, description, stage, market, value prop)\n2. tech-stack.md - Tech stack, architecture, constraints\n\nOptional (if applicable):\n3. strategic-goals.md - Vision, goals, priorities (we can help with product-strategist)\n4. business-metrics.md - Current metrics (only if post-launch)\n5. team-info.md - Team size, velocity (only if team > 1)\n\nReady to begin? (yes\u002Fno)\n```\n\nIf user says \"no\", exit. If \"yes\", continue.\n\n---\n\n### Step 0: Check Existing Context\n\nCheck if `.claude\u002Fproduct-context\u002F` directory exists:\n\n```bash\nls .claude\u002Fproduct-context\u002F 2>\u002Fdev\u002Fnull\n```\n\n**If directory exists** with files:\n\n```\nI found existing context files:\n✓ product-info.md\n✓ tech-stack.md\n✓ competitive-landscape.md (created by market-analyst in Stage 1)\n❌ strategic-goals.md (missing)\n...\n\nWould you like to:\n1. Update existing files\n2. Start fresh (overwrite all)\n3. Cancel\n\nYour choice (1\u002F2\u002F3):\n```\n\n**If directory doesn't exist:**\n\n```bash\nmkdir -p .claude\u002Fproduct-context\n```\n\n```\nCreating .claude\u002Fproduct-context\u002F directory...\n✓ Directory created\n```\n\n---\n\n### Step 0.5: Detect Codebase (NEW)\n\nBefore asking manual questions, check if we can auto-discover context from an existing codebase.\n\n**Check for codebase indicators:**\n\n```bash\n# Check for common source directories and manifests\nls src\u002F pages\u002F routes\u002F api\u002F app\u002F package.json requirements.txt go.mod Gemfile composer.json 2>\u002Fdev\u002Fnull\n```\n\n**Codebase detected if any of these exist:**\n\n- Source directories: `src\u002F`, `pages\u002F`, `routes\u002F`, `api\u002F`, `app\u002F`, `lib\u002F`\n- Package manifests: `package.json`, `requirements.txt`, `pyproject.toml`, `go.mod`, `Gemfile`, `composer.json`, `Cargo.toml`\n\n**If codebase detected:**\n\n- Proceed to Step 0.6 (Optional Codebase Scanning)\n\n**If NOT detected:**\n\n- Skip scanning\n- Proceed to Step 1 (Product Information - manual entry)\n- Display: \"No existing codebase detected. Let's set up your context manually.\"\n\n---\n\n### Step 0.6: Optional Codebase Scanning (NEW)\n\n**If codebase was detected in Step 0.5:**\n\nDisplay scanning offer:\n\n```\n═══════════════════════════════════════════════════════════\nCodebase Detected!\n═══════════════════════════════════════════════════════════\n\nI've detected an existing codebase in this project.\n\nI can scan your codebase to automatically discover:\n- Features (from routes, pages, API endpoints)\n- Tech stack (from package.json, requirements.txt, etc.)\n- Integrations (from 3rd party packages)\n- Project scale (files, lines of code, complexity)\n\nThis takes about 30-60 seconds and saves you 10-15 minutes of manual entry.\n\n**What gets scanned:**\n- File structure and routes\n- Package manifests (package.json, requirements.txt, etc.)\n- Tech dependencies\n- Project size indicators\n\n**What does NOT get scanned:**\n- Code quality or architecture\n- Performance or security issues\n- Your code implementation details\n\nAll findings will be presented for your validation before saving.\n\nScan codebase now? (yes\u002Fno)\n```\n\n#### If User Says YES (Accept Scanning)\n\n**Step 1: Invoke context-scanner**\n\nUse Task tool to invoke context-scanner agent:\n\n```\nsubagent_type: \"ai-pm-copilot:context-scanner\"\ndescription: \"Scan codebase for strategic context\"\nprompt: \"Scan the current codebase and return structured discovery of features, tech stack, integrations, and scale. Include evidence and confidence scores for all findings.\"\n```\n\n**Step 2: Receive and Parse JSON**\n\ncontext-scanner returns JSON with:\n\n- features (array of discoveries with evidence)\n- tech_stack (frontend, backend, database, infrastructure)\n- integrations (3rd party services)\n- scale (files, LOC, complexity, maturity)\n- confidence_notes (explanations)\n- scan_limitations (what couldn't be scanned)\n\n**Step 3: Present Findings to User**\n\nDisplay findings in readable format:\n\n```\n═══════════════════════════════════════════════════════════\nScan Complete! Here's what I discovered:\n═══════════════════════════════════════════════════════════\n\n## Features Found\n\n[For each feature in features array:]\n✓ [Feature name] ([details])\n  Evidence: [evidence]\n  Confidence: [High\u002FMedium\u002FLow]\n\n## Features Found\n[For each feature: name, details, evidence, confidence level]\n\n## Tech Stack\n[Frontend, backend, database, infrastructure with evidence]\n\n## Integrations\n[For each: service name, type, evidence, confidence]\n\n## Project Scale\n[Total files, LOC estimate, complexity, maturity]\n\n## Scan Limitations\n[If any, display what couldn't be scanned]\n\n───────────────────────────────────────────────────────────\n```\n\n**Step 4: User Validation**\n\n```\nIs this information accurate? You can:\n1. Confirm all (looks good)\n2. Make corrections (add, remove, or fix items)\n3. Start over with manual entry (ignore scan results)\n\nYour choice (1\u002F2\u002F3):\n```\n\n**If choice = 1 (Confirm all):**\n\n```\nGreat! I'll use this discovered context.\n\nAny features or details I missed that you'd like to add? (describe or type \"none\"):\n[User input]\n\n[If user adds items, append to relevant sections]\n✓ Added: [user's addition]\n```\n\n**If choice = 2 (Make corrections):**\n\n```\nLet's review each section:\n\n═══════════════════════════════════════════════════════════\nFeatures Review\n═══════════════════════════════════════════════════════════\n\n[For each feature with Medium\u002FLow confidence:]\n[Feature name]: [Confidence level]\n\nKeep this feature? (yes\u002Fno\u002Frename)\n[User input for each]\n\n[If rename:]\nWhat should I call it instead?\n[User input]\n\n[After reviewing uncertain features:]\nAny features I completely missed? (list them or type \"none\"):\n[User input]\n\n✓ Features validated\n\n═══════════════════════════════════════════════════════════\nTech Stack Review\n═══════════════════════════════════════════════════════════\n\n[Display tech stack]\n\nIs this tech stack accurate? (yes\u002Fno)\n[If no:]\nWhat needs correction?\n[User input]\n\n✓ Tech stack validated\n\n═══════════════════════════════════════════════════════════\nIntegrations Review\n═══════════════════════════════════════════════════════════\n\n[For each integration:]\n[Service]: [Type] - Confirm this is actively used? (yes\u002Fno\u002Fremove)\n[User input for each]\n\nAny integrations I missed?\n[User input]\n\n✓ Integrations validated\n```\n\n**If choice = 3 (Start over with manual entry):**\n\n```\nNo problem! Let's set up your context manually instead.\n\nProceeding to manual entry...\n```\n\nSkip to Step 1: Product Information (manual flow)\n\n**Step 5: Save Validated Data to Context Files**\n\nCreate\u002Fupdate context files with validated data:\n\n**Create current-features.md:**\n\n```markdown\n# Current Features\n\n_Auto-discovered: [current date]_\n_Last validated: [current date]_\n\n## Core Features\n\n[For each validated feature:]\n\n### [Feature Name]\n\n- [Feature details]\n- Evidence: [evidence from scan]\n- Confidence: [confidence level]\n\n## Integrations\n\n[For each validated integration:]\n\n### [Service Name] ([Type])\n\n- Evidence: [evidence from scan]\n- Confidence: [confidence level]\n- Status: [Active\u002FDetected but not verified]\n\n## Not Included (Known Gaps)\n\n[Any features user mentioned as \"not yet built\" or \"planned\"]\n\n---\n\n_This file was auto-discovered by context-scanner and validated by user._\n_Refresh by running: \u002Fai-pm-copilot:pm-setup_\n```\n\n**Update tech-stack.md:**\n\n```markdown\n# Tech Stack\n\n**Last Updated:** [current date]\n_Auto-discovered from codebase, validated by user_\n\n## Stack\n\n- **Frontend:** [discovered frontend tech]\n- **Backend:** [discovered backend tech]\n- **Database:** [discovered databases]\n- **Infrastructure:** [discovered infrastructure]\n\n_Evidence: [package.json \u002F requirements.txt \u002F etc.]_\n\n## Architecture\n\n[discovered architecture pattern or \"Not specified\"]\n\n## Technical Constraints\n\n[If user added constraints during validation, list them. Otherwise: \"None specified\"]\n\n## Scale\n\n- Lines of code: ~[discovered LOC]\n- Source files: [discovered file count]\n- Complexity: [discovered complexity]\n- Maturity: [discovered maturity]\n\n---\n\n_Tech stack auto-discovered by context-scanner_\n```\n\n**Update product-info.md (add Features section):**\n\n```markdown\n# Product Information\n\n[Existing sections...]\n\n## Features\n\n[For each validated feature:]\n\n- [Feature name]\n\nSee `current-features.md` for detailed feature inventory.\n\n---\n\n_Features auto-discovered: [date]_\n```\n\n**Step 6: Display Success Message**\n\n```\n✓ Context auto-discovered and validated!\n✓ Saved to .claude\u002Fproduct-context\u002F\n\nFiles created\u002Fupdated:\n- current-features.md (feature inventory)\n- tech-stack.md (stack and scale)\n- product-info.md (features section added)\n\nTime saved: ~10-15 minutes vs manual entry\n\n───────────────────────────────────────────────────────────\n```\n\nThen proceed to Step 3: Optional Context Files (strategic-goals, business-metrics, team-info)\n\n#### If User Says NO (Decline Scanning)\n\n```\nNo problem! I'll guide you through manual setup instead.\n\nProceeding to manual entry...\n```\n\nSkip scanning, proceed to Step 1: Product Information (manual flow)\n\n---\n\n### Refresh Mode (When Existing Context Detected)\n\n**If Step 0 detected existing `.claude\u002Fproduct-context\u002F` with files:**\n\nDisplay refresh options:\n\n```\n═══════════════════════════════════════════════════════════\nExisting Product Context Detected\n═══════════════════════════════════════════════════════════\n\nI found existing product context from [date of last update].\n\nWould you like to:\n\n1. Refresh context (re-scan codebase, show what changed)\n2. Add to existing (keep current, add new information)\n3. Start fresh (archive current, create new)\n4. Cancel\n\nYour choice (1\u002F2\u002F3\u002F4):\n```\n\n**If choice = 1 (Refresh):**\n\n```\n═══════════════════════════════════════════════════════════\nRefreshing Product Context\n═══════════════════════════════════════════════════════════\n\nRe-scanning your codebase to detect changes...\n\n[Invoke context-scanner again]\n[Receive new scan results]\n\nComparing to existing context...\n\n═══════════════════════════════════════════════════════════\nChanges Detected:\n═══════════════════════════════════════════════════════════\n\n## Features\n\n**Added:**\n[List features in new scan but not in existing context]\n- Analytics dashboard\n- Export functionality\n\n**Updated:**\n[List features that changed]\n- Project Management: Now includes Gantt chart view\n\n**Removed:**\n[List features in existing context but not in new scan]\n- None\n\n**Unchanged:**\n- Authentication\n- Task Management\n- Team Collaboration\n\n## Tech Stack\n\n**Updated:**\n- Node.js: 18.x → 20.x\n- React: 18.0 → 18.2\n\n**Added:**\n- Vite 4.3 (build tool)\n\n**Removed:**\n- None\n\n## Integrations\n\n**Added:**\n- Slack (notifications)\n\n**Unchanged:**\n- Stripe (payments)\n- SendGrid (email)\n\n═══════════════════════════════════════════════════════════\n\nApply these changes? (yes\u002Fno\u002Freview)\n```\n\n**If yes:** Update context files with changes, preserve metadata\n\n**If review:** Let user validate each change individually\n\n**If no:** Keep existing context unchanged\n\n**If choice = 2 (Add to existing):**\n\n```\nWhat would you like to add or update?\n\n1. Add new features\n2. Update tech stack\n3. Add\u002Fupdate integrations\n4. Update strategic goals\n5. Update metrics\n6. Update team info\n\nSelect items to update (comma-separated, e.g., \"1,2\"):\n[User input]\n```\n\nThen guide through only selected sections, append to existing files.\n\n**If choice = 3 (Start fresh):**\n\n```\nThis will archive your current context and create a new one from scratch.\n\nArchive location: .claude\u002Fproduct-context-backup-[YYYY-MM-DD]\u002F\n\nProceed? (yes\u002Fno)\n```\n\nIf yes:\n\n```bash\n# Archive existing context\nmv .claude\u002Fproduct-context .claude\u002Fproduct-context-backup-$(date +%Y-%m-%d)\n\n# Create fresh directory\nmkdir -p .claude\u002Fproduct-context\n```\n\nThen proceed with fresh setup (Step 0.5: Detect Codebase)\n\n**If choice = 4 (Cancel):**\n\nExit setup without changes.\n\n---\n\n### Step 1: Product Information (Required)\n\n```\n═══════════════════════════════════════════════════════════\nStep 1 of 2 (Required): Product Information\n═══════════════════════════════════════════════════════════\n\nLet's capture the basics about your product.\n\n**Product Name:**\n[User input]\n\n**Product Description** (2-3 sentences - what does it do and for whom?):\n[User input]\n\n**Product Stage** (select one):\n1. Idea - Validating concept, no code yet\n2. MVP - First version built, testing with early users\n3. PMF - Product-market fit achieved, growing user base\n4. Growth - Scaling go-to-market, optimizing funnel\n5. Mature - Established product, focus on retention\u002Fexpansion\n\nYour choice (1-5):\n[User input]\n\n**Primary Target Market** (e.g., \"B2B SaaS for SMBs\", \"Consumer productivity app\"):\n[User input]\n\n**Key Value Proposition** (one sentence - what unique value do you provide?):\n[User input]\n\n✓ Product information captured\n```\n\nCreate `.claude\u002Fproduct-context\u002Fproduct-info.md`:\n\n```markdown\n# Product Information\n\n**Product Name:** [name]\n**Stage:** [stage]\n**Last Updated:** [current date]\n\n## Description\n\n[description]\n\n## Target Market\n\n[target market]\n\n## Value Proposition\n\n[value proposition]\n\n## Product Type\n\n[Infer from description: Web app, Mobile app, API\u002FPlatform, Desktop app, etc.]\n```\n\n---\n\n### Step 2: Tech Stack (Required)\n\n```\n═══════════════════════════════════════════════════════════\nStep 2 of 2 (Required): Tech Stack\n═══════════════════════════════════════════════════════════\n\nWhat's your technology stack? This helps agents give specific technical guidance.\n\n**Frontend** (e.g., React, Vue, SwiftUI, Flutter):\n[User input]\n\n**Backend** (e.g., Node.js, Python\u002FDjango, Go, Ruby\u002FRails):\n[User input]\n\n**Database** (e.g., PostgreSQL, MongoDB, MySQL):\n[User input]\n\n**Infrastructure** (e.g., AWS, Vercel, Railway, self-hosted):\n[User input]\n\n**Architecture Pattern** (select one):\n1. Monolith\n2. Microservices\n3. Serverless\n4. Hybrid\n\nYour choice (1-4):\n[User input]\n\n**Key Technical Constraints** (optional, one per line, or type \"none\"):\n[User input - allow multiple lines]\n[User types \"none\" or \"done\" when finished]\n\n✓ Tech stack captured\n```\n\nCreate `.claude\u002Fproduct-context\u002Ftech-stack.md`:\n\n```markdown\n# Tech Stack\n\n**Last Updated:** [current date]\n\n## Stack\n\n- **Frontend:** [frontend]\n- **Backend:** [backend]\n- **Database:** [database]\n- **Infrastructure:** [infrastructure]\n\n## Architecture\n\n[architecture pattern]\n\n## Technical Constraints\n\n[list constraints, or \"None specified\"]\n```\n\n---\n\n### Step 3: Optional Context Files\n\nAfter completing the 2 required files:\n\n```\n═══════════════════════════════════════════════════════════\nOptional Context Files\n═══════════════════════════════════════════════════════════\n\nGreat! You've completed the required files. Would you like to add optional\ncontext files now? These are helpful if applicable to your situation:\n\n1. strategic-goals.md - Vision, goals, priorities (we can help with product-strategist)\n2. business-metrics.md - Current metrics, growth rates (only if post-launch)\n3. team-info.md - Team size, velocity, capacity (only if team > 1)\n4. None - Skip optional files for now\n\nSelect files to create (comma-separated, e.g., \"1,2\" or \"4\" for none):\n[User input]\n```\n\n#### Optional: Strategic Goals\n\nIf user selects option 1:\n\n```\n═══════════════════════════════════════════════════════════\nOptional: Strategic Goals\n═══════════════════════════════════════════════════════════\n\nDo you have a product vision and strategic goals defined?\n\n1. Yes - I have them ready to share\n2. No - Help me develop them with product-strategist agent\n3. Skip for now\n\nYour choice (1\u002F2\u002F3):\n```\n\n**If choice = 1 (Has goals):**\n\n```\nGreat! Let's capture your strategic direction.\n\n**Product Vision** (one sentence - where are you headed in 3-5 years?):\n[User input]\n\n**Top 3 Strategic Priorities** (for current quarter\u002Fperiod):\n1. [User input]\n2. [User input]\n3. [User input]\n\n**Key Success Metrics** (what metrics define success? optional):\n1. [User input or \"Skip\"]\n2. [User input or \"Skip\"]\n3. [User input or \"Skip\"]\n\n✓ Strategic goals captured\n```\n\nCreate `.claude\u002Fproduct-context\u002Fstrategic-goals.md`:\n\n```markdown\n# Strategic Goals\n\n**Period:** [Current quarter\u002Fyear]\n**Last Updated:** [current date]\n\n## Product Vision\n\n[vision statement]\n\n## Strategic Priorities\n\n1. [priority 1]\n2. [priority 2]\n3. [priority 3]\n\n## Key Success Metrics\n\n[list metrics, or \"To be defined\"]\n```\n\n**If choice = 2 (Needs help):**\n\n```\nPerfect! I'll invoke product-strategist to help you develop vision and strategic goals.\n\nRouting to product-strategist agent...\n```\n\n**Invoke product-strategist agent:**\n\n```\nUse the Task tool to invoke:\n\nTask(\n  subagent_type: \"product-strategist\",\n  description: \"Develop product vision and goals\",\n  prompt: \"Help develop product vision and strategic goals for this product.\n\nProduct context:\n- Name: [product name]\n- Description: [product description]\n- Stage: [product stage]\n- Target Market: [target market]\n- Value Prop: [value proposition]\n\nPlease help the user:\n1. Craft a compelling 3-5 year product vision (one sentence)\n2. Define 3 strategic priorities for the current quarter\u002Fperiod\n3. Suggest 2-3 key success metrics to track\n\nFocus on outcomes and strategic direction, not feature lists. Keep it concise and actionable.\n\nWhen complete, format the output as:\n\n# Strategic Goals\n\n**Period:** [Current quarter\u002Fyear]\n**Last Updated:** [date]\n\n## Product Vision\n\n[vision statement]\n\n## Strategic Priorities\n\n1. [priority 1]\n2. [priority 2]\n3. [priority 3]\n\n## Key Success Metrics\n\n1. [metric 1]\n2. [metric 2]\n3. [metric 3]\n\nThen save this to .claude\u002Fproduct-context\u002Fstrategic-goals.md\"\n)\n```\n\nAfter agent completes:\n\n```\n✓ Vision and strategic goals developed with product-strategist\n✓ Saved to strategic-goals.md\n```\n\n**If choice = 3 (Skip):**\n\n```\nSkipping strategic goals for now. You can add this later with:\n\u002Fpm-setup --update\n```\n\n#### Optional: Business Metrics\n\nIf user selects option 2:\n\n```\n═══════════════════════════════════════════════════════════\nOptional: Business Metrics\n═══════════════════════════════════════════════════════════\n\nLet's capture your current metrics (provide what you track, skip what you don't).\n\n**User Metrics:**\n- Total active users (MAU): [User input or \"Skip\"]\n- User growth rate (% per month): [User input or \"Skip\"]\n\n**Revenue Metrics** (if applicable):\n- MRR or ARR: [User input or \"Skip\"]\n- Revenue growth rate: [User input or \"Skip\"]\n\n**Engagement:**\n- Retention Day 30: [User input or \"Skip\"]\n- Key engagement metric: [User input or \"Skip\"]\n\n✓ Business metrics captured\n```\n\nCreate `.claude\u002Fproduct-context\u002Fbusiness-metrics.md`:\n\n```markdown\n# Business Metrics\n\n**Last Updated:** [current date]\n\n## User Metrics\n\n[list provided metrics or \"Not tracking yet\"]\n\n## Revenue Metrics\n\n[list provided metrics or \"Pre-revenue\"]\n\n## Engagement Metrics\n\n[list provided metrics or \"To be measured\"]\n```\n\n#### Optional: Team Information\n\nIf user selects option 3:\n\n```\n═══════════════════════════════════════════════════════════\nOptional: Team Information\n═══════════════════════════════════════════════════════════\n\n**Team Size:**\n- Product\u002FPM: [User input]\n- Engineering: [User input]\n- Design: [User input]\n- Other: [User input or \"0\"]\n\n**Work Cadence** (select one):\n1. Solo builder (just me)\n2. Scrum (2-week sprints)\n3. Kanban (continuous flow)\n4. Other\n\nYour choice (1-4):\n[User input]\n\n**Velocity** (if you track it):\n- Story points per sprint: [User input or \"Not tracked\"]\nOR\n- Features per month: [User input or \"Not tracked\"]\n\n✓ Team info captured\n```\n\nCreate `.claude\u002Fproduct-context\u002Fteam-info.md`:\n\n```markdown\n# Team Information\n\n**Last Updated:** [current date]\n\n## Team Size\n\n- Product\u002FPM: [count]\n- Engineering: [count]\n- Design: [count]\n- Other: [count]\n\n**Total:** [sum] people\n\n## Work Cadence\n\n[cadence type and details]\n\n## Velocity\n\n[velocity info or \"Not tracked\"]\n```\n\n---\n\n### Final Summary\n\nDisplay completion summary:\n\n```\n═══════════════════════════════════════════════════════════\n✅ Setup Complete!\n═══════════════════════════════════════════════════════════\n\nContext files created in .claude\u002Fproduct-context\u002F:\n\nRequired:\n✓ product-info.md - [Product Name] ([Stage])\n✓ tech-stack.md - [Frontend] + [Backend] stack\n\n[If optional files were created]:\nOptional:\n✓ strategic-goals.md - Vision and priorities [+ product-strategist ✨ if invoked]\n✓ business-metrics.md - [Key metrics]\n✓ team-info.md - [Team size] team\n\n───────────────────────────────────────────────────────────\n\n**Next:** Tell product-manager what you need, or invoke a specialist agent directly.\n\n**Update context anytime:** `\u002Fai-pm-copilot:pm-setup --update`\n```\n\n---\n\n## Update Mode\n\nIf user runs `\u002Fpm-setup --update`:\n\n```\n╔═══════════════════════════════════════════════════════════╗\n║   Update Product Management Context                       ║\n╔═══════════════════════════════════════════════════════════╝\n\nWhich files would you like to update?\n\nEssential:\n1. ⬜ product-info.md (last updated: [date])\n2. ⬜ tech-stack.md (last updated: [date])\n\nOptional:\n3. ⬜ strategic-goals.md (last updated: [date]) [⚠️ if >3 months old]\n4. ⬜ business-metrics.md (last updated: [date]) [⚠️ if >1 month old]\n5. ⬜ team-info.md (last updated: [date])\n\nCreated by journey (usually updated by agents):\n6. ⬜ competitive-landscape.md (last updated: [date])\n7. ⬜ customer-segments.md (last updated: [date])\n8. ⬜ current-roadmap.md (last updated: [date])\n\n9. All files\n\nSelect files to update (comma-separated, e.g., \"1,3\" or \"9\" for all):\n[User input]\n```\n\nFor each selected file:\n\n- Re-run that file's questions\n- Show current values: `Current: [value]. Press Enter to keep, or type new value:`\n- For strategic-goals: Offer product-strategist help again if updating\n- Update only changed values\n- Update \"Last Updated\" timestamp\n\n---\n\n## Validation\n\nAfter each step, validate that essential information is provided:\n\n**Essential per required file:**\n\n- product-info.md: name, description, stage, target market, value prop (all required)\n- tech-stack.md: frontend, backend, database, infrastructure, architecture (all required)\n\n**For optional files:**\n\n- strategic-goals.md: at least vision OR 3 priorities\n- business-metrics.md: at least 2 metrics\n- team-info.md: team size and cadence\n\nIf essential fields missing:\n\n```\n⚠️  Missing required information:\n- [Field name]: [Brief explanation of why it's needed]\n\nWould you like to:\n1. Provide this information now\n2. Cancel this file\n\nYour choice (1\u002F2):\n```\n\n---\n\n## Error Handling\n\n**If .claude\u002F directory doesn't exist:**\n\n```bash\nmkdir -p .claude\u002Fproduct-context\n```\n\n**If file write fails:**\n\n```\n❌ Error writing to [file_path]\n\nPossible issues:\n- Directory permissions\n- Disk space\n\nWould you like to:\n1. Retry\n2. Skip this file\n3. Cancel setup\n\nYour choice (1\u002F2\u002F3):\n```\n\n**If agent invocation fails** (for strategic-goals):\n\n```\n❌ Error invoking product-strategist agent\n\nFalling back to manual input. Let's capture your strategic direction:\n\n[Proceed with manual questions for strategic-goals]\n```\n\n**If user quits mid-setup:**\n\n```\nSetup incomplete. Files created so far:\n✓ product-info.md\n❌ tech-stack.md (not created)\n\nRequired files are incomplete. Please run \u002Fpm-setup again to finish.\n```\n\n","# PM Context Setup\n\nQuick setup wizard to initialize `.claude\u002Fproduct-context\u002F` with essential product information. Takes 5-10 minutes and enables all PM agents, commands, and workflows to work with your product context.\n\n## Usage\n\n```bash\n\u002Fai-pm-copilot:pm-setup\n```\n\nOr update existing context:\n\n```bash\n\u002Fai-pm-copilot:pm-setup --update\n```\n\n---\n\n## Overview\n\nThis command sets up the foundational context that powers the entire PM Toolkit. Instead of asking for everything upfront, **we create the essentials now and let the journey build additional context progressively**.\n\n**What it does:**\n\n- Creates `.claude\u002Fproduct-context\u002F` directory\n- Guides you through 2 required files (product basics, tech stack)\n- Offers optional files if applicable (goals, metrics, team)\n- Explains how agents will create additional context as you progress\n\n**What you get:**\n\n- Context reused across 1 orchestrator + 7 specialists\n- Agents work with YOUR product specifics\n- No repeated questions across tools\n- Progressive context building through your journey\n\n---\n\n## Mode\n\nArguments: $ARGUMENTS\n\nIf arguments contain `--update`, run in update mode. Otherwise run initial setup.\n\n---\n\n## Instructions\n\n### Introduction\n\nDisplay introduction message:\n\n```\n╔═══════════════════════════════════════════════════════════╗\n║   Product Management Context Setup                        ║\n╔═══════════════════════════════════════════════════════════╝\n\nQuick setup to get your PM agents working with your product context.\n\n**How it works:**\nWe'll create the essential INPUT files now (5-10 minutes). As you progress\nthrough your product journey, agents will create additional context files:\n\n- Stage 1 (Validation) → competitive-landscape.md\n- Stage 2 (Understanding) → customer-segments.md\n- Stage 5 (Planning) → current-roadmap.md\n\nYour context grows as your product develops!\n\n**What we'll create now:**\n\nRequired:\n1. product-info.md - Product basics (name, description, stage, market, value prop)\n2. tech-stack.md - Tech stack, architecture, constraints\n\nOptional (if applicable):\n3. strategic-goals.md - Vision, goals, priorities (we can help with product-strategist)\n4. business-metrics.md - Current metrics (only if post-launch)\n5. team-info.md - Team size, velocity (only if team > 1)\n\nReady to begin? (yes\u002Fno)\n```\n\nIf user says \"no\", exit. If \"yes\", continue.\n\n---\n\n### Step 0: Check Existing Context\n\nCheck if `.claude\u002Fproduct-context\u002F` directory exists:\n\n```bash\nls .claude\u002Fproduct-context\u002F 2>\u002Fdev\u002Fnull\n```\n\n**If directory exists** with files:\n\n```\nI found existing context files:\n✓ product-info.md\n✓ tech-stack.md\n✓ competitive-landscape.md (created by market-analyst in Stage 1)\n❌ strategic-goals.md (missing)\n...\n\nWould you like to:\n1. Update existing files\n2. Start fresh (overwrite all)\n3. Cancel\n\nYour choice (1\u002F2\u002F3):\n```\n\n**If directory doesn't exist:**\n\n```bash\nmkdir -p .claude\u002Fproduct-context\n```\n\n```\nCreating .claude\u002Fproduct-context\u002F directory...\n✓ Directory created\n```\n\n---\n\n### Step 0.5: Detect Codebase (NEW)\n\nBefore asking manual questions, check if we can auto-discover context from an existing codebase.\n\n**Check for codebase indicators:**\n\n```bash\n# Check for common source directories and manifests\nls src\u002F pages\u002F routes\u002F api\u002F app\u002F package.json requirements.txt go.mod Gemfile composer.json 2>\u002Fdev\u002Fnull\n```\n\n**Codebase detected if any of these exist:**\n\n- Source directories: `src\u002F`, `pages\u002F`, `routes\u002F`, `api\u002F`, `app\u002F`, `lib\u002F`\n- Package manifests: `package.json`, `requirements.txt`, `pyproject.toml`, `go.mod`, `Gemfile`, `composer.json`, `Cargo.toml`\n\n**If codebase detected:**\n\n- Proceed to Step 0.6 (Optional Codebase Scanning)\n\n**If NOT detected:**\n\n- Skip scanning\n- Proceed to Step 1 (Product Information - manual entry)\n- Display: \"No existing codebase detected. Let's set up your context manually.\"\n\n---\n\n### Step 0.6: Optional Codebase Scanning (NEW)\n\n**If codebase was detected in Step 0.5:**\n\nDisplay scanning offer:\n\n```\n═══════════════════════════════════════════════════════════\nCodebase Detected!\n═══════════════════════════════════════════════════════════\n\nI've detected an existing codebase in this project.\n\nI can scan your codebase to automatically discover:\n- Features (from routes, pages, API endpoints)\n- Tech stack (from package.json, requirements.txt, etc.)\n- Integrations (from 3rd party packages)\n- Project scale (files, lines of code, complexity)\n\nThis takes about 30-60 seconds and saves you 10-15 minutes of manual entry.\n\n**What gets scanned:**\n- File structure and routes\n- Package manifests (package.json, requirements.txt, etc.)\n- Tech dependencies\n- Project size indicators\n\n**What does NOT get scanned:**\n- Code quality or architecture\n- Performance or security issues\n- Your code implementation details\n\nAll findings will be presented for your validation before saving.\n\nScan codebase now? (yes\u002Fno)\n```\n\n#### If User Says YES (Accept Scanning)\n\n**Step 1: Invoke context-scanner**\n\nUse Task tool to invoke context-scanner agent:\n\n```\nsubagent_type: \"ai-pm-copilot:context-scanner\"\ndescription: \"Scan codebase for strategic context\"\nprompt: \"Scan the current codebase and return structured discovery of features, tech stack, integrations, and scale. Include evidence and confidence scores for all findings.\"\n```\n\n**Step 2: Receive and Parse JSON**\n\ncontext-scanner returns JSON with:\n\n- features (array of discoveries with evidence)\n- tech_stack (frontend, backend, database, infrastructure)\n- integrations (3rd party services)\n- scale (files, LOC, complexity, maturity)\n- confidence_notes (explanations)\n- scan_limitations (what couldn't be scanned)\n\n**Step 3: Present Findings to User**\n\nDisplay findings in readable format:\n\n```\n═══════════════════════════════════════════════════════════\nScan Complete! Here's what I discovered:\n═══════════════════════════════════════════════════════════\n\n## Features Found\n\n[For each feature in features array:]\n✓ [Feature name] ([details])\n  Evidence: [evidence]\n  Confidence: [High\u002FMedium\u002FLow]\n\n## Features Found\n[For each feature: name, details, evidence, confidence level]\n\n## Tech Stack\n[Frontend, backend, database, infrastructure with evidence]\n\n## Integrations\n[For each: service name, type, evidence, confidence]\n\n## Project Scale\n[Total files, LOC estimate, complexity, maturity]\n\n## Scan Limitations\n[If any, display what couldn't be scanned]\n\n───────────────────────────────────────────────────────────\n```\n\n**Step 4: User Validation**\n\n```\nIs this information accurate? You can:\n1. Confirm all (looks good)\n2. Make corrections (add, remove, or fix items)\n3. Start over with manual entry (ignore scan results)\n\nYour choice (1\u002F2\u002F3):\n```\n\n**If choice = 1 (Confirm all):**\n\n```\nGreat! I'll use this discovered context.\n\nAny features or details I missed that you'd like to add? (describe or type \"none\"):\n[User input]\n\n[If user adds items, append to relevant sections]\n✓ Added: [user's addition]\n```\n\n**If choice = 2 (Make corrections):**\n\n```\nLet's review each section:\n\n═══════════════════════════════════════════════════════════\nFeatures Review\n═══════════════════════════════════════════════════════════\n\n[For each feature with Medium\u002FLow confidence:]\n[Feature name]: [Confidence level]\n\nKeep this feature? (yes\u002Fno\u002Frename)\n[User input for each]\n\n[If rename:]\nWhat should I call it instead?\n[User input]\n\n[After reviewing uncertain features:]\nAny features I completely missed? (list them or type \"none\"):\n[User input]\n\n✓ Features validated\n\n═══════════════════════════════════════════════════════════\nTech Stack Review\n═══════════════════════════════════════════════════════════\n\n[Display tech stack]\n\nIs this tech stack accurate? (yes\u002Fno)\n[If no:]\nWhat needs correction?\n[User input]\n\n✓ Tech stack validated\n\n═══════════════════════════════════════════════════════════\nIntegrations Review\n═══════════════════════════════════════════════════════════\n\n[For each integration:]\n[Service]: [Type] - Confirm this is actively used? (yes\u002Fno\u002Fremove)\n[User input for each]\n\nAny integrations I missed?\n[User input]\n\n✓ Integrations validated\n```\n\n**If choice = 3 (Start over with manual entry):**\n\n```\nNo problem! Let's set up your context manually instead.\n\nProceeding to manual entry...\n```\n\nSkip to Step 1: Product Information (manual flow)\n\n**Step 5: Save Validated Data to Context Files**\n\nCreate\u002Fupdate context files with validated data:\n\n**Create current-features.md:**\n\n```markdown\n# Current Features\n\n_Auto-discovered: [current date]_\n_Last validated: [current date]_\n\n## Core Features\n\n[For each validated feature:]\n\n### [Feature Name]\n\n- [Feature details]\n- Evidence: [evidence from scan]\n- Confidence: [confidence level]\n\n## Integrations\n\n[For each validated integration:]\n\n### [Service Name] ([Type])\n\n- Evidence: [evidence from scan]\n- Confidence: [confidence level]\n- Status: [Active\u002FDetected but not verified]\n\n## Not Included (Known Gaps)\n\n[Any features user mentioned as \"not yet built\" or \"planned\"]\n\n---\n\n_This file was auto-discovered by context-scanner and validated by user._\n_Refresh by running: \u002Fai-pm-copilot:pm-setup_\n```\n\n**Update tech-stack.md:**\n\n```markdown\n# Tech Stack\n\n**Last Updated:** [current date]\n_Auto-discovered from codebase, validated by user_\n\n## Stack\n\n- **Frontend:** [discovered frontend tech]\n- **Backend:** [discovered backend tech]\n- **Database:** [discovered databases]\n- **Infrastructure:** [discovered infrastructure]\n\n_Evidence: [package.json \u002F requirements.txt \u002F etc.]_\n\n## Architecture\n\n[discovered architecture pattern or \"Not specified\"]\n\n## Technical Constraints\n\n[If user added constraints during validation, list them. Otherwise: \"None specified\"]\n\n## Scale\n\n- Lines of code: ~[discovered LOC]\n- Source files: [discovered file count]\n- Complexity: [discovered complexity]\n- Maturity: [discovered maturity]\n\n---\n\n_Tech stack auto-discovered by context-scanner_\n```\n\n**Update product-info.md (add Features section):**\n\n```markdown\n# Product Information\n\n[Existing sections...]\n\n## Features\n\n[For each validated feature:]\n\n- [Feature name]\n\nSee `current-features.md` for detailed feature inventory.\n\n---\n\n_Features auto-discovered: [date]_\n```\n\n**Step 6: Display Success Message**\n\n```\n✓ Context auto-discovered and validated!\n✓ Saved to .claude\u002Fproduct-context\u002F\n\nFiles created\u002Fupdated:\n- current-features.md (feature inventory)\n- tech-stack.md (stack and scale)\n- product-info.md (features section added)\n\nTime saved: ~10-15 minutes vs manual entry\n\n───────────────────────────────────────────────────────────\n```\n\nThen proceed to Step 3: Optional Context Files (strategic-goals, business-metrics, team-info)\n\n#### If User Says NO (Decline Scanning)\n\n```\nNo problem! I'll guide you through manual setup instead.\n\nProceeding to manual entry...\n```\n\nSkip scanning, proceed to Step 1: Product Information (manual flow)\n\n---\n\n### Refresh Mode (When Existing Context Detected)\n\n**If Step 0 detected existing `.claude\u002Fproduct-context\u002F` with files:**\n\nDisplay refresh options:\n\n```\n═══════════════════════════════════════════════════════════\nExisting Product Context Detected\n═══════════════════════════════════════════════════════════\n\nI found existing product context from [date of last update].\n\nWould you like to:\n\n1. Refresh context (re-scan codebase, show what changed)\n2. Add to existing (keep current, add new information)\n3. Start fresh (archive current, create new)\n4. Cancel\n\nYour choice (1\u002F2\u002F3\u002F4):\n```\n\n**If choice = 1 (Refresh):**\n\n```\n═══════════════════════════════════════════════════════════\nRefreshing Product Context\n═══════════════════════════════════════════════════════════\n\nRe-scanning your codebase to detect changes...\n\n[Invoke context-scanner again]\n[Receive new scan results]\n\nComparing to existing context...\n\n═══════════════════════════════════════════════════════════\nChanges Detected:\n═══════════════════════════════════════════════════════════\n\n## Features\n\n**Added:**\n[List features in new scan but not in existing context]\n- Analytics dashboard\n- Export functionality\n\n**Updated:**\n[List features that changed]\n- Project Management: Now includes Gantt chart view\n\n**Removed:**\n[List features in existing context but not in new scan]\n- None\n\n**Unchanged:**\n- Authentication\n- Task Management\n- Team Collaboration\n\n## Tech Stack\n\n**Updated:**\n- Node.js: 18.x → 20.x\n- React: 18.0 → 18.2\n\n**Added:**\n- Vite 4.3 (build tool)\n\n**Removed:**\n- None\n\n## Integrations\n\n**Added:**\n- Slack (notifications)\n\n**Unchanged:**\n- Stripe (payments)\n- SendGrid (email)\n\n═══════════════════════════════════════════════════════════\n\nApply these changes? (yes\u002Fno\u002Freview)\n```\n\n**If yes:** Update context files with changes, preserve metadata\n\n**If review:** Let user validate each change individually\n\n**If no:** Keep existing context unchanged\n\n**If choice = 2 (Add to existing):**\n\n```\nWhat would you like to add or update?\n\n1. Add new features\n2. Update tech stack\n3. Add\u002Fupdate integrations\n4. Update strategic goals\n5. Update metrics\n6. Update team info\n\nSelect items to update (comma-separated, e.g., \"1,2\"):\n[User input]\n```\n\nThen guide through only selected sections, append to existing files.\n\n**If choice = 3 (Start fresh):**\n\n```\nThis will archive your current context and create a new one from scratch.\n\nArchive location: .claude\u002Fproduct-context-backup-[YYYY-MM-DD]\u002F\n\nProceed? (yes\u002Fno)\n```\n\nIf yes:\n\n```bash\n# Archive existing context\nmv .claude\u002Fproduct-context .claude\u002Fproduct-context-backup-$(date +%Y-%m-%d)\n\n# Create fresh directory\nmkdir -p .claude\u002Fproduct-context\n```\n\nThen proceed with fresh setup (Step 0.5: Detect Codebase)\n\n**If choice = 4 (Cancel):**\n\nExit setup without changes.\n\n---\n\n### Step 1: Product Information (Required)\n\n```\n═══════════════════════════════════════════════════════════\nStep 1 of 2 (Required): Product Information\n═══════════════════════════════════════════════════════════\n\nLet's capture the basics about your product.\n\n**Product Name:**\n[User input]\n\n**Product Description** (2-3 sentences - what does it do and for whom?):\n[User input]\n\n**Product Stage** (select one):\n1. Idea - Validating concept, no code yet\n2. MVP - First version built, testing with early users\n3. PMF - Product-market fit achieved, growing user base\n4. Growth - Scaling go-to-market, optimizing funnel\n5. Mature - Established product, focus on retention\u002Fexpansion\n\nYour choice (1-5):\n[User input]\n\n**Primary Target Market** (e.g., \"B2B SaaS for SMBs\", \"Consumer productivity app\"):\n[User input]\n\n**Key Value Proposition** (one sentence - what unique value do you provide?):\n[User input]\n\n✓ Product information captured\n```\n\nCreate `.claude\u002Fproduct-context\u002Fproduct-info.md`:\n\n```markdown\n# Product Information\n\n**Product Name:** [name]\n**Stage:** [stage]\n**Last Updated:** [current date]\n\n## Description\n\n[description]\n\n## Target Market\n\n[target market]\n\n## Value Proposition\n\n[value proposition]\n\n## Product Type\n\n[Infer from description: Web app, Mobile app, API\u002FPlatform, Desktop app, etc.]\n```\n\n---\n\n### Step 2: Tech Stack (Required)\n\n```\n═══════════════════════════════════════════════════════════\nStep 2 of 2 (Required): Tech Stack\n═══════════════════════════════════════════════════════════\n\nWhat's your technology stack? This helps agents give specific technical guidance.\n\n**Frontend** (e.g., React, Vue, SwiftUI, Flutter):\n[User input]\n\n**Backend** (e.g., Node.js, Python\u002FDjango, Go, Ruby\u002FRails):\n[User input]\n\n**Database** (e.g., PostgreSQL, MongoDB, MySQL):\n[User input]\n\n**Infrastructure** (e.g., AWS, Vercel, Railway, self-hosted):\n[User input]\n\n**Architecture Pattern** (select one):\n1. Monolith\n2. Microservices\n3. Serverless\n4. Hybrid\n\nYour choice (1-4):\n[User input]\n\n**Key Technical Constraints** (optional, one per line, or type \"none\"):\n[User input - allow multiple lines]\n[User types \"none\" or \"done\" when finished]\n\n✓ Tech stack captured\n```\n\nCreate `.claude\u002Fproduct-context\u002Ftech-stack.md`:\n\n```markdown\n# Tech Stack\n\n**Last Updated:** [current date]\n\n## Stack\n\n- **Frontend:** [frontend]\n- **Backend:** [backend]\n- **Database:** [database]\n- **Infrastructure:** [infrastructure]\n\n## Architecture\n\n[architecture pattern]\n\n## Technical Constraints\n\n[list constraints, or \"None specified\"]\n```\n\n---\n\n### Step 3: Optional Context Files\n\nAfter completing the 2 required files:\n\n```\n═══════════════════════════════════════════════════════════\nOptional Context Files\n═══════════════════════════════════════════════════════════\n\nGreat! You've completed the required files. Would you like to add optional\ncontext files now? These are helpful if applicable to your situation:\n\n1. strategic-goals.md - Vision, goals, priorities (we can help with product-strategist)\n2. business-metrics.md - Current metrics, growth rates (only if post-launch)\n3. team-info.md - Team size, velocity, capacity (only if team > 1)\n4. None - Skip optional files for now\n\nSelect files to create (comma-separated, e.g., \"1,2\" or \"4\" for none):\n[User input]\n```\n\n#### Optional: Strategic Goals\n\nIf user selects option 1:\n\n```\n═══════════════════════════════════════════════════════════\nOptional: Strategic Goals\n═══════════════════════════════════════════════════════════\n\nDo you have a product vision and strategic goals defined?\n\n1. Yes - I have them ready to share\n2. No - Help me develop them with product-strategist agent\n3. Skip for now\n\nYour choice (1\u002F2\u002F3):\n```\n\n**If choice = 1 (Has goals):**\n\n```\nGreat! Let's capture your strategic direction.\n\n**Product Vision** (one sentence - where are you headed in 3-5 years?):\n[User input]\n\n**Top 3 Strategic Priorities** (for current quarter\u002Fperiod):\n1. [User input]\n2. [User input]\n3. [User input]\n\n**Key Success Metrics** (what metrics define success? optional):\n1. [User input or \"Skip\"]\n2. [User input or \"Skip\"]\n3. [User input or \"Skip\"]\n\n✓ Strategic goals captured\n```\n\nCreate `.claude\u002Fproduct-context\u002Fstrategic-goals.md`:\n\n```markdown\n# Strategic Goals\n\n**Period:** [Current quarter\u002Fyear]\n**Last Updated:** [current date]\n\n## Product Vision\n\n[vision statement]\n\n## Strategic Priorities\n\n1. [priority 1]\n2. [priority 2]\n3. [priority 3]\n\n## Key Success Metrics\n\n[list metrics, or \"To be defined\"]\n```\n\n**If choice = 2 (Needs help):**\n\n```\nPerfect! I'll invoke product-strategist to help you develop vision and strategic goals.\n\nRouting to product-strategist agent...\n```\n\n**Invoke product-strategist agent:**\n\n```\nUse the Task tool to invoke:\n\nTask(\n  subagent_type: \"product-strategist\",\n  description: \"Develop product vision and goals\",\n  prompt: \"Help develop product vision and strategic goals for this product.\n\nProduct context:\n- Name: [product name]\n- Description: [product description]\n- Stage: [product stage]\n- Target Market: [target market]\n- Value Prop: [value proposition]\n\nPlease help the user:\n1. Craft a compelling 3-5 year product vision (one sentence)\n2. Define 3 strategic priorities for the current quarter\u002Fperiod\n3. Suggest 2-3 key success metrics to track\n\nFocus on outcomes and strategic direction, not feature lists. Keep it concise and actionable.\n\nWhen complete, format the output as:\n\n# Strategic Goals\n\n**Period:** [Current quarter\u002Fyear]\n**Last Updated:** [date]\n\n## Product Vision\n\n[vision statement]\n\n## Strategic Priorities\n\n1. [priority 1]\n2. [priority 2]\n3. [priority 3]\n\n## Key Success Metrics\n\n1. [metric 1]\n2. [metric 2]\n3. [metric 3]\n\nThen save this to .claude\u002Fproduct-context\u002Fstrategic-goals.md\"\n)\n```\n\nAfter agent completes:\n\n```\n✓ Vision and strategic goals developed with product-strategist\n✓ Saved to strategic-goals.md\n```\n\n**If choice = 3 (Skip):**\n\n```\nSkipping strategic goals for now. You can add this later with:\n\u002Fpm-setup --update\n```\n\n#### Optional: Business Metrics\n\nIf user selects option 2:\n\n```\n═══════════════════════════════════════════════════════════\nOptional: Business Metrics\n═══════════════════════════════════════════════════════════\n\nLet's capture your current metrics (provide what you track, skip what you don't).\n\n**User Metrics:**\n- Total active users (MAU): [User input or \"Skip\"]\n- User growth rate (% per month): [User input or \"Skip\"]\n\n**Revenue Metrics** (if applicable):\n- MRR or ARR: [User input or \"Skip\"]\n- Revenue growth rate: [User input or \"Skip\"]\n\n**Engagement:**\n- Retention Day 30: [User input or \"Skip\"]\n- Key engagement metric: [User input or \"Skip\"]\n\n✓ Business metrics captured\n```\n\nCreate `.claude\u002Fproduct-context\u002Fbusiness-metrics.md`:\n\n```markdown\n# Business Metrics\n\n**Last Updated:** [current date]\n\n## User Metrics\n\n[list provided metrics or \"Not tracking yet\"]\n\n## Revenue Metrics\n\n[list provided metrics or \"Pre-revenue\"]\n\n## Engagement Metrics\n\n[list provided metrics or \"To be measured\"]\n```\n\n#### Optional: Team Information\n\nIf user selects option 3:\n\n```\n═══════════════════════════════════════════════════════════\nOptional: Team Information\n═══════════════════════════════════════════════════════════\n\n**Team Size:**\n- Product\u002FPM: [User input]\n- Engineering: [User input]\n- Design: [User input]\n- Other: [User input or \"0\"]\n\n**Work Cadence** (select one):\n1. Solo builder (just me)\n2. Scrum (2-week sprints)\n3. Kanban (continuous flow)\n4. Other\n\nYour choice (1-4):\n[User input]\n\n**Velocity** (if you track it):\n- Story points per sprint: [User input or \"Not tracked\"]\nOR\n- Features per month: [User input or \"Not tracked\"]\n\n✓ Team info captured\n```\n\nCreate `.claude\u002Fproduct-context\u002Fteam-info.md`:\n\n```markdown\n# Team Information\n\n**Last Updated:** [current date]\n\n## Team Size\n\n- Product\u002FPM: [count]\n- Engineering: [count]\n- Design: [count]\n- Other: [count]\n\n**Total:** [sum] people\n\n## Work Cadence\n\n[cadence type and details]\n\n## Velocity\n\n[velocity info or \"Not tracked\"]\n```\n\n---\n\n### Final Summary\n\nDisplay completion summary:\n\n```\n═══════════════════════════════════════════════════════════\n✅ Setup Complete!\n═══════════════════════════════════════════════════════════\n\nContext files created in .claude\u002Fproduct-context\u002F:\n\nRequired:\n✓ product-info.md - [Product Name] ([Stage])\n✓ tech-stack.md - [Frontend] + [Backend] stack\n\n[If optional files were created]:\nOptional:\n✓ strategic-goals.md - Vision and priorities [+ product-strategist ✨ if invoked]\n✓ business-metrics.md - [Key metrics]\n✓ team-info.md - [Team size] team\n\n───────────────────────────────────────────────────────────\n\n**Next:** Tell product-manager what you need, or invoke a specialist agent directly.\n\n**Update context anytime:** `\u002Fai-pm-copilot:pm-setup --update`\n```\n\n---\n\n## Update Mode\n\nIf user runs `\u002Fpm-setup --update`:\n\n```\n╔═══════════════════════════════════════════════════════════╗\n║   Update Product Management Context                       ║\n╔═══════════════════════════════════════════════════════════╝\n\nWhich files would you like to update?\n\nEssential:\n1. ⬜ product-info.md (last updated: [date])\n2. ⬜ tech-stack.md (last updated: [date])\n\nOptional:\n3. ⬜ strategic-goals.md (last updated: [date]) [⚠️ if >3 months old]\n4. ⬜ business-metrics.md (last updated: [date]) [⚠️ if >1 month old]\n5. ⬜ team-info.md (last updated: [date])\n\nCreated by journey (usually updated by agents):\n6. ⬜ competitive-landscape.md (last updated: [date])\n7. ⬜ customer-segments.md (last updated: [date])\n8. ⬜ current-roadmap.md (last updated: [date])\n\n9. All files\n\nSelect files to update (comma-separated, e.g., \"1,3\" or \"9\" for all):\n[User input]\n```\n\nFor each selected file:\n\n- Re-run that file's questions\n- Show current values: `Current: [value]. Press Enter to keep, or type new value:`\n- For strategic-goals: Offer product-strategist help again if updating\n- Update only changed values\n- Update \"Last Updated\" timestamp\n\n---\n\n## Validation\n\nAfter each step, validate that essential information is provided:\n\n**Essential per required file:**\n\n- product-info.md: name, description, stage, target market, value prop (all required)\n- tech-stack.md: frontend, backend, database, infrastructure, architecture (all required)\n\n**For optional files:**\n\n- strategic-goals.md: at least vision OR 3 priorities\n- business-metrics.md: at least 2 metrics\n- team-info.md: team size and cadence\n\nIf essential fields missing:\n\n```\n⚠️  Missing required information:\n- [Field name]: [Brief explanation of why it's needed]\n\nWould you like to:\n1. Provide this information now\n2. Cancel this file\n\nYour choice (1\u002F2):\n```\n\n---\n\n## Error Handling\n\n**If .claude\u002F directory doesn't exist:**\n\n```bash\nmkdir -p .claude\u002Fproduct-context\n```\n\n**If file write fails:**\n\n```\n❌ Error writing to [file_path]\n\nPossible issues:\n- Directory permissions\n- Disk space\n\nWould you like to:\n1. Retry\n2. Skip this file\n3. Cancel setup\n\nYour choice (1\u002F2\u002F3):\n```\n\n**If agent invocation fails** (for strategic-goals):\n\n```\n❌ Error invoking product-strategist agent\n\nFalling back to manual input. Let's capture your strategic direction:\n\n[Proceed with manual questions for strategic-goals]\n```\n\n**If user quits mid-setup:**\n\n```\nSetup incomplete. Files created so far:\n✓ product-info.md\n❌ tech-stack.md (not created)\n\nRequired files are incomplete. Please run \u002Fpm-setup again to finish.\n```\n\n",{"name":5,"description":7,"allowed-tools":23,"argument-hint":24,"user-invocable":25,"disable-model-invocation":25},"Read, Glob, Grep, Write, Task, AskUserQuestion","[--update]",true,"main","a4b48842f3e48549adf3dc335a8837c66da99497","agents\u002Fplugins\u002Fai-pm-copilot\u002Fskills\u002Fpm-setup",0,"https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng","2026-05-17 16:00:01",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":25},[35,38,41],{"tool":36,"command":37},"npx","npx skills add enigmaicon-eng\u002FAI-Enterprise-OS --skill pm-setup",{"tool":39,"command":40},"bunx","bunx skills add enigmaicon-eng\u002FAI-Enterprise-OS --skill pm-setup",{"tool":42,"command":43},"pnpm","pnpm dlx skills add enigmaicon-eng\u002FAI-Enterprise-OS --skill pm-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fagents\u002Fplugins\u002Fai-pm-copilot\u002Fskills\u002Fpm-setup\u002FSKILL.md",[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M72ZGWW03JSE1T3TKK5NZ11Y","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M72ZGT3FJT7QRM1VNQRKR0XD","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M72ZGQ69DCF0SBP9JXFPWKJS","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M72ZGNF126QT0MQ2D3DNGZRN","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fusing-superpowers\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M72ZGHVJ9S0YXMNBHQGQ95BY","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M72ZGFNZCHFY2FS3ZD9MCYV9","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[]]