$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill solo-to-cpoUse this skill when the user asks about "career path to CPO", "how do I become a CPO", "PM career progression", "path from PM to VP Product", "PM career growth", "how do I grow as a PM", "what does the PM career ladder look like", "solo PM to product leader", or wants to understa
| 1 | # Solo PM → Founding PM → CPO Career Arc |
| 2 | |
| 3 | You are helping the user understand and plan their PM career trajectory. The PM career is not a linear ladder — it's a series of capability expansions, each requiring different skills and different proofs of competency. |
| 4 | |
| 5 | Framework: Jackie Bavaro (Cracking the PM Career), Lenny Rachitsky (PM career survey, communication as most valued skill), Shreyas Doshi (altitude and horizon framework). |
| 6 | |
| 7 | ## Step 1 — Load Context |
| 8 | |
| 9 | Read `memory/user-profile.md` for the user's current role context and product stage. This determines where they are on the arc and what the next step looks like. |
| 10 | |
| 11 | ## Step 2 — The Arc |
| 12 | |
| 13 | **Stage 1 — Solo PM (PM0 / PM1):** |
| 14 | You're doing all PM activities: discovery, execution, stakeholder management, metrics. No specialization yet. The test: can you own an outcome end-to-end without needing constant guidance? |
| 15 | |
| 16 | Core skills to develop: problem framing, user research synthesis, PRD writing, stakeholder communication, prioritization. |
| 17 | Evidence to demonstrate: "Here's a feature I owned end-to-end, from discovery to launch to measured impact." |
| 18 | |
| 19 | **Stage 2 — Senior PM:** |
| 20 | You influence beyond your product area. You drive strategy, not just execution. You make other people around you better. |
| 21 | The test: can you work at the strategy level without prompting? Can you tell the difference between an execution problem and a strategy problem? |
| 22 | |
| 23 | Core skills to develop: strategy-stack thinking, OKR definition, competitive positioning, stakeholder influence without authority. |
| 24 | Evidence to demonstrate: "Here's a strategic decision I drove that changed what the company built." |
| 25 | |
| 26 | **Stage 3 — Principal PM / Staff PM:** |
| 27 | You set the product direction for a whole area. You represent the product point of view in leadership conversations. You mentor and develop other PMs. |
| 28 | The test: can you develop the product vision for an area, defend it with evidence, and execute against it across multiple teams? |
| 29 | |
| 30 | **Stage 4 — Director of Product:** |
| 31 | You manage PMs and scale PM craft across a team. You're responsible for the health of the PM function as well as product outcomes. |
| 32 | The test: can you hire and develop great PMs? Can you create an environment where good product thinking happens even when you're not in the room? |
| 33 | |
| 34 | **Stage 5 — VP Product / CPO:** |
| 35 | You own the entire product strategy and P&L implications. You influence company strategy, not just product decisions. You're the voice of the customer and the customer of the engineering organization. |
| 36 | The test: can you set a product vision that attracts talent, convinces investors, and aligns the whole company? |
| 37 | |
| 38 | ## Step 3 — Current Stage Assessment |
| 39 | |
| 40 | Based on what the user shares, assess: |
| 41 | - Which stage are they at currently? |
| 42 | - What is the primary gap between their current stage and the next? |
| 43 | - Which skills are strong, which are underdeveloped? |
| 44 | |
| 45 | Lenny's survey data on most valued PM skills (n=1,000, 600+ companies): |
| 46 | 1. Communication (most valued) |
| 47 | 2. Execution |
| 48 | 3. Product sense |
| 49 | |
| 50 | If any of these three are weak, they're the priority before anything else. |
| 51 | |
| 52 | ## Step 4 — Next Step Plan |
| 53 | |
| 54 | For the user's next stage, define: |
| 55 | |
| 56 | **Skill to build:** What's the highest-leverage capability to develop in the next 6 months? |
| 57 | |
| 58 | **Evidence to create:** What specific work product would prove this capability to a hiring manager or promotion committee? |
| 59 | |
| 60 | **Opportunity to seek:** What type of project, team, or initiative gives the best context to develop this skill? |
| 61 | |
| 62 | **Reading/learning:** Which resources would most directly develop this skill? (Reference: Bavaro's Cracking the PM Career, Doshi's articles on Linkedin, Lenny's newsletter archives) |
| 63 | |
| 64 | **Mentor to find:** What type of person would most accelerate this development? (A CPO who was a solo PM? A principal PM who crossed the strategy-execution boundary?) |
| 65 | |
| 66 | ## Step 5 — The Founding PM Path |
| 67 | |
| 68 | If the user is on the founding PM path (early-stage company, first PM): |
| 69 | |
| 70 | The Founding PM role is uniquely high-stakes and high-growth. Specifics: |
| 71 | - You'll do everything: discovery, strategy, roadmap, PRD, QA, CS, analytics — simultaneously |
| 72 | - The test is: did the product ship? Did users care? Did the company survive? |
| 73 | - The skill that matters most: judgment under ambiguity. There's no playbook. |
| 74 | - What to prioritize: Get to PMF evidence. Every week that doesn't move toward PMF evidence is a week too long. |
| 75 | - The accelerant: AI assistance (like PM Copilot) can function like having a senior PM peer — especially for frameworks and structure the Founding PM hasn't developed muscle memory for yet. |
| 76 | |
| 77 | ## Step 6 — Output |
| 78 | |
| 79 | Produce: |
| 80 | - Arc stage asse |