PM-Kit plugin
A product manager workspace in Obsidian where standups, decisions, blockers and sprints run as Claude Code commands.
- 140 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Installation runs a script from the network, and a hook makes git commits in the vault by itself.
Install
- Works in
Manual install
curl -fsSL https://raw.githubusercontent.com/kv0906/pm-kit/main/cli/install.sh | bashThe first install command from the README installs the `pm-kit` CLI. The script runs from the network, so read it beforehand; then create a vault with `pm-kit init`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Installation runs a script from the network, and a hook makes git commits in the vault by itself.
This is third-party code. Review the repository files before installing.
What it does
PM-Kit turns an Obsidian notes folder into a product manager workspace. The repository holds skills, agents, rules and hooks for Claude Code. Each command covers one task: `/daily` writes a standup across several projects, `/block` records a blocker, `/decide` drafts a decision with alternatives, `/doc` prepares an evidence-backed PRD and `/weekly` reviews the week. Other commands handle prioritisation (`/prioritize`), root-cause research (`/discover`), user journey maps, an executive brief and questions over the notes (`/ask`, optionally with QMD search). The `pm-kit update` command replaces only framework files and leaves personal notes untouched.
Who it is for. Product managers and engineering leads who keep working notes in Obsidian and want to run them through Claude Code.
Good fit when
- A morning standup across several projects must be logged in a minute.
- A made decision should be saved together with alternatives and reasons.
- A PRD is being prepared before release with every claim tied to a source.
- A manager needs a plain-language weekly report on project status.
Not a fit when
- Notes live outside Obsidian and there is no wish to move them.
- A hosted system with real-time collaboration is required.
- The task is one-off, so a full vault scaffold is excessive.
Example request
Log a standup for the checkout project: new cart shipped, payment in progress, blocked on the test environment. Then record the blocker.Limitations
Built for Claude Code; other agents read only part of the rules. The main install route, `curl ... | bash`, runs a script from the internet, so read it first. Smart `/ask` search needs bun and QMD; without them a plain grep over the vault is used. An auto-commit hook records changes in git by itself. The folder structure and command names are set by the author and can be adapted to your process only by editing files. Some commands work best in English, and documents are created in it by default.
How to disable. Delete the vault or disable the hooks in `.claude/settings.json`. The CLI is removed together with the folder where the install script put it. Notes remain plain Markdown files.
FAQ
Where do I start after installing?
Open the folder in Obsidian, run `claude` and execute `/onboard`. It sets up the project and loads context.
How do I run daily standups?
The `/today` command walks through standup, sync, review, focus and wrap-up. For one entry `/daily project: shipped X, wip Y` is enough.
Does an update touch my notes?
No. `pm-kit update` replaces skills, templates, scripts and docs, while notes and configuration stay. Backups go to `_archive/_updates/`.
Is QMD required?
No. Without it `/ask` uses a plain grep over the vault. QMD adds hybrid search and requires bun.
Which agents work with it?
The main flow is built for Claude Code. For Amp the README describes environment setup through `.agents/setup`.
Discussion
No questions or reviews yet.
Related
PluginsA set of 58 commands for product managers in Claude Code, Codex and Cursor: from an idea and a PRD to launch and growth analysis
An Obsidian vault template for Claude Code: /daily, /weekly, /monthly and /project commands link three-year goals to today's tasks
A scaffold for Claude Code and Codex: tasks in files, developer and QA roles, manual approval and shared state.
A Claude Code skill collects product context in Markdown and links decisions to interviews, documents and hypotheses
PM Skills
PM Skills Marketplace
A plugin marketplace for product managers: discovery, strategy, PRDs, launch, growth and audits of AI-built code
Eight Claude Code skills for Obsidian: Granola notes, NotebookLM imports, TaskNotes tasks, recall of past sessions, chat export
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| PM-Kit (this card) | no | 140 | |
| PM-Skills | no | 803 | a plugin of 17 separate skills for product teams; PM-Kit keeps the work in an Obsidian vault with rules and safe updates |
| PM Skills | no | 27,935 | a marketplace of hundreds of skills and agents; PM-Kit focuses on a manager's daily work in one notes vault |
README in short
The README walks through CLI install, vault creation and first run, then lists commands, Amp orb setup and optional QMD search. Updates touch framework files only.