Verified:GitHub

pm-org

Generate an ORG.md mapping team roles and decision rights from git history and artifacts.

42|2|Updated Mar 28, 2026

Search Tags:#product-management #stakeholders #reverse-engineering #team-structure #decision-rights #org-research #org-map

Ready to run

npx skills add https://github.com/nmrtn/nanopm --skill pm-org

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-org
Source: https://github.com/nmrtn/nanopm/tree/main/pm-org
Command: npx skills add https://github.com/nmrtn/nanopm --skill pm-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Org knowledge is often scattered, making it hard for new PMs to understand who owns what, who decides, and how the team actually works. This Skill maps roles, decision rights, and operating rhythms into a single, shareable ORG.md.

Core Features & Use Cases

Reverse-engineers the org from git history, repo artifacts, and public team pages to surface who’s who and who decides what.
Generates ORG.md with ownership, decision rights, team shape, and ways of working to accelerate onboarding and alignment.
Useful for startup teams, small product squads, and new PMs onboarding into established orgs.

Quick Start

Run /pm-org to generate ORG.md for your project, documenting who does what and how decisions get made.

Frequently Asked Questions about pm-org

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

FAQPage Schema

How do I map team decision rights and stakeholders for a new PM onboarding?▼

Map team decision rights and stakeholders by reverse-engineering git history, repo artifacts, and public pages to draft an ORG.md. This single document defines ownership, decision rights, team structure, and operating rhythms to accelerate PM onboarding and alignment.

What is an ORG.md file and how does it document team structure?▼

An ORG.md file documents team structure by consolidating scattered org knowledge into defined ownership, decision rights, and ways of working. It surfaces who’s who and who decides what, making it easier for product squads to maintain alignment.

How do I reverse-engineer an org map from git history and repo artifacts?▼

Reverse-engineer an org map from git history by collecting evidence from repo contributors, commit history, and public team pages. This evidence drafts a comprehensive ORG.md mapping roles, decision rights, and operating rhythms for teams lacking clear organizational documentation.

Can I use this to document ways of working for small to mid-sized product teams?▼

Yes, you can document ways of working for small to mid-sized product teams lacking clear org maps. The Skill applies to small to mid-sized teams or projects, reverse-engineering artifacts to define operating rhythms and team shape within a shareable ORG.md file.

What's the best way to generate an org map for a project lacking clear documentation?▼

The best way to generate an org map for a project lacking clear documentation is to run /pm-org, which collects evidence from repo history, contributors, public pages, and internal notes to draft an ORG.md with defined ownership, decision rights, and team structure.

When should I not use reverse-engineering to map stakeholders and decision rights?▼

You should not use reverse-engineering to map stakeholders and decision rights if your team's git history, repo artifacts, and public pages lack sufficient evidence to accurately determine ownership, team structure, and operating rhythms for a reliable ORG.md.