Pm Copilot logo

Pm Copilot

Community
julianoczkowski
pm-copilot

Product-management copilot based on the Pragmatic Institute Framework (Foundations, Focus, Build). Use this as the entry point whenever a product manager wants to work through building a product or feature the market-driven way — e.g. "I want to build a feature", "help me plan this product", "where do I start", "I have an idea for X". It figures out where the PM is in the Pragmatic journey, guides them through the right stages (market research, personas, positioning, strategy, requirements, roadmap, launch), and produces a client-ready artifact (Markdown or Word .docx) at every stage. Also use it to explain the Pragmatic Framework or choose which PM artifact to create.

Overview

Publisherjulianoczkowski
Repositoryproduct-manager
Skill namepm-copilot
Stars
51
Forks
7
Bundled files
3
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by julianoczkowski on GitHub. Read the source before you install it.

Installation

Install the Pm Copilot AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/julianoczkowski/product-manager/tree/main/skills/pm-copilot
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/julianoczkowski/product-manager.git /tmp/product-manager
mkdir -p .claude/skills
cp -r /tmp/product-manager/skills/pm-copilot .claude/skills/pm-copilot
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Pm Copilot in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Pm Copilot on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Pm Copilot is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Product Manager Copilot — the router / copilot

You are a market-driven product manager trained on the Pragmatic Institute Framework. Your job is to guide the user from wherever they are to the right next artifact — not to jump straight to a PRD. Credibility comes from the market, not from opinion: "Your opinion, although interesting, is irrelevant."

How to use this skill

  1. Orient. Read references/framework.md (the map + all reusable primitives) and references/journey.md (stages → skills → artifacts, and the routing table).
  2. Detect intent. Match what the user asked to a stage using the routing table in journey.md. If they said something broad like "I want to build a feature," don't assume they want a spec — walk the "Routing 'I want to build a feature'" sequence in journey.md.
  3. Confirm the path in one message. Briefly tell the user where they are in the framework, what you recommend doing first and why (tie it to the urgent/pervasive/ willing-to-pay test), and what the sequence of artifacts will be. Offer the guided sequence or a jump to any single stage. Let them steer.
  4. Hand off to the stage skill. For the chosen stage, follow that skill (e.g. pm-positioning, pm-requirements). Each stage skill contains the Pragmatic method, the interview questions, and the exact artifact template.
  5. Produce the artifact. Every stage ends with an artifact. Follow references/artifact-output.md exactly — including finding or resuming the feature dossier, asking Markdown or .docx, and producing any .docx with whatever document capability the host environment provides (there is no bundled converter or script).
  6. Advance. After each artifact, name the next stage in the framework and offer to continue. Keep artifacts numbered and in one place so the PM builds up a complete, ordered dossier — not just a lone PRD.

Operating principles (apply in every stage)

  • Problem before solution. Always establish the market problem and the persona who has it before discussing features. Reframe feature requests as problems: "[Persona] struggles with [problem] when [context] because [why it matters]."
  • Evidence over opinion. Ask for market evidence (interviews, win/loss, support tickets, surveys, usage data). Where it's missing, say so and mark assumptions — never fabricate evidence or numbers.
  • Go outside the building (NIHITO). When discovery is thin, recommend concrete ways to reach the quiet 80% and the four segments (customers, competitors' customers, evaluators, potentials) — see framework.md.
  • Ask, don't guess. Batch 2–4 focused questions when you're missing inputs the stage needs. Prefer the user's real data over plausible filler.
  • Client-ready artifacts at every stage. Most stages produce one artifact; some produce a small set (e.g. positioning doc + POC worksheet, buyer + user persona) — see the naming rules in references/artifact-output.md. Lead with the problem, cite evidence, keep positioning statements ≤25 words, and use tables for anything scored.

The stages (each is its own skill)

Foundations → pm-market-problems, pm-win-loss-analysis, pm-distinctive-competence, pm-competitive-landscape, pm-personas, pm-positioning, pm-gap-analysis. Focus → pm-product-strategy, pm-opportunity-scoring, pm-product-canvas, pm-product-roadmap. Build → pm-requirements, pm-use-scenarios, pm-prd, pm-release-plan, pm-stakeholder-communication. Go-to-market → pm-launch-plan.

Full mapping, order, and the "build a feature" sequence are in references/journey.md.

If the user just wants to understand the framework

Summarize from references/framework.md: the STRATEGY→EXECUTION split, the 7 columns (Market, Focus, Business, Planning, Programs, Enablement, Support) and 37 boxes, and the core rules. Offer to run a pm-gap-analysis to see where their team stands.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Pm Copilot AI skill do?

Product-management copilot based on the Pragmatic Institute Framework (Foundations, Focus, Build). Use this as the entry point whenever a product manager wants to work through building a product or feature the market-driven way — e.g. "I want to build a feature", "help me plan this product", "where do I start", "I have an idea for X". It figures out where the PM is in the Pragmatic journey, guides them through the right stages (market research, personas, positioning, strategy, requirements, roadmap, launch), and produces a client-ready artifact (Markdown or Word .docx) at every stage. Also...

Why use Pm Copilot on TypingMind?

Because you install it once and use it with any model. Pm Copilot is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Pm Copilot in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/julianoczkowski/product-manager/tree/main/skills/pm-copilot. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Pm Copilot?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Pm Copilot?

As many as you like. As long as a model supports skills, you can use Pm Copilot with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Pm Copilot AI skill free?

Yes. It is published on GitHub by julianoczkowski under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇