Installation

One line starts the interactive installer that sets up your project-management Agent Skills:

npx agentic-pm-kit install

The installer asks you 10 questions, writes the files into your project, and records your answers in .pm-kit.config.json. There is no telemetry, and no network calls during installation beyond the initial npm package download.

The install walkthrough: 10 questions

Question 1 — Install target directory

The installer proposes your current working directory as the destination and asks if you want to use it. If you answer "No," it prompts for the absolute path to your project directory.

When to change it: when you want to install into a repository subdirectory or a project that is not the current directory.

Question 2 — Project name

Free-form text. The name is used to generate the docs/pm-kit/README.md for your project and is stored in the config.

Example of a good answer: BookSwap Campus

Question 3 — Project description

One sentence describing your project. Also used in the generated README and gives the skills context when you invoke them.

Example of a good answer: Peer-to-peer used-textbook marketplace for university students in Mexico

Question 4 — Agent target(s)

Multi-select. The options are Claude Code and Gemini CLI; both are checked by default. You can choose only one if you don't use the other.

Why it matters: the install paths are different for each agent (see On-disk layout below). If you select Gemini CLI, skills are installed in a user-global location that is shared across all your Gemini projects.

Question 5 — Agent communication language

Free-form text. Type the language you want the agent to speak during facilitation.

Example of a good answer: English

Other valid options: español, português, français, kichwa — any natural language you type is stored verbatim in the config and the agent honors it.

Question 6 — Artifact output language

Free-form text. The language in which the agent should draft the final artifacts (charters, WBS, risk matrices, etc.). If you leave it blank, it defaults to the same language as the communication language.

When to differ: if you want the agent to walk you through the process in Spanish but deliver artifacts in English because your client requires it, type English here and español in the previous question.

Question 7 — Modules to install

Multi-select. All are checked by default. The available modules are:

If you only need one phase of the lifecycle, uncheck the rest.

Question 8 — Brainstorming deck

Single-select. The options are:

• Curated 20 (recommended): the 20 strategies optimized for PM context. This is the default.
• Full 60: includes the 20 curated strategies plus ~40 general-purpose strategies that are not PM-specific. In v1 this option installs the curated 20-strategy deck while the additional strategies are being authored.

Question 9 — Authoritative-source mode

Single-select. The options are:

• Offline (default): skills use only the bundled sources — the Scrum Guide 2020 and the Agile Manifesto in English and Latin American Spanish — plus the agent's general knowledge of PMBOK concepts. No network calls on each skill invocation. Predictable, no runtime network dependency, and the right choice for most use cases.
• Online (opt-in): skills instruct the agent to fetch the relevant canonical URLs before drafting. This gives access to public PMI pages and other up-to-date sources. It does not solve access to paywalled content (full PMBOK, ISO 21500), but for users who want maximum grounding in current sources it is the right option.

Question 10 — Install summary and final confirmation

Before writing any files, the installer shows a complete summary of all your answers: target directory, project name and description, selected agents, the paths where skills will be written, languages, modules, brainstorming deck, and source mode. You confirm with "Yes" to proceed or "No" to cancel with no changes.

On-disk layout

The installer always writes these files per project, regardless of which agents you selected:

<your-project>/
├── docs/
│   └── pm-kit/
│       ├── README.md            ← generated with your project name and description
│       ├── checklists/          ← one acceptance checklist per installed artifact
│       ├── templates/           ← blank starter templates per artifact
│       └── outputs/             ← your agent-generated artifacts land here
├── vendor/
│   └── pm-kit/
│       ├── scrum-guide-en.md    ← Scrum Guide 2020 in English (CC BY-SA 4.0)
│       ├── scrum-guide-es.md    ← Scrum Guide 2020 in Latin American Spanish
│       ├── agile-manifesto.md   ← full text + copyright notice
│       └── sources-index.json   ← PMI/ISO URLs with freshness dates
│   └── bmad/
│       └── LICENSE              ← MIT license for vendored open-source content
└── .pm-kit.config.json          ← your install answers; base for subsequent runs

The skill paths depend on which agent(s) you selected:

Claude Code only

Claude Code auto-discovers skills from the project root. No additional configuration required.

<your-project>/
└── .claude/
    └── skills/
        └── pm-kit/
            ├── brainstorming-five-whys/
            │   └── SKILL.md
            ├── brainstorming-question-storming/
            │   └── SKILL.md
            ├── ... (up to 20 brainstorming strategies)
            ├── charter/
            │   └── SKILL.md
            ├── stakeholder-register/
            │   └── SKILL.md
            ├── prd/
            │   └── SKILL.md
            └── ... (skills for installed modules)

Gemini CLI only

Gemini CLI discovers extensions from ~/.gemini/extensions/ at the user level, not from the project directory. This means pm-kit skills are shared across all your Gemini CLI projects. The installer creates an extension with a gemini-extension.json manifest and places skills under ~/.gemini/extensions/pm-kit/skills/.

~/ (user home directory)
└── .gemini/
    └── extensions/
        └── pm-kit/
            ├── gemini-extension.json    ← extension manifest
            └── skills/
                ├── brainstorming-five-whys/
                │   └── SKILL.md
                ├── brainstorming-question-storming/
                │   └── SKILL.md
                ├── ... (up to 20 brainstorming strategies)
                ├── charter/
                │   └── SKILL.md
                ├── stakeholder-register/
                │   └── SKILL.md
                └── ... (skills for installed modules)

Claude Code + Gemini CLI

When you select both agents, the installer writes both trees:

<your-project>/
├── .claude/
│   └── skills/
│       └── pm-kit/
│           └── ... (per-project skills for Claude Code)
├── docs/
│   └── pm-kit/  (always per-project)
├── vendor/      (always per-project)
└── .pm-kit.config.json

~/ (user home directory)
└── .gemini/
    └── extensions/
        └── pm-kit/
            ├── gemini-extension.json
            └── skills/
                └── ... (user-global skills for Gemini CLI)

Languages

Free-form language input

The language fields accept any text string you type — there is no fixed menu. The value is stored verbatim in .pm-kit.config.json and passed to the agent as-is.

Languages with best coverage in bundled sources: English and Latin American Spanish (the Scrum Guide ships in both). For any other language the agent translates on demand; quality depends on the agent's own translation capability.

language.communication vs language.output

The config stores two separate language fields:

• language.communication — the language the agent uses when speaking to you during facilitation: asking questions, explaining steps, confirming decisions. This is "the agent's voice."
• language.output — the language used to draft the final artifacts. This is the language of the charter, WBS, risk matrix, etc.

You can set them to the same value (most common) or to different values. Example: communication in Spanish, artifacts in English for an international client.

Source mode

Offline (default)

Skills use only the bundled sources: the Scrum Guide 2020 (English and Latin American Spanish) and the Agile Manifesto. For PMBOK references, skills instruct the agent to cite concepts at the level of named principles and performance domains, without fabricating page numbers, direct quotations, or invented structural details. When the agent is uncertain about a specific PMBOK fact, it says so explicitly and points the reader to the canonical URL in vendor/pm-kit/sources-index.json.

This mode is predictable, requires no per-invocation network connection, and is the right choice for most use cases.

Online (opt-in)

In online mode, skills also instruct the agent to fetch the relevant canonical URLs before drafting. This gives access to public PMI pages, the available online PMBOK table of contents, and other up-to-date sources. It does not solve access to paywalled content, but for users who want maximum grounding in current sources it is the right option.

Enable it at question 9 in the installer, or pass --online-mode to the command:

npx agentic-pm-kit install --online-mode

You can switch modes after the initial install through the subsequent-run menu.

Subsequent runs

When you run npx agentic-pm-kit (without the install subcommand) inside a directory that already has .pm-kit.config.json, the installer detects the existing installation and opens a menu with the following options:

• Add / remove modules — install or uninstall lifecycle modules without reinstalling everything.
• Change language — update the communication or artifact output language.
• Switch source mode — toggle between offline and online.
• Reinstall — refresh all skills and vendor files to the current package version (useful after npm update).
• Uninstall — remove .claude/skills/pm-kit/, the Gemini CLI global extension, docs/pm-kit/, vendor/pm-kit/, and the config file. Artifacts you have generated in docs/pm-kit/outputs/ are not touched during a reinstall; they are removed during a full uninstall.

Troubleshooting

The npx agentic-pm-kit command is not found

The installer requires Node.js 18 or later. Check your version:

node --version

If node is not installed or the version is below 18, download Node.js from nodejs.org (choose the LTS version). Bun 1.0+ also works:

bun --version
bunx agentic-pm-kit install

If node is installed but npx can't find the package, ensure the npm bin directory is in your PATH.

Permission errors on the Gemini CLI global install path

If the installer fails when writing to ~/.gemini/extensions/pm-kit/, the most likely cause is that the ~/.gemini/ directory was previously created by another process running as root. To verify and fix:

ls -la ~/.gemini/
# If the owner is not you, run:
sudo chown -R $USER:$USER ~/.gemini/

How to restart with a clean config

To run the installer from scratch as if it were the first time:

rm .pm-kit.config.json
npx agentic-pm-kit install

This removes the existing config and launches the full 10-question interactive flow. Existing skill and vendor files are overwritten with the new installation. Artifacts you have generated in docs/pm-kit/outputs/ are not modified.

How to uninstall

npx agentic-pm-kit

The subsequent-run menu appears automatically when .pm-kit.config.json is detected. Select Uninstall to remove:

• <your-project>/.claude/skills/pm-kit/ (if Claude Code was installed)
• ~/.gemini/extensions/pm-kit/ (if Gemini CLI was installed)
• <your-project>/docs/pm-kit/
• <your-project>/vendor/pm-kit/
• <your-project>/.pm-kit.config.json

Artifacts in docs/pm-kit/outputs/ are removed along with the rest during a full uninstall. Move them before uninstalling if you want to keep them.

Command-line flags

The next step is to invoke your first skill. Start with the Ideation module to develop your project concept before drafting the charter.