Menu
Draft or edit a document — PRD, spec, design doc, technical brief. Use for "/doc project title" to create a new doc or edit existing.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | doc |
| description | Draft or edit a document — PRD, spec, design doc, technical brief. Use for "/doc project title" to create a new doc or edit existing. |
| allowed-tools | Read, Write, Edit, Bash, Glob, Grep, TaskCreate, TaskUpdate, TaskList, TaskGet |
| user-invocable | true |
Create or edit documents (specs, PRDs, design docs, etc.).
Today's date: !date +%Y-%m-%d
Existing docs: !ls docs/*/*.md 2>/dev/null | tail -10
Reference template: @_templates/doc.md Config: @_core/config.yaml Processing logic: @_core/PROCESSING.md
User input: $ARGUMENTS
Parse Input
Check Existing
docs/{project}/*.md for similar titles (or docs/general/*.md if no project)Gather Context
Interactive Drafting
Create Doc Note
docs/general/{slug}.mddocs/{project}/{slug}.md## Links sectionUpdate References
Append to Vault Log
01-index/_vault-log.md (see .claude/rules/vault-log.md)docCreated: docs/{project}/{slug}.md
Status: draft
Sections: {filled}/{total}
Supports --docx, --pdf flags. See .claude/rules/export-formats.md for layout specs and workflow. Complete normal processing first, then generate the formatted file.
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".