Inbox Process
# User-invoked prompt · inbox-process (v1.8.1)
> Walks `meta/queue/to-process/` and triages each item into wiki / archive
> / reject / defer with user confirmation. ROUTER reads this when the user
> wants to process inbox drops.
## Trigger keywords
- `处理 inbox` / `扫 inbox` / `inbox 走一遍`
- `process inbox` / `walk inbox` / `triage inbox`
- `/inbox-process` (slash command escape hatch)
## Pre-flight
1. Verify cwd is a second-brain repo (`meta/` exists). If not: refuse and
tell user "/inbox-process must run inside a second-brain vault, not the
Life OS dev repo".
2. Verify `meta/queue/to-process/` exists. If missing: create it, write
`meta/queue/README.md` (see template at end of this prompt), tell user
"Inbox initialized. Drop `.md` files into `meta/queue/to-process/` and
re-run /inbox-process when ready", and exit.
3. Read `wiki/SCHEMA.md` to confirm frontmatter contract for any wiki write
later in this flow.
4. Read `meta/queue/manifest.md` if it exists (create one with empty
`seen: []` / `last_run: null` YAML frontmatter if not). The manifest tracks
which items were processed in prior runs so we know which are *new* this run.
5. List wiki domains (`ls wiki/` excluding `INDEX.md`, `SCHEMA.md`,
`log.md`, `OBSIDIAN-SETUP.md`, `.templates/`). Cache this list — every
`accept` proposal must place the new entry under one of these existing
domains (or explicitly create a new one with user approval).
## Step 1 · Scan + deltawhen to use it
Community prompt sourced from the open-source GitHub repo jasonhnd/life_OS (NOASSERTION). A "Inbox Process" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
roleplaycommunitygeneral
source
jasonhnd/life_OS · NOASSERTION