council/.claude/commands/ask-vale.md at 97d71c4c4930747b9d4da47b44660734ed11120c

Files

T

jpmschweitzerandClaude Opus 4.7 97d71c4c49 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>

2026-04-19 20:17:12 +02:00

2.6 KiB

Raw Blame History

description, argument-hint

description	argument-hint
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.	<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:

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.
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]
Display the response to the user, prefixed with:
```
## Sister Beatrix Vale
```
If --save was set, write the consult to /var/mnt/data/projects/council/reflections/YYYY-MM-DD_ask-vale.md with frontmatter:
```
---
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.).
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/.

2.6 KiB Raw Blame History

2.6 KiB

Raw Blame History