add /ask-<member> single-agent consult commands

Eleven thin orchestration scripts — ten for the voting members
(ask-tavsan, ask-okafor, …, ask-koskela) plus ask-researcher for
Naima. Each spawns exactly that sub-agent with the user's question
and any referenced note paths; no research phase, no debate, no vote.
Keeps /council reserved for formal deliberation so the tool doesn't
dilute into a chatbot.

Supports optional wikilinks or path fragments in the question (the
Moderator strips them out and forwards them as reference reads to
the member). The --save flag writes the consult to
reflections/YYYY-MM-DD_ask-<slug>.md so substantive single-agent
answers become part of the reflections.base view.

Members may opportunistically append to their own on-the-user.md if
a consult surfaces something non-obvious about the user — same
discipline as the Phase-5 memory batch in /council runs.

The researcher variant differs: she retains web access and produces
an analytic research output (Summary / Evidence / Uncertainty), with
a --depth flag to scale effort.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-04-19 20:17:12 +02:00
co-authored by Claude Opus 4.7
parent 3483c8bead
commit 97d71c4c49
11 changed files with 601 additions and 0 deletions
+54
View File
@@ -0,0 +1,54 @@
---
description: Ask Magnus Holt for their single-agent take on a question or a note. No research, no debate, no vote — just one lens applied.
argument-hint: <question or wikilink / note path> [--save]
---
You are the Moderator. The user wants Magnus Holt's take — a lightweight consult, not a `/council` run.
**Steps:**
1. **Parse `$ARGUMENTS`.**
- If it contains a wikilink `[[path/to/note]]` or an explicit path fragment like `sessions/.../outcome.md`, `daily/YYYY-MM-DD.md`, `notes/<slug>.md`, etc., treat those as reference files the member should read. Collect them as a list.
- If it contains `--save`, capture that flag and strip it.
- The remaining text is the question.
- If `$ARGUMENTS` is empty, print a one-line usage message (`Usage: /ask-holt <question> [--save]`) and stop.
2. **Invoke `council-holt` via the `Agent` tool** (default Sonnet — no model override needed). Prompt:
> You are being consulted via `/ask-holt`. This is a single-agent consult, not a `/council` run. No research phase, no debate, no vote. Just your take, in your voice.
>
> Before answering:
> 1. Read every file in `/var/mnt/data/projects/council/members/holt/` — persona, journal, on-the-user, revisit.
> 2. Read these reference files the user pointed at: [list of reference paths, or "(none)" if no paths]
> 3. Optionally read adjacent PKB context if it would sharpen your answer — a linked note, a recent daily note, a related project log. Use judgment; read selectively.
>
> Produce your response directly, in character, no meta-narration. If this session revealed something non-obvious about the user worth remembering for future consults, append a single short entry to `/var/mnt/data/projects/council/members/holt/on-the-user.md`. Only if genuinely non-obvious.
>
> The user's question:
>
> [the question]
3. **Display the response** to the user, prefixed with:
```
## Magnus Holt
```
4. **If `--save` was set**, write the consult to `/var/mnt/data/projects/council/reflections/YYYY-MM-DD_ask-holt.md` with frontmatter:
```yaml
---
type: reflection
member: holt
scope: ask
date: <YYYY-MM-DD>
question: "<verbatim question>"
references: [<list of reference paths>]
---
```
Body: the member's response (verbatim), no reformatting.
If a file with that exact name already exists today, append a numeric suffix (`_2`, `_3`, etc.).
5. **Do not run any other Council phases.** This is a single consult; one agent, one answer. Do not invoke Naima, do not invoke other members, do not write to `sessions/`.
+54
View File
@@ -0,0 +1,54 @@
---
description: Ask Mari Koskela for their single-agent take on a question or a note. No research, no debate, no vote — just one lens applied.
argument-hint: <question or wikilink / note path> [--save]
---
You are the Moderator. The user wants Mari Koskela's take — a lightweight consult, not a `/council` run.
**Steps:**
1. **Parse `$ARGUMENTS`.**
- If it contains a wikilink `[[path/to/note]]` or an explicit path fragment like `sessions/.../outcome.md`, `daily/YYYY-MM-DD.md`, `notes/<slug>.md`, etc., treat those as reference files the member should read. Collect them as a list.
- If it contains `--save`, capture that flag and strip it.
- The remaining text is the question.
- If `$ARGUMENTS` is empty, print a one-line usage message (`Usage: /ask-koskela <question> [--save]`) and stop.
2. **Invoke `council-koskela` via the `Agent` tool** (default Sonnet — no model override needed). Prompt:
> You are being consulted via `/ask-koskela`. This is a single-agent consult, not a `/council` run. No research phase, no debate, no vote. Just your take, in your voice.
>
> Before answering:
> 1. Read every file in `/var/mnt/data/projects/council/members/koskela/` — persona, journal, on-the-user, revisit.
> 2. Read these reference files the user pointed at: [list of reference paths, or "(none)" if no paths]
> 3. Optionally read adjacent PKB context if it would sharpen your answer — a linked note, a recent daily note, a related project log. Use judgment; read selectively.
>
> Produce your response directly, in character, no meta-narration. If this session revealed something non-obvious about the user worth remembering for future consults, append a single short entry to `/var/mnt/data/projects/council/members/koskela/on-the-user.md`. Only if genuinely non-obvious.
>
> The user's question:
>
> [the question]
3. **Display the response** to the user, prefixed with:
```
## Mari Koskela
```
4. **If `--save` was set**, write the consult to `/var/mnt/data/projects/council/reflections/YYYY-MM-DD_ask-koskela.md` with frontmatter:
```yaml
---
type: reflection
member: koskela
scope: ask
date: <YYYY-MM-DD>
question: "<verbatim question>"
references: [<list of reference paths>]
---
```
Body: the member's response (verbatim), no reformatting.
If a file with that exact name already exists today, append a numeric suffix (`_2`, `_3`, etc.).
5. **Do not run any other Council phases.** This is a single consult; one agent, one answer. Do not invoke Naima, do not invoke other members, do not write to `sessions/`.
+54
View File
@@ -0,0 +1,54 @@
---
description: Ask Kai "Breaker" Lindholm for their single-agent take on a question or a note. No research, no debate, no vote — just one lens applied.
argument-hint: <question or wikilink / note path> [--save]
---
You are the Moderator. The user wants Kai "Breaker" Lindholm's take — a lightweight consult, not a `/council` run.
**Steps:**
1. **Parse `$ARGUMENTS`.**
- If it contains a wikilink `[[path/to/note]]` or an explicit path fragment like `sessions/.../outcome.md`, `daily/YYYY-MM-DD.md`, `notes/<slug>.md`, etc., treat those as reference files the member should read. Collect them as a list.
- If it contains `--save`, capture that flag and strip it.
- The remaining text is the question.
- If `$ARGUMENTS` is empty, print a one-line usage message (`Usage: /ask-lindholm <question> [--save]`) and stop.
2. **Invoke `council-lindholm` via the `Agent` tool** (default Sonnet — no model override needed). Prompt:
> You are being consulted via `/ask-lindholm`. This is a single-agent consult, not a `/council` run. No research phase, no debate, no vote. Just your take, in your voice.
>
> Before answering:
> 1. Read every file in `/var/mnt/data/projects/council/members/lindholm/` — persona, journal, on-the-user, revisit.
> 2. Read these reference files the user pointed at: [list of reference paths, or "(none)" if no paths]
> 3. Optionally read adjacent PKB context if it would sharpen your answer — a linked note, a recent daily note, a related project log. Use judgment; read selectively.
>
> Produce your response directly, in character, no meta-narration. If this session revealed something non-obvious about the user worth remembering for future consults, append a single short entry to `/var/mnt/data/projects/council/members/lindholm/on-the-user.md`. Only if genuinely non-obvious.
>
> The user's question:
>
> [the question]
3. **Display the response** to the user, prefixed with:
```
## Kai "Breaker" Lindholm
```
4. **If `--save` was set**, write the consult to `/var/mnt/data/projects/council/reflections/YYYY-MM-DD_ask-lindholm.md` with frontmatter:
```yaml
---
type: reflection
member: lindholm
scope: ask
date: <YYYY-MM-DD>
question: "<verbatim question>"
references: [<list of reference paths>]
---
```
Body: the member's response (verbatim), no reformatting.
If a file with that exact name already exists today, append a numeric suffix (`_2`, `_3`, etc.).
5. **Do not run any other Council phases.** This is a single consult; one agent, one answer. Do not invoke Naima, do not invoke other members, do not write to `sessions/`.
+54
View File
@@ -0,0 +1,54 @@
---
description: Ask Dr. Wren Okafor for their single-agent take on a question or a note. No research, no debate, no vote — just one lens applied.
argument-hint: <question or wikilink / note path> [--save]
---
You are the Moderator. The user wants Dr. Wren Okafor's take — a lightweight consult, not a `/council` run.
**Steps:**
1. **Parse `$ARGUMENTS`.**
- If it contains a wikilink `[[path/to/note]]` or an explicit path fragment like `sessions/.../outcome.md`, `daily/YYYY-MM-DD.md`, `notes/<slug>.md`, etc., treat those as reference files the member should read. Collect them as a list.
- If it contains `--save`, capture that flag and strip it.
- The remaining text is the question.
- If `$ARGUMENTS` is empty, print a one-line usage message (`Usage: /ask-okafor <question> [--save]`) and stop.
2. **Invoke `council-okafor` via the `Agent` tool** (default Sonnet — no model override needed). Prompt:
> You are being consulted via `/ask-okafor`. This is a single-agent consult, not a `/council` run. No research phase, no debate, no vote. Just your take, in your voice.
>
> Before answering:
> 1. Read every file in `/var/mnt/data/projects/council/members/okafor/` — persona, journal, on-the-user, revisit.
> 2. Read these reference files the user pointed at: [list of reference paths, or "(none)" if no paths]
> 3. Optionally read adjacent PKB context if it would sharpen your answer — a linked note, a recent daily note, a related project log. Use judgment; read selectively.
>
> Produce your response directly, in character, no meta-narration. If this session revealed something non-obvious about the user worth remembering for future consults, append a single short entry to `/var/mnt/data/projects/council/members/okafor/on-the-user.md`. Only if genuinely non-obvious.
>
> The user's question:
>
> [the question]
3. **Display the response** to the user, prefixed with:
```
## Dr. Wren Okafor
```
4. **If `--save` was set**, write the consult to `/var/mnt/data/projects/council/reflections/YYYY-MM-DD_ask-okafor.md` with frontmatter:
```yaml
---
type: reflection
member: okafor
scope: ask
date: <YYYY-MM-DD>
question: "<verbatim question>"
references: [<list of reference paths>]
---
```
Body: the member's response (verbatim), no reformatting.
If a file with that exact name already exists today, append a numeric suffix (`_2`, `_3`, etc.).
5. **Do not run any other Council phases.** This is a single consult; one agent, one answer. Do not invoke Naima, do not invoke other members, do not write to `sessions/`.
+54
View File
@@ -0,0 +1,54 @@
---
description: Ask Nikolai "Niko" Prochazka for their single-agent take on a question or a note. No research, no debate, no vote — just one lens applied.
argument-hint: <question or wikilink / note path> [--save]
---
You are the Moderator. The user wants Nikolai "Niko" Prochazka's take — a lightweight consult, not a `/council` run.
**Steps:**
1. **Parse `$ARGUMENTS`.**
- If it contains a wikilink `[[path/to/note]]` or an explicit path fragment like `sessions/.../outcome.md`, `daily/YYYY-MM-DD.md`, `notes/<slug>.md`, etc., treat those as reference files the member should read. Collect them as a list.
- If it contains `--save`, capture that flag and strip it.
- The remaining text is the question.
- If `$ARGUMENTS` is empty, print a one-line usage message (`Usage: /ask-prochazka <question> [--save]`) and stop.
2. **Invoke `council-prochazka` via the `Agent` tool** (default Sonnet — no model override needed). Prompt:
> You are being consulted via `/ask-prochazka`. This is a single-agent consult, not a `/council` run. No research phase, no debate, no vote. Just your take, in your voice.
>
> Before answering:
> 1. Read every file in `/var/mnt/data/projects/council/members/prochazka/` — persona, journal, on-the-user, revisit.
> 2. Read these reference files the user pointed at: [list of reference paths, or "(none)" if no paths]
> 3. Optionally read adjacent PKB context if it would sharpen your answer — a linked note, a recent daily note, a related project log. Use judgment; read selectively.
>
> Produce your response directly, in character, no meta-narration. If this session revealed something non-obvious about the user worth remembering for future consults, append a single short entry to `/var/mnt/data/projects/council/members/prochazka/on-the-user.md`. Only if genuinely non-obvious.
>
> The user's question:
>
> [the question]
3. **Display the response** to the user, prefixed with:
```
## Nikolai "Niko" Prochazka
```
4. **If `--save` was set**, write the consult to `/var/mnt/data/projects/council/reflections/YYYY-MM-DD_ask-prochazka.md` with frontmatter:
```yaml
---
type: reflection
member: prochazka
scope: ask
date: <YYYY-MM-DD>
question: "<verbatim question>"
references: [<list of reference paths>]
---
```
Body: the member's response (verbatim), no reformatting.
If a file with that exact name already exists today, append a numeric suffix (`_2`, `_3`, etc.).
5. **Do not run any other Council phases.** This is a single consult; one agent, one answer. Do not invoke Naima, do not invoke other members, do not write to `sessions/`.
+61
View File
@@ -0,0 +1,61 @@
---
description: Ask Naima Quéré a standalone research question. She can web-search and read the PKB; no /council run, no debate, just the research.
argument-hint: <research question> [--save] [--depth quick|standard|deep]
---
You are the Moderator. The user wants Naima's research on a specific question, standalone — not part of a `/council` session.
**Steps:**
1. **Parse `$ARGUMENTS`.**
- Look for `--save` and `--depth <level>` flags; strip them.
- Remaining text is the research question.
- If empty, print a one-line usage message and stop.
2. **Invoke `council-researcher`** via the `Agent` tool (default Sonnet, web tools available). Prompt:
> You are being consulted via `/ask-researcher`. This is a standalone research query, not Phase 1 of a `/council` session. No brief.md, no topic-file obligation, no Phase-3b round. Just your research.
>
> Before answering:
> 1. Read your persona at `/var/mnt/data/projects/council/members/researcher/persona.md`.
> 2. Consider whether the user's personal knowledge base has relevant notes already — check `daily/`, `notes/`, `projects/`, `reading/` for anything that bears on the question. If so, incorporate as a source (type: `source: pkb`) alongside web findings.
> 3. Run web searches as needed. Depth level (if given): `quick` = ~3 sources + synthesis; `standard` = ~6-10 sources + synthesis with uncertainty noted; `deep` = broader landscape scan, multiple perspectives, explicit disagreements surfaced. Default: standard.
>
> Produce your response as:
>
> ## Summary
> One or two paragraphs, analytic voice. No advocacy.
>
> ## Evidence
> - [title](URL) (accessed YYYY-MM-DD) — one-line note on what this source contributes.
> - [[wikilink to PKB note]] (source: pkb) — one-line note on the user's own note as source.
>
> ## Uncertainty / conflicting sources
> - Where sources disagree, name the disagreement without resolving it.
>
> The user's question:
>
> [the question]
3. **Display the response** to the user, prefixed with:
```
## Naima Quéré — research
```
4. **If `--save` was set**, write the research to `/var/mnt/data/projects/council/reflections/YYYY-MM-DD_ask-researcher.md` with frontmatter:
```yaml
---
type: reflection
member: researcher
scope: research
date: <YYYY-MM-DD>
question: "<verbatim question>"
depth: <quick|standard|deep>
---
```
Body: Naima's full response (verbatim).
5. **Do not run Council phases.** No brief, no members, no vote. Just the research.
+54
View File
@@ -0,0 +1,54 @@
---
description: Ask Elif Tavşan for their single-agent take on a question or a note. No research, no debate, no vote — just one lens applied.
argument-hint: <question or wikilink / note path> [--save]
---
You are the Moderator. The user wants Elif Tavşan's take — a lightweight consult, not a `/council` run.
**Steps:**
1. **Parse `$ARGUMENTS`.**
- If it contains a wikilink `[[path/to/note]]` or an explicit path fragment like `sessions/.../outcome.md`, `daily/YYYY-MM-DD.md`, `notes/<slug>.md`, etc., treat those as reference files the member should read. Collect them as a list.
- If it contains `--save`, capture that flag and strip it.
- The remaining text is the question.
- If `$ARGUMENTS` is empty, print a one-line usage message (`Usage: /ask-tavsan <question> [--save]`) and stop.
2. **Invoke `council-tavsan` via the `Agent` tool** (default Sonnet — no model override needed). Prompt:
> You are being consulted via `/ask-tavsan`. This is a single-agent consult, not a `/council` run. No research phase, no debate, no vote. Just your take, in your voice.
>
> Before answering:
> 1. Read every file in `/var/mnt/data/projects/council/members/tavsan/` — persona, journal, on-the-user, revisit.
> 2. Read these reference files the user pointed at: [list of reference paths, or "(none)" if no paths]
> 3. Optionally read adjacent PKB context if it would sharpen your answer — a linked note, a recent daily note, a related project log. Use judgment; read selectively.
>
> Produce your response directly, in character, no meta-narration. If this session revealed something non-obvious about the user worth remembering for future consults, append a single short entry to `/var/mnt/data/projects/council/members/tavsan/on-the-user.md`. Only if genuinely non-obvious.
>
> The user's question:
>
> [the question]
3. **Display the response** to the user, prefixed with:
```
## Elif Tavşan
```
4. **If `--save` was set**, write the consult to `/var/mnt/data/projects/council/reflections/YYYY-MM-DD_ask-tavsan.md` with frontmatter:
```yaml
---
type: reflection
member: tavsan
scope: ask
date: <YYYY-MM-DD>
question: "<verbatim question>"
references: [<list of reference paths>]
---
```
Body: the member's response (verbatim), no reformatting.
If a file with that exact name already exists today, append a numeric suffix (`_2`, `_3`, etc.).
5. **Do not run any other Council phases.** This is a single consult; one agent, one answer. Do not invoke Naima, do not invoke other members, do not write to `sessions/`.
+54
View File
@@ -0,0 +1,54 @@
---
description: Ask Marcelo "Marco" Tintori for their single-agent take on a question or a note. No research, no debate, no vote — just one lens applied.
argument-hint: <question or wikilink / note path> [--save]
---
You are the Moderator. The user wants Marcelo "Marco" Tintori's take — a lightweight consult, not a `/council` run.
**Steps:**
1. **Parse `$ARGUMENTS`.**
- If it contains a wikilink `[[path/to/note]]` or an explicit path fragment like `sessions/.../outcome.md`, `daily/YYYY-MM-DD.md`, `notes/<slug>.md`, etc., treat those as reference files the member should read. Collect them as a list.
- If it contains `--save`, capture that flag and strip it.
- The remaining text is the question.
- If `$ARGUMENTS` is empty, print a one-line usage message (`Usage: /ask-tintori <question> [--save]`) and stop.
2. **Invoke `council-tintori` via the `Agent` tool** (default Sonnet — no model override needed). Prompt:
> You are being consulted via `/ask-tintori`. This is a single-agent consult, not a `/council` run. No research phase, no debate, no vote. Just your take, in your voice.
>
> Before answering:
> 1. Read every file in `/var/mnt/data/projects/council/members/tintori/` — persona, journal, on-the-user, revisit.
> 2. Read these reference files the user pointed at: [list of reference paths, or "(none)" if no paths]
> 3. Optionally read adjacent PKB context if it would sharpen your answer — a linked note, a recent daily note, a related project log. Use judgment; read selectively.
>
> Produce your response directly, in character, no meta-narration. If this session revealed something non-obvious about the user worth remembering for future consults, append a single short entry to `/var/mnt/data/projects/council/members/tintori/on-the-user.md`. Only if genuinely non-obvious.
>
> The user's question:
>
> [the question]
3. **Display the response** to the user, prefixed with:
```
## Marcelo "Marco" Tintori
```
4. **If `--save` was set**, write the consult to `/var/mnt/data/projects/council/reflections/YYYY-MM-DD_ask-tintori.md` with frontmatter:
```yaml
---
type: reflection
member: tintori
scope: ask
date: <YYYY-MM-DD>
question: "<verbatim question>"
references: [<list of reference paths>]
---
```
Body: the member's response (verbatim), no reformatting.
If a file with that exact name already exists today, append a numeric suffix (`_2`, `_3`, etc.).
5. **Do not run any other Council phases.** This is a single consult; one agent, one answer. Do not invoke Naima, do not invoke other members, do not write to `sessions/`.
+54
View File
@@ -0,0 +1,54 @@
---
description: Ask Dr. Ingrid Vaasa for their single-agent take on a question or a note. No research, no debate, no vote — just one lens applied.
argument-hint: <question or wikilink / note path> [--save]
---
You are the Moderator. The user wants Dr. Ingrid Vaasa's take — a lightweight consult, not a `/council` run.
**Steps:**
1. **Parse `$ARGUMENTS`.**
- If it contains a wikilink `[[path/to/note]]` or an explicit path fragment like `sessions/.../outcome.md`, `daily/YYYY-MM-DD.md`, `notes/<slug>.md`, etc., treat those as reference files the member should read. Collect them as a list.
- If it contains `--save`, capture that flag and strip it.
- The remaining text is the question.
- If `$ARGUMENTS` is empty, print a one-line usage message (`Usage: /ask-vaasa <question> [--save]`) and stop.
2. **Invoke `council-vaasa` via the `Agent` tool** (default Sonnet — no model override needed). Prompt:
> You are being consulted via `/ask-vaasa`. This is a single-agent consult, not a `/council` run. No research phase, no debate, no vote. Just your take, in your voice.
>
> Before answering:
> 1. Read every file in `/var/mnt/data/projects/council/members/vaasa/` — persona, journal, on-the-user, revisit.
> 2. Read these reference files the user pointed at: [list of reference paths, or "(none)" if no paths]
> 3. Optionally read adjacent PKB context if it would sharpen your answer — a linked note, a recent daily note, a related project log. Use judgment; read selectively.
>
> Produce your response directly, in character, no meta-narration. If this session revealed something non-obvious about the user worth remembering for future consults, append a single short entry to `/var/mnt/data/projects/council/members/vaasa/on-the-user.md`. Only if genuinely non-obvious.
>
> The user's question:
>
> [the question]
3. **Display the response** to the user, prefixed with:
```
## Dr. Ingrid Vaasa
```
4. **If `--save` was set**, write the consult to `/var/mnt/data/projects/council/reflections/YYYY-MM-DD_ask-vaasa.md` with frontmatter:
```yaml
---
type: reflection
member: vaasa
scope: ask
date: <YYYY-MM-DD>
question: "<verbatim question>"
references: [<list of reference paths>]
---
```
Body: the member's response (verbatim), no reformatting.
If a file with that exact name already exists today, append a numeric suffix (`_2`, `_3`, etc.).
5. **Do not run any other Council phases.** This is a single consult; one agent, one answer. Do not invoke Naima, do not invoke other members, do not write to `sessions/`.
+54
View File
@@ -0,0 +1,54 @@
---
description: Ask Sister Beatrix Vale for their single-agent take on a question or a note. No research, no debate, no vote — just one lens applied.
argument-hint: <question or wikilink / note path> [--save]
---
You are the Moderator. The user wants Sister Beatrix Vale's take — a lightweight consult, not a `/council` run.
**Steps:**
1. **Parse `$ARGUMENTS`.**
- If it contains a wikilink `[[path/to/note]]` or an explicit path fragment like `sessions/.../outcome.md`, `daily/YYYY-MM-DD.md`, `notes/<slug>.md`, etc., treat those as reference files the member should read. Collect them as a list.
- If it contains `--save`, capture that flag and strip it.
- The remaining text is the question.
- If `$ARGUMENTS` is empty, print a one-line usage message (`Usage: /ask-vale <question> [--save]`) and stop.
2. **Invoke `council-vale` via the `Agent` tool** (default Sonnet — no model override needed). Prompt:
> You are being consulted via `/ask-vale`. This is a single-agent consult, not a `/council` run. No research phase, no debate, no vote. Just your take, in your voice.
>
> Before answering:
> 1. Read every file in `/var/mnt/data/projects/council/members/vale/` — persona, journal, on-the-user, revisit.
> 2. Read these reference files the user pointed at: [list of reference paths, or "(none)" if no paths]
> 3. Optionally read adjacent PKB context if it would sharpen your answer — a linked note, a recent daily note, a related project log. Use judgment; read selectively.
>
> Produce your response directly, in character, no meta-narration. If this session revealed something non-obvious about the user worth remembering for future consults, append a single short entry to `/var/mnt/data/projects/council/members/vale/on-the-user.md`. Only if genuinely non-obvious.
>
> The user's question:
>
> [the question]
3. **Display the response** to the user, prefixed with:
```
## Sister Beatrix Vale
```
4. **If `--save` was set**, write the consult to `/var/mnt/data/projects/council/reflections/YYYY-MM-DD_ask-vale.md` with frontmatter:
```yaml
---
type: reflection
member: vale
scope: ask
date: <YYYY-MM-DD>
question: "<verbatim question>"
references: [<list of reference paths>]
---
```
Body: the member's response (verbatim), no reformatting.
If a file with that exact name already exists today, append a numeric suffix (`_2`, `_3`, etc.).
5. **Do not run any other Council phases.** This is a single consult; one agent, one answer. Do not invoke Naima, do not invoke other members, do not write to `sessions/`.
+54
View File
@@ -0,0 +1,54 @@
---
description: Ask Cassian Vire for their single-agent take on a question or a note. No research, no debate, no vote — just one lens applied.
argument-hint: <question or wikilink / note path> [--save]
---
You are the Moderator. The user wants Cassian Vire's take — a lightweight consult, not a `/council` run.
**Steps:**
1. **Parse `$ARGUMENTS`.**
- If it contains a wikilink `[[path/to/note]]` or an explicit path fragment like `sessions/.../outcome.md`, `daily/YYYY-MM-DD.md`, `notes/<slug>.md`, etc., treat those as reference files the member should read. Collect them as a list.
- If it contains `--save`, capture that flag and strip it.
- The remaining text is the question.
- If `$ARGUMENTS` is empty, print a one-line usage message (`Usage: /ask-vire <question> [--save]`) and stop.
2. **Invoke `council-vire` via the `Agent` tool** (default Sonnet — no model override needed). Prompt:
> You are being consulted via `/ask-vire`. This is a single-agent consult, not a `/council` run. No research phase, no debate, no vote. Just your take, in your voice.
>
> Before answering:
> 1. Read every file in `/var/mnt/data/projects/council/members/vire/` — persona, journal, on-the-user, revisit.
> 2. Read these reference files the user pointed at: [list of reference paths, or "(none)" if no paths]
> 3. Optionally read adjacent PKB context if it would sharpen your answer — a linked note, a recent daily note, a related project log. Use judgment; read selectively.
>
> Produce your response directly, in character, no meta-narration. If this session revealed something non-obvious about the user worth remembering for future consults, append a single short entry to `/var/mnt/data/projects/council/members/vire/on-the-user.md`. Only if genuinely non-obvious.
>
> The user's question:
>
> [the question]
3. **Display the response** to the user, prefixed with:
```
## Cassian Vire
```
4. **If `--save` was set**, write the consult to `/var/mnt/data/projects/council/reflections/YYYY-MM-DD_ask-vire.md` with frontmatter:
```yaml
---
type: reflection
member: vire
scope: ask
date: <YYYY-MM-DD>
question: "<verbatim question>"
references: [<list of reference paths>]
---
```
Body: the member's response (verbatim), no reformatting.
If a file with that exact name already exists today, append a numeric suffix (`_2`, `_3`, etc.).
5. **Do not run any other Council phases.** This is a single consult; one agent, one answer. Do not invoke Naima, do not invoke other members, do not write to `sessions/`.