$npx -y skills add kv0906/pm-kit --skill inboxQuick capture mode (with content) or batch processing mode (no content). GTD-style routing of inbox items to proper folders. Use "/inbox thought to capture" or "/inbox" to process.
| 1 | # /inbox — Quick Capture & Process |
| 2 | |
| 3 | Dual-mode command for fast capture and later processing. |
| 4 | |
| 5 | ## Context |
| 6 | |
| 7 | Today's date: `!date +%Y-%m-%d` |
| 8 | Inbox contents: `!ls 00-inbox/*.md 2>/dev/null` |
| 9 | |
| 10 | Reference template: @_templates/inbox.md |
| 11 | Config: @_core/config.yaml |
| 12 | Processing logic: @_core/PROCESSING.md |
| 13 | |
| 14 | ## Input |
| 15 | |
| 16 | User input: $ARGUMENTS |
| 17 | |
| 18 | ## Mode Detection |
| 19 | |
| 20 | - **Capture mode**: If $ARGUMENTS has content |
| 21 | - **Process mode**: If $ARGUMENTS is empty |
| 22 | |
| 23 | --- |
| 24 | |
| 25 | ## Capture Mode (with content) |
| 26 | |
| 27 | 1. **Auto-detect** |
| 28 | - Project: Look for project names from config |
| 29 | - Type: daily, decision, blocker, meeting, doc |
| 30 | |
| 31 | 2. **Create Inbox Note** |
| 32 | - Filename: `00-inbox/{date}-{slug}.md` |
| 33 | - Tag with detected project/type |
| 34 | - Status: unprocessed |
| 35 | |
| 36 | 3. **Append to Vault Log** |
| 37 | - Append entry to `01-index/_vault-log.md` (see `.claude/rules/vault-log.md`) |
| 38 | - Action: `inbox-capture` |
| 39 | - Details: what was captured and detected type |
| 40 | |
| 41 | 4. **Output** |
| 42 | ``` |
| 43 | Captured to: 00-inbox/{filename} |
| 44 | Detected: {project} / {type} |
| 45 | Process later with: /inbox |
| 46 | ``` |
| 47 | |
| 48 | --- |
| 49 | |
| 50 | ## Process Mode (no content) |
| 51 | |
| 52 | Use session tasks for batch visibility: |
| 53 | |
| 54 | ``` |
| 55 | TaskCreate: "Scan and classify inbox items" |
| 56 | activeForm: "Scanning inbox..." |
| 57 | |
| 58 | TaskCreate: "Route items to destinations" |
| 59 | activeForm: "Routing inbox items..." |
| 60 | ``` |
| 61 | |
| 62 | 1. **Scan Inbox** |
| 63 | - List all `.md` files in `00-inbox/` |
| 64 | - Read and classify each |
| 65 | |
| 66 | 2. **Present Plan** |
| 67 | ``` |
| 68 | ## Processing Plan |
| 69 | |
| 70 | | # | Content Preview | Type | Project | Action | |
| 71 | |---|-----------------|------|---------|--------| |
| 72 | | 1 | "Shipped login..." | daily | project-a | Update daily | |
| 73 | | 2 | "Blocked on API..." | blocker | project-a | Create blocker | |
| 74 | |
| 75 | Proceed? (y/n/edit) |
| 76 | ``` |
| 77 | |
| 78 | 3. **Route Items** |
| 79 | - For each confirmed item: |
| 80 | - Route to appropriate handler (/daily, /block, /decide, etc.) |
| 81 | - Mark processed inbox files |
| 82 | |
| 83 | 4. **Append to Vault Log** |
| 84 | - Append one `inbox-route` entry per batch to `01-index/_vault-log.md` (see `.claude/rules/vault-log.md`) |
| 85 | - Details: count of items routed and their types |
| 86 | |
| 87 | 5. **Output** |
| 88 | ``` |
| 89 | Processed: {count} items |
| 90 | - Daily updates: {count} |
| 91 | - Blockers: {count} |
| 92 | - Decisions: {count} |
| 93 | ``` |