メニュー
Deep review — the full weekly review. Process all inboxes to zero, audit projects and areas, get creative. ~30 min. Use when: 'deep review', 'weekly review', 'full review'.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/emcodeio/weave --skill deep-reviewコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Design and create a new template for the vault template library. Creates the template file, optional .base file, optional category note, and updates types.json and Note Schemas. Use when the user says 'new template', 'design a template', 'add a template for', or 'I need a template type for'.
Create a new vault note from a template. Lists available templates, gathers required properties, creates the note with full frontmatter and sections, and handles proactive linking. Use when the user says 'new note', 'create a note', 'new transcript', 'new research note', 'new person note', 'new book note', or names any template type.
Triage and integrate a workbench cluster of related working documents — shape detection (audience-targeted / conceptual exploration / standalone reports / cluster nav), iteration-pair reconciliation, optional composite drafting, per-shape fate proposals. Use when the user says to integrate a cluster, graduate working documents, close out a workbench cluster, or process a sibling cluster from a concept forge.
SKILL.md を表示中
SOC 職業分類に基づく
| name | deep-review |
| description | Deep review — the full weekly review. Process all inboxes to zero, audit projects and areas, get creative. ~30 min. Use when: 'deep review', 'weekly review', 'full review'. |
| disable-model-invocation | true |
You are running the user's deep review — the full weekly review. This has three phases. Take each phase conversationally — present findings and options, don't rush. The user drives decisions.
This is the ONLY session that processes inboxes to zero.
Process ALL inboxes to zero.
Run /process-inbox — unified scan-classify-confirm-execute workflow for both Drafts inbox and Obsidian Inbox/. Claude scans all items, auto-classifies, groups by action type, presents a numbered summary, user confirms/overrides, then Claude executes in batch. See that skill for the full three-pass workflow.
Scan unread emails using mcp__mail__get_emails (unread, limit 25). Group by actionability:
mcp__apple-mail__create-draft[[Action Pool]]obsidian search query="path:Daily/" vault="{{VAULT_NAME}}" limit=7
Check this week's daily notes for uncaptured items, friction patterns, energy/mood trends.
Ask: "Anything in your physical space that needs capturing?"
Search for all notes with categories: ["[[Projects]]"] and status: active. For each project:
status: someday?Read [[Action Pool]]. Friction detection on standalone actions — items sitting across multiple reviews without progress.
Read this week's daily notes (from Phase 1's daily note scan, or re-read via obsidian search query="path:Daily/" vault="{{VAULT_NAME}}" limit=7). For each day, compare ## Today's Options against ## Done Today:
energy and mood frontmatter with completion patterns. Do certain action types only get done on high-energy days?Surface findings conversationally: "I noticed X appeared three times this week but never got done — is something blocking it, or has the purpose shifted?"
Read area notes in Notes/. Check each area for neglected responsibilities. Surface leisure collection notes gently as options.
Weekly scan of shadow pattern activity. Read this week's daily note ## Observations sections and gather any pattern-related notes. Present a brief summary:
If contradictions were detected, append them to the user's defense pattern document ### Contradictions section. If a new undocumented pattern emerged, flag it: "This pattern isn't documented yet — worth adding?"
Read past week and upcoming week from Apple Calendar using mcp__apple-events__calendar_events. Note:
Read full [[Day-Specific Routines]]. Ask: "Are these still working? Anything to add, remove, or adjust?"
Surface today's items from [[Day-Specific Routines]] (e.g., "Balance finances" on Friday).
Run vault health checks:
obsidian orphans vault="{{VAULT_NAME}}"
obsidian deadends vault="{{VAULT_NAME}}"
obsidian unresolved vault="{{VAULT_NAME}}"
Optionally dispatch the vault-organizer agent for structural health and the contradictions-resolver agent for semantic consistency.
Review orphans for any that should be connected to existing areas or categories.
Search for all notes in Workbench/ (obsidian search query="path:Workbench/" vault="{{VAULT_NAME}}"):
status: ready): Present list, offer /integrate-workbench for eachstatus: drafting): "These workbench items haven't been touched in 30+ days: [list]. Still active work, ready to integrate, or safe to delete?"status: paused): Mention count only — intentionally on holdThis is a review checkpoint — the user decides what to do with each item.
Read [[Someday Pool]] and any projects with status: someday. Use mcp__qmd__query to find connections between someday items and active projects — a vec search may surface relevant context. Also check leisure collection notes.
Help the user pick three desired outcomes for the coming week — what would make the week feel successful?
Ask about this week's accomplishments. Acknowledge progress and completed projects.
Ask: "Are your current project and area categories working well? Anything that should be merged, split, or reframed?" Use mcp__qmd__query to check for conceptual overlaps.
Summarize:
Commit all vault changes.