メニュー
Triage the open questions backlog. Group by topic, flag overdue items, propose resolutions or promotions, offer to move resolved items to .resolved/. Invoked when the user says "triage open questions", "what's blocking me", or "review the open questions list".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Answer a question using the Memex wiki. Read the index, find relevant pages, read them, synthesise a cited answer, optionally file the answer back as a new wiki page for compounding value. Invoked when the user asks a question referring to "the wiki", "my notes", "the docs", or asks a question whose answer likely lives in the wiki.
Ingest a raw source into the Memex wiki. Reads the file, summarises it to a new page under the profile's summary folder, extracts entities/concepts/topics and updates or creates their pages, bumps index.md, appends log.md. Invoked when the user mentions ingesting an article, processing a source, or adding a file under .memex/raw/ to the wiki.
Health-check the Memex wiki. Find orphan pages, contradictions, stale claims, missing cross-references, pages referenced but missing, overdue open questions, and data gaps. Produce a report; offer to auto-fix easy issues. Invoked when the user says "lint the wiki", "audit my docs", "health-check the wiki", or runs /memex:lint.
Structurally refactor wiki pages — split a page into multiple, merge two or more into one, rename a slug across all references. Handles cross-reference updates automatically. Invoked when the user says "split this page", "merge these pages", "rename this slug", or "refactor the wiki".
Interactively build a custom Memex profile tailored to a project's actual folder shape. Surveys the project with Glob/Grep, classifies the project type, asks the user targeted questions about taxonomy and gating, and writes a complete memex.config.json + .memex/ tree + CLAUDE.md + AGENTS.md. Invoked by /memex:init-profile, or when the user says "help me build a profile", "make a memex profile for this project", or "none of the profiles fit".
| name | open-questions-triage |
| description | Triage the open questions backlog. Group by topic, flag overdue items, propose resolutions or promotions, offer to move resolved items to .resolved/. Invoked when the user says "triage open questions", "what's blocking me", or "review the open questions list". |
| triggers | ["triage open questions","what's blocking me","review open questions","resolve open questions"] |
| allowed-tools | Read, Grep, Glob, Write, Edit, Bash |
<ops-root>/.open-questions/*.md (exclude .resolved/)title, slug, status, owner, created, updatedstatus: resolved in its frontmatter is treated as resolved even if it hasn't been moved to .resolved/ (matches docsite behaviour as of 0.1.0a2).Note. The docsite's
/open-questionsview lists the same files. Browser-driven submissions land in this same folder and append a line tolog.md, so a triage pass and a docsite browse are looking at the same data.
Group the list by:
<1 week, 1–4 weeks, 1–3 months, 3+ months## Context paragraphowner: unassigned AND age > 2 weeks → flag as needs-ownerstatus: open AND age > 90 days → flag as overdueTODO/TBD markers inside the question body → surface themPresent the triage as a table. Columns: slug | title | age | owner | flags.
Group by age bucket, newest first within each.
For each overdue or overlong question, propose one of:
## Resolution with date and move to .resolved/.resolved/ with resolution = "no longer applicable"updated: to now)entities/<slug>/README.md or similar, then mark the open question resolved with a link to the new pageCarry out the actions one by one. Each action:
updated:).resolved/ (use git mv if available, else filesystem move)log.md entry with event: open-q-resolved | <slug>Summary: how many questions were reviewed, how many resolved / split / demoted / escalated / promoted. Flag any remaining needs-owner items.