القائمة
Check for and apply PM-Kit framework updates from GitHub releases. Reads local VERSION, queries latest release, shows changelog, and runs update script.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
PM-Kit command reference and workflow guide. Use for "/help", "what commands are available", "how do I use PM-Kit", "cheat sheet", "show me workflows", or "/help preview" for topic-specific help.
Render vault notes as styled HTML and open in browser. Turn markdown docs, decisions, progress reports into readable previews. Use for "/preview docs/project-a/checkout-flow.md", "/preview progress all", "/preview decide auth-approach", or when user wants to see a doc before sharing.
Executive briefing in plain language — report to me like I'm the CEO or product owner. Business impact and user impact only, no jargon. Use for "/report", "/report project-a", "report to me", "brief me", "what should I know", "executive summary", or when user wants a non-technical status update focused on outcomes not implementation.
Core vault file operations — read/write notes, manage wiki-links, process templates with Handlebars syntax, enforce naming conventions. Auto-invoked for all file operations.
Flag a blocker with severity, owner, and due date. Checks for duplicates before creating. Use for "/block project: description --severity high --due friday".
Log standup update with keyword detection. Multi-project daily notes with auto-blocker/decision detection. Use for "/daily project: shipped X, wip Y, blocked on Z".
| name | update |
| description | Check for and apply PM-Kit framework updates from GitHub releases. Reads local VERSION, queries latest release, shows changelog, and runs update script. |
| allowed-tools | Bash, Read, Glob |
| user-invocable | true |
Check for new PM-Kit releases and safely apply framework updates without touching your notes or config.
/update # Check + apply if available
/update --check # Check only, no download
/update --dry-run # Preview what would change without applying
Read the local VERSION file to determine the installed version.
cat VERSION
If VERSION doesn't exist, tell the user to run ./scripts/setup.sh first.
Query the GitHub API for the latest release:
# Detect repo from git remote, fallback to kv0906/pm-kit
REPO_SLUG="kv0906/pm-kit"
REMOTE_URL="$(git remote get-url origin 2>/dev/null || true)"
if [ -n "$REMOTE_URL" ]; then
REPO_SLUG="$(echo "$REMOTE_URL" | sed -E 's#.*[:/]([^/]+/[^/.]+)(\.git)?$#\1#')"
fi
curl -sS "https://api.github.com/repos/${REPO_SLUG}/releases/latest"
Run the update script, passing through any flags the user provided:
# If user ran /update --check:
./scripts/update.sh --check
# If user ran /update --dry-run:
./scripts/update.sh --dry-run
# If user ran /update (no flags):
./scripts/update.sh
The script will:
_archive/_updates/{date}/_core/config.yaml, .gitignore) — shows diff insteadVERSION fileAfter the script completes, summarize:
/push to commit changes| Category | Examples | Action |
|---|---|---|
| Framework | CLAUDE.md, _templates/*, .claude/**, scripts/*, handbook/* | Overwrite (backed up first) |
| Hybrid | _core/config.yaml, .gitignore | Diff shown, user merges |
| User content | 00-inbox/, daily/, decisions/, blockers/, meetings/ | Never touched |