القائمة
Core vault file operations — read/write notes, manage wiki-links, process templates with Handlebars syntax, enforce naming conventions. Auto-invoked for all file operations.
التثبيت باستخدام 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.
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".
Log a decision with context, alternatives considered, and rationale. Use for "/decide project: using websocket over polling" or "/decide project: chose React for frontend".
| name | vault-ops |
| description | Core vault file operations — read/write notes, manage wiki-links, process templates with Handlebars syntax, enforce naming conventions. Auto-invoked for all file operations. |
| allowed-tools | Read, Write, Edit, Glob, Grep |
Core operations for reading, writing, and managing files in a PM-Kit vault.
pm-kit/
├── CLAUDE.md # Vault context (read first)
├── _core/ # config.yaml, MANIFESTO.md, PROCESSING.md
├── _templates/ # Note templates (ALWAYS USE)
├── 00-inbox/ # Unprocessed captures
├── 01-index/ # Project MOCs
├── daily/ # YYYY-MM-DD.md (multi-project)
├── docs/{project}/ # PRDs, specs
├── decisions/{project}/ # Decision records
├── blockers/{project}/ # Active blockers
├── meetings/ # Meeting notes
├── reports/ # Generated reports
│ └── previews/ # HTML previews (/preview, /report --preview)
└── _archive/ # Archived by YYYY-MM/
Strict filename patterns enable glob queries without a database:
| Type | Pattern | Example |
|---|---|---|
| Daily | daily/YYYY-MM-DD.md | daily/2026-01-15.md |
| Doc | docs/{project}/{slug}.md | docs/project-a/checkout-flow.md |
| Decision | decisions/{project}/YYYY-MM-DD-{slug}.md | decisions/project-a/2026-01-15-auth-approach.md |
| Blocker | blockers/{project}/YYYY-MM-DD-{slug}.md | blockers/project-a/2026-01-15-api-rate-limit.md |
| Meeting | meetings/YYYY-MM-DD-{type}-{slug}.md | meetings/2026-01-15-sync-sprint-review.md |
| Inbox | 00-inbox/YYYY-MM-DD-{slug}.md | 00-inbox/2026-01-15-quick-thought.md |
| Index | 01-index/{project}.md | 01-index/project-a.md |
_templates/[[Note Name]] # Simple link
[[Note Name|Display Text]] # Link with alias
[[Note Name#Section]] # Link to heading
[[folder/Note Name]] # Link with path
When processing templates, replace Handlebars syntax:
{{date}} → Today's date (YYYY-MM-DD){{project}} → Project ID{{project_name}} → Project display name{{title}} → Note title{{slug}} → URL-safe slugAll notes require frontmatter:
---
type: [daily|doc|decision|blocker|meeting|inbox|index]
project: {project-id}
status: {per note_types in config.yaml}
date: YYYY-MM-DD
tags: []
---
| From | Links To |
|---|---|
| Daily (blocked item) | blockers/{project}/ |
| Meeting | decisions/{project}/, blockers/{project}/ |
| Decision | docs/{project}/ |
| Doc | decisions, blockers |
Move to _archive/YYYY-MM/ when: