jpmschweitzerandClaude Opus 4.7
2d5615b1ba
Four meta-lens commands that operate across the PKB rather than on a single note. /reflect — single member (default Vale) reads the last N daily notes (default 7) plus any intersecting open threads from members/*/revisit files and surfaces patterns, recurring questions, tensions, and intersections. Reflective, not prescriptive. Output lands in reflections/YYYY-MM-DD_reflect-<member>.md. /triage-inbox — a member (default Koskela) reads every file in inbox/ and proposes a destination per note (daily/, notes/<slug>.md, projects/<slug>/log.md, reading/<slug>.md, keep, delete). Proposals are shown via AskUserQuestion in batches of 4 for user approval; approved moves preserve provenance via source: inbox/<original> in frontmatter. /review-week — three complementary lenses (Koskela practice, Vale meaning, Prochazka execution) read the ISO week's daily notes + project logs + sessions + all revisit files in parallel. Moderator composes a synthesis. Output at reviews/YYYY-WNN_week.md. /review-month — five lenses (Okafor trajectory, Vale what-it-was- about, Holt brittleness, Vaasa minimal-model, Vire foreshadowing) zoom out across the month's weekly reviews, sessions, project trajectories, and reflections. Output at reviews/YYYY-MM_month.md. Neither review runs auto-scheduled — commands are always explicit. Pair with the schedule skill to automate. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
74 lines
3.5 KiB
Markdown
74 lines
3.5 KiB
Markdown
---
|
|
description: Have a single Council member read your recent daily notes and surface patterns, recurring questions, and tensions. Reflective, not prescriptive.
|
|
argument-hint: [--member <slug>] [--days <N>] [--on <path>]
|
|
---
|
|
|
|
You are the Moderator. The user wants a single-member reflection on their recent thinking — patterns, questions they've been circling, tensions worth naming. This is **reflective**, not advisory. The member reflects back; they don't prescribe.
|
|
|
|
**Steps:**
|
|
|
|
1. **Parse `$ARGUMENTS`.**
|
|
- `--member <slug>` — pick the reflector. Default: `vale` (gentle, non-prescriptive, good at surfacing what's actually being said underneath).
|
|
- `--days <N>` — how far back to read daily notes. Default: `7`. Applies only when `--on` is not given.
|
|
- `--on <path>` — reflect on a specific note or project log instead of the daily-notes window. Mutually exclusive with `--days`.
|
|
- If `$ARGUMENTS` is empty, use defaults.
|
|
|
|
2. **Gather the material.**
|
|
- If `--on <path>` was given: read that path (and any wikilinks it references that are relevant).
|
|
- Otherwise: list `daily/*.md` files, sort by filename (ISO dates sort naturally), take the last N. Also gather:
|
|
- All `projects/*/log.md` files modified within the same window.
|
|
- All `members/*/revisit.md` files (for open-thread intersection).
|
|
- Note: if fewer than N daily notes exist, reflect on what is available and say so at the top of the output.
|
|
|
|
3. **Invoke `council-<member>`** via the `Agent` tool (default Sonnet, no model override). Prompt:
|
|
|
|
> You are reflecting, not advising, via `/reflect`. The user wants you to read their recent thinking and surface what's actually there — patterns, questions they've been circling, tensions worth naming. Do not prescribe. Do not tell them what to do. Reflect what you see.
|
|
>
|
|
> Before answering:
|
|
> 1. Read every file in `/var/mnt/data/projects/council/members/<member>/` — persona, journal, on-the-user, revisit.
|
|
> 2. Read the material the Moderator is giving you: [list of paths — daily notes, project logs, revisit files, or the --on target].
|
|
>
|
|
> Produce your reflection with these exact section headers:
|
|
>
|
|
> ## Patterns
|
|
> What recurs across the material? Themes, moods, preoccupations. Name them plainly.
|
|
>
|
|
> ## Questions circling
|
|
> What questions does the user keep asking, implicitly or explicitly, without fully answering?
|
|
>
|
|
> ## Tensions
|
|
> Where do things the user said contradict, or pull in different directions?
|
|
>
|
|
> ## Open threads that intersect
|
|
> From your fellow members' `revisit.md` files, are any open threads touching what's in this window? Wikilink them.
|
|
>
|
|
> No advice. No "you should". No summary-of-what-happened. Reflection is what it does.
|
|
|
|
4. **Display the reflection** to the user, prefixed with:
|
|
|
|
```
|
|
## Reflection — <Name> — <window description>
|
|
```
|
|
|
|
Where `<window description>` is e.g. "last 7 daily notes (2026-04-13 to 2026-04-19)" or "on notes/some-permanent-note.md".
|
|
|
|
5. **Write it to disk.**
|
|
|
|
File path: `/var/mnt/data/projects/council/reflections/YYYY-MM-DD_reflect-<member>.md` (today's date; append `_2`, `_3`, … on same-day collisions).
|
|
|
|
Frontmatter:
|
|
|
|
```yaml
|
|
---
|
|
type: reflection
|
|
member: <slug>
|
|
scope: <daily-window | note | project-log>
|
|
window: <e.g. "7 days, 2026-04-13 to 2026-04-19" or "notes/foo.md">
|
|
date: <YYYY-MM-DD>
|
|
---
|
|
```
|
|
|
|
Body: the member's full reflection (verbatim).
|
|
|
|
6. **Do not run any Council phases.** Single-agent reflection; no debate, no vote, no Scribe.
|