pm-kit
AI-augmented PM workspace for Coding Agents — daily standups, decisions, blockers, docs, and sprint reviews as markdown skills
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
Its scripts were only partly scanned.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/kv0906/pm-kit with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/kv0906/pm-kit'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/kv0906--pm-kit)HTML
<a href="/listings/kv0906--pm-kit"><img src="/api/listings/kv0906--pm-kit/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
These steps run a script from the network that findsafeskills does not scan.
Option A: CLI Install (Recommended)
# 1. Install the CLI curl -fsSL https://raw.githubusercontent.com/kv0906/pm-kit/main/cli/install.sh | bash # 2. Create your vault pm-kit init ~/Documents/my-vault cd ~/Documents/my-vault # 3. Open the folder in Obsidian, then run Claude Code claude /onboard
Option B: GitHub Template
# 1. Use this template on GitHub (or clone) git clone <your-repo-url> cd pm-kit # 2. Open the folder in Obsidian # 3. Run Claude Code claude /onboard
`/onboard` sets up your project, learns your preferences, and loads context. Full walkthrough: **[START_HERE.md](START_HERE.md)**
Amp Orbs
Fresh Amp orbs run `.agents/setup` to prepare shell tools and locked document-export dependencies (Python, Node, LibreOffice, Pandoc, PDF tools, and OCR). Amp can reuse the prepared snapshot; warm setup checks existing packages instead of reinstalling them. `.agents` is a symlink to `.claude`, where the lifecycle scripts are tracked.
The setup does not run the interactive vault wizard, edit your notes or configuration, or authenticate integrations. QMD and account-specific integrations remain optional. There are no persistent services to start; `.agents/resume` performs no installs. New login shells inside the repository automatically use the document-tools Python environment and Node module path.
To verify setup manually from the repository root:
./.agents/setup ./.agents/resume bash -lc 'python -c "import openpyxl, reportlab"; node -e "require(\"docx\"); require(\"pptxgenjs\")"'
Dependency manifests and locks live in `.claude/orb/`. To update them, edit `requirements.in` or `package.json`, regenerate the corresponding lock, and commit it:
uv pip compile .claude/orb/requirements.in -o .claude/orb/requirements.txt --python-version 3.11 npm install --prefix .claude/orb --package-lock-only --ignore-scripts
Orb setup must reach the project's default branch before future orbs use it.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 243 lines · 1 finding marked
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- 
- # PM-Kit
- Turn your AI coding tool into a PM workspace, knowledge hub, and execution engine.
- ## Disclaimer
- This is not gospel. This is not the holy grail.
- PM-Kit is one system that works. It is a guideline and mindset shift, not a rigid rulebook.
- The principles in `_core/MANIFESTO.md` may resonate with you, or they may not. That is fine.
- Take what works. Ignore what does not. Make it yours.
- You will get better results through repetition. The framework should adapt to your workflow, not the other way around.
- ## Quick Start
- ### Option A: CLI Install (Recommended)
- ```bash
- # 1. Install the CLI
- curl -fsSL https://raw.githubusercontent.com/kv0906/pm-kit/main/cli/install.sh | bash
- Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
- Line 24 on GitHub
- # 2. Create your vault
- pm-kit init ~/Documents/my-vault
- cd ~/Documents/my-vault
- # 3. Open the folder in Obsidian, then run Claude Code
- claude
- /onboard
- ```
- ### Option B: GitHub Template
- ```bash
- # 1. Use this template on GitHub (or clone)
- git clone <your-repo-url>
- cd pm-kit
- # 2. Open the folder in Obsidian
- # 3. Run Claude Code
- claude
- /onboard
- ```
- `/onboard` sets up your project, learns your preferences, and loads context. Full walkthrough: **[START_HERE.md](START_HERE.md)**
- ### Amp Orbs
- Fresh Amp orbs run `.agents/setup` to prepare shell tools and locked document-export
- dependencies (Python, Node, LibreOffice, Pandoc, PDF tools, and OCR). Amp can reuse
- the prepared snapshot; warm setup checks existing packages instead of reinstalling them.
- `.agents` is a symlink to `.claude`, where the lifecycle scripts are tracked.
- The setup does not run the interactive vault wizard, edit your notes or configuration,
- or authenticate integrations. QMD and account-specific integrations remain optional.
- There are no persistent services to start; `.agents/resume` performs no installs.
- New login shells inside the repository automatically use the document-tools Python
- environment and Node module path.
- To verify setup manually from the repository root:
- ```bash
- ./.agents/setup
- ./.agents/resume
- bash -lc 'python -c "import openpyxl, reportlab"; node -e "require(\"docx\"); require(\"pptxgenjs\")"'
- ```
- Dependency manifests and locks live in `.claude/orb/`. To update them, edit
- `requirements.in` or `package.json`, regenerate the corresponding lock, and commit it:
- ```bash
- uv pip compile .claude/orb/requirements.in -o .claude/orb/requirements.txt --python-version 3.11
- npm install --prefix .claude/orb --package-lock-only --ignore-scripts
- ```
- Orb setup must reach the project's default branch before future orbs use it.
- ## Daily Routine
- ```
- /today # Guided workflow: standup → sync → review → focus → wrap-up
- /today wrap # Jump to end-of-day summary
- ```
- Or for quick atomic updates:
- ```
- /daily my-project: shipped X, wip Y, blocked on Z
- /push
- ```
- ## Weekly Routine
- ```
- /weekly
- /push
- ```
- ## Updating
- ```bash
- # CLI users
- pm-kit update # Update framework files from latest release
- pm-kit self-update # Update the CLI itself
- # Template users
- ./scripts/update.sh # Update framework files from latest release
- ```
- Or from within Claude: `/update`
- Updates only touch framework files (skills, templates, scripts, docs). Your notes, config, and content are never modified. Backups are saved to `_archive/_updates/`.
- ## All Commands
- | Command | Purpose |
- |---------|---------|
- | `/today` | Guided daily workflow orchestrator |
- | `/daily` | Multi-project standup logging |
- | `/progress` | Cross-project status synthesis |
- | `/preview` | Render docs and reports as styled HTML |
- | `/report` | Executive brief in plain language (CEO/PO view) |
- | `/block` | Structured blocker capture |
- | `/decide` | Decision records with alternatives |
- | `/doc` | Evidence-backed PRDs, user stories, and validation |
- | `/explain` | Explanations at the depth and language you need |
- | `/show-me` | Focused diagrams and visual explanations |
- | `/prioritize` | Direct triage, MoSCoW, RICE, or Kano when useful |
- | `/discover` | Root cause, I-P-O, JTBD, and research guidance |
- | `/journey` | User journey maps with evidence and friction |
- | `/meet` | Meeting extraction into actions/decisions |
- | `/inbox` | Fast capture for later processing |
- | `/ask` | Vault Q&A (QMD-powered when available) |
- | `/health` | Link + vault integrity checks |
- | `/weekly` | Review delivery, learning, outcomes, and next priorities |
- | `/push` | Commit and sync |
- | `/onboard` | Interactive setup + context loading |
- | `/update` | Check for and apply framework updates |
- | `/help` | Command reference and workflow cheat sheet |
- ## Product Thinking
- Use only the structure a decision needs. A small reversible request can receive direct
- triage; competing investments may need a comparison. MoSCoW defines release scope,
- RICE compares credible estimates, and Kano examines customer preferences with research.
- The kit chooses a method by the decision and missing evidence, then explains a non-obvious choice briefly.
- Opportunity maps, product-risk checks, and outcome measures live inside the existing workflows;
- you do not need to learn more commands or complete every framework for each request.
- ```text
- /discover project-a: why do users abandon checkout?
- /journey project-a: a returning customer completes checkout
- /prioritize project-a: compare the checkout requests for the next release
- /doc project-a checkout-flow
- ```
- `_core/judgment.md` defines product reasoning and approval boundaries.
- `_core/knowledge.md` separates evidence, assumptions, interpretations, and reviewed lessons.
- Keep personal judgment and writing examples in `_core/identity.md` or linked `docs/` notes;
- keep product context under `docs/{project}/`. Framework updates preserve those user files
- but replace the shared core guides. Unknown evidence stays unknown; shipped work does
- not automatically count as a measured outcome.
- ## Smarter /ask with QMD (Optional)
- Install [QMD](https://github.com/tobi/qmd) for hybrid search (BM25 + vector + rerank) that dramatically improves `/ask` accuracy. **Requires [bun](https://bun.sh) and technical comfort with CLI tools.** Without QMD, `/ask` still works using vault grep.
- ```bash
- # 1. Install bun (if not installed)
- curl -fsSL https://bun.sh/install | bash
- # 2. Install QMD and set up your vault
- bun install -g github:tobi/qmd
- qmd collection add . --name pm-kit
- # 3. Build the search index
- qmd embed
- ```
- After setup, `/ask` automatically uses QMD when available. No command changes needed.
- Having trouble? See [handbook/QMD_INTEGRATION.md](handbook/QMD_INTEGRATION.md) or [open an issue](https://github.com/kv0906/pm-kit/issues).
- ## Who Uses PM-Kit
- | Role | How They Use It |
- |------|------------------|
- | Product Managers / Product Owners | Run dailies, write PRDs, track blockers, align cross-functional work |
- | Engineering Leads | Capture decisions, drive sprint clarity, maintain technical context |
- | Engineers (Junior -> Senior) | Document context, ship specs, keep decisions traceable |
- | Founders / Solo Builders | Turn scattered thoughts into an execution system |
- | Analysts / Operators | Log research, synthesize findings, build durable knowledge |
- ## Works With
- | Tool | Status | How |
- |------|--------|-----|
- | Claude Code | Native | Reads `CLAUDE.md`, `.claude/` skills, agents, hooks |
- | Cursor | Compatible | `.cursorrules` + `.cursor/rules/` symlinked to source |
- | GitHub Copilot | Compatible | `.github/copilot-instructions.md` symlinked to source |
- | Windsurf | Compatible | `.windsurfrules` symlinked to source |
- | Cline | Compatible | `.clinerules` symlinked to source |
- | OpenAI Codex | Compatible | `AGENTS.md` with project context |
- All compatibility files are symlinks to `CLAUDE.md` (single source of truth). Rules in `.claude/rules/` are shared via symlinks where the tool supports directory-based rules.
- ## Documentation
- | Doc | What It Covers |
- |-----|----------------|
- | [START_HERE.md](START_HERE.md) | 10-step beginner guide |
- | [handbook/HELP_GUIDE.md](handbook/HELP_GUIDE.md) | Full command reference, workflows, and cheat sheet |
- | [handbook/ARCHITECTURE.md](handbook/ARCHITECTURE.md) | How PM-Kit works, project structure, principles |
- | [handbook/QMD_INTEGRATION.md](handbook/QMD_INTEGRATION.md) | QMD setup, troubleshooting, architecture |
- | [handbook/SETUP_GUIDE.md](handbook/SETUP_GUIDE.md) | Installation and first run |
- | [handbook/CUSTOMIZATION.md](handbook/CUSTOMIZATION.md) | Projects, templates, and overrides |
- | [handbook/WORKFLOW_EXAMPLES.md](handbook/WORKFLOW_EXAMPLES.md) | Example operating flows |
- | [handbook/TROUBLESHOOTING.md](handbook/TROUBLESHOOTING.md) | Common issues and fixes |
- | [handbook/maintainer-runbook.md](handbook/maintainer-runbook.md) | Release, changelog governance, and maintainer workflow |
- ## Contributing
- Contributions are welcome.
- - Read `CONTRIBUTING.md`
- - Use the PR template
- - Include a `## Changelog Entry` in each PR
- Every merged PR to `main` is automatically recorded in `CHANGELOG.md`.
- ## License
- MIT
- ## Star History
- [](https://star-history.com/#kv0906/pm-kit&Date)
- Think clearly. Build simply. Let systems carry the weight.
cli/install.sh · Bundled script · 201 lines · 1 finding marked
- #!/usr/bin/env bash
- # PM-Kit CLI Installer
- # Usage: curl -fsSL https://raw.githubusercontent.com/kv0906/pm-kit/main/cli/install.sh | bash
- Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
- Line 3 on GitHub
- set -euo pipefail
- # Colors
- RED='\033[0;31m'
- GREEN='\033[0;32m'
- YELLOW='\033[1;33m'
- CYAN='\033[0;36m'
- BOLD='\033[1m'
- NC='\033[0m'
- info() { echo -e "${CYAN}→${NC} $*"; }
- ok() { echo -e "${GREEN}✓${NC} $*"; }
- warn() { echo -e "${YELLOW}!${NC} $*"; }
- err() { echo -e "${RED}✗${NC} $*" >&2; }
- echo -e "${CYAN}${BOLD}"
- echo "╔═══════════════════════════════════════════════════╗"
- echo "║ PM-Kit CLI Installer ║"
- echo "╚═══════════════════════════════════════════════════╝"
- echo -e "${NC}"
- # --- Prerequisites ---
- for cmd in bash git curl tar; do
- if ! command -v "$cmd" >/dev/null 2>&1; then
- err "Required command not found: $cmd"
- exit 1
- fi
- done
- ok "Prerequisites: bash, git, curl, tar"
- # --- Platform ---
- OS="$(uname -s)"
- case "$OS" in
- Darwin) ok "Platform: macOS" ;;
- Linux) ok "Platform: Linux" ;;
- *) warn "Platform: $OS (untested, may work)" ;;
- esac
- # --- CLI home ---
- CLI_HOME="${PM_KIT_HOME:-$HOME/.pm-kit}"
- mkdir -p "$CLI_HOME/bin" "$CLI_HOME/lib"
- info "Installing to: $CLI_HOME"
- # --- Download latest release ---
- REPO_SLUG="kv0906/pm-kit"
- API_URL="https://api.github.com/repos/${REPO_SLUG}/releases/latest"
- info "Fetching latest release..."
- API_RESPONSE="$(curl -sS -w "\n%{http_code}" "$API_URL" 2>/dev/null)" || {
- err "Failed to reach GitHub API."
- exit 1
- }
- HTTP_CODE="$(echo "$API_RESPONSE" | tail -1)"
- API_BODY="$(echo "$API_RESPONSE" | sed '$d')"
- if [ "$HTTP_CODE" != "200" ]; then
- err "GitHub API returned $HTTP_CODE."
- exit 1
- fi
- REMOTE_TAG="$(echo "$API_BODY" | grep '"tag_name"' | head -1 | sed -E 's/.*"tag_name"[[:space:]]*:[[:space:]]*"([^"]+)".*/\1/')"
- TARBALL_URL="$(echo "$API_BODY" | grep '"tarball_url"' | head -1 | sed -E 's/.*"tarball_url"[[:space:]]*:[[:space:]]*"([^"]+)".*/\1/')"
- REMOTE_VERSION="${REMOTE_TAG#v}"
- if [ -z "$REMOTE_VERSION" ] || [ -z "$TARBALL_URL" ]; then
- err "Could not parse release info."
- exit 1
- fi
- ok "Latest version: v${REMOTE_VERSION}"
- # --- Download and extract ---
- TMPDIR_INSTALL="$(mktemp -d)"
- TARBALL="$TMPDIR_INSTALL/release.tar.gz"
- info "Downloading..."
- curl -sS -L -o "$TARBALL" "$TARBALL_URL" || {
- err "Download failed."
- rm -rf "$TMPDIR_INSTALL"
- exit 1
- }
- tar -xzf "$TARBALL" -C "$TMPDIR_INSTALL" || {
- err "Extraction failed."
- rm -rf "$TMPDIR_INSTALL"
- exit 1
- }
- EXTRACT_DIR="$(find "$TMPDIR_INSTALL" -mindepth 1 -maxdepth 1 -type d | head -1)"
- if [ -z "$EXTRACT_DIR" ]; then
- err "Could not find extracted directory."
- rm -rf "$TMPDIR_INSTALL"
- exit 1
- fi
- # --- Install CLI files ---
- CLI_SRC="$EXTRACT_DIR/cli"
- if [ ! -d "$CLI_SRC" ]; then
- err "Release does not contain cli/ directory."
- err "This release may predate the CLI. Check for a newer release."
- rm -rf "$TMPDIR_INSTALL"
- exit 1
- fi
- info "Installing CLI..."
- cp "$CLI_SRC/bin/pm-kit" "$CLI_HOME/bin/pm-kit"
- chmod +x "$CLI_HOME/bin/pm-kit"
- # Copy lib files
- rm -rf "$CLI_HOME/lib"
- cp -R "$CLI_SRC/lib" "$CLI_HOME/lib"
- # Copy install.sh for reference
- cp "$CLI_SRC/install.sh" "$CLI_HOME/install.sh" 2>/dev/null || true
- # Write VERSION
- echo "$REMOTE_VERSION" > "$CLI_HOME/VERSION"
- # Initialize update check timer
- date +%s > "$CLI_HOME/.last-update-check"
- ok "CLI installed to $CLI_HOME"
- # --- Cleanup ---
- rm -rf "$TMPDIR_INSTALL"
- # --- Add to PATH ---
- BIN_DIR="$CLI_HOME/bin"
- PATH_LINE="export PATH=\"$BIN_DIR:\$PATH\""
- add_to_path() {
- local rc_file="$1"
- if [ -f "$rc_file" ]; then
- if grep -q "$BIN_DIR" "$rc_file" 2>/dev/null; then
- return 0 # Already present
- fi
- fi
- echo "" >> "$rc_file"
- echo "# PM-Kit CLI" >> "$rc_file"
- echo "$PATH_LINE" >> "$rc_file"
- return 1 # Added
- }
- SHELL_NAME="$(basename "$SHELL")"
- ADDED_TO=""
- case "$SHELL_NAME" in
- zsh)
- add_to_path "$HOME/.zshrc" || ADDED_TO="$HOME/.zshrc"
- ;;
- bash)
- if [ -f "$HOME/.bash_profile" ]; then
- add_to_path "$HOME/.bash_profile" || ADDED_TO="$HOME/.bash_profile"
- else
- add_to_path "$HOME/.bashrc" || ADDED_TO="$HOME/.bashrc"
- fi
- ;;
- *)
- add_to_path "$HOME/.profile" || ADDED_TO="$HOME/.profile"
- ;;
- esac
- # --- Success ---
- echo ""
- echo -e "${GREEN}━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━${NC}"
- echo -e "${GREEN} PM-Kit CLI installed! (v${REMOTE_VERSION})${NC}"
- echo -e "${GREEN}━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━${NC}"
- echo ""
- if [ -n "$ADDED_TO" ]; then
- info "Added to PATH in $ADDED_TO"
- echo ""
- echo "To use immediately, run:"
- echo " source $ADDED_TO"
- echo ""
- fi
- echo "Get started:"
- echo " pm-kit init # Create a new vault"
- echo " pm-kit help # See all commands"
- echo ""
- echo "Or from an existing vault:"
- echo " cd /path/to/vault"
- echo " pm-kit migrate # Convert to CLI-managed"
- echo " pm-kit doctor # Check vault health"
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.