How do I install the Vestige Record Question skill?

Run npx skillmds@latest add conorluddy/vestige-record-question in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Vestige Record Question safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vestige Record Question?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vestige Record Question free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Vestige Record Question?

conorluddy (@conorluddy) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vestige Record Question by conorluddy

Name: Vestige Record Question
Author: conorluddy

Vestige Record Question

Capture an open question to Vestige memory when an ambiguity can't be resolved now and needs a human, investigation, or later session. Fire on "TBD:", "open question:", "we should figure out…", "unclear whether…", "follow-up:", "to investigate:", "leaving X open", or when the user says "capture that as a question", "we'll come back to that", "park that for now", "good question — note it down". Questions surface in every `vestige context` pack until `vestige-forget`'d (typically when answered via `vestige-record-decision`). Default importance 0.5. Returns the new handle (`mem_<ULID>`).

conorluddy Updated Sep 17, 2026

File contents

Record an open question

Capture an unresolved question / ambiguity / TBD so it isn't lost between sessions. Questions surface in the project context pack so future-you (or a future agent) can either answer them or rule them out.

When to fire

A real ambiguity surfaced — the answer matters but isn't available now.
You're tempted to write "TODO" or "FIXME" but it's a design question, not a code task.
The user said "let's come back to that" / "park it" / "we'll figure that out later".
You wrote ## Open Questions or ### TBD in your own response.

Tie-breakers vs siblings:

Question vs note — if the answer is known and you're recording the answer, that's a note (or a decision). Questions are unknowns.
Question vs source TODO — if it's "write the function, fix the bug", leave a TODO comment in the source. Memories are for project-level ambiguities.

How to invoke

vestige question add "<the question, framed as a question>" \
  --importance 0.5 \
  --json

body (positional, required): write it as an actual question. "Should we keep V0 single-process or move to a daemon?" beats "Daemon mode TBD".
--importance (optional, default 0.5): bump to 0.8+ for blockers; drop to 0.3 for "nice to know eventually".
--source (optional): when the question was prompted by a specific file or piece of context, attach it.

After invocation

The JSON envelope returns { "id": "mem_<ULID>", ... }. Surface: "Captured open question mem_…. It'll appear in vestige context until resolved."

When the question gets answered later:

Use vestige-record-decision (or -note) to capture the answer.
Use vestige-forget on the original question's handle so the context pack stops surfacing it.

The journal still has the original question — forget is soft.

Idempotence & dedup

Every call is a fresh write. Before capturing, dedup:

vestige recall "<key phrase>" --type question --json --limit 3

If the same question is already open, don't double-capture — the first one will already keep surfacing in the context pack. Only re-capture if you're rephrasing for clarity, in which case vestige-forget the old phrasing.

---name: vestige-record-questiondescription: Capture an open question to Vestige memory when an ambiguity can't be resolved now and needs a human, investigation, or later session. Fire on "TBD:", "open question:", "we should figure out…", "unclear whether…", "follow-up:", "to investigate:", "leaving X open", or when the user says "capture that as a question", "we'll come back to that", "park that for now", "good question — note it down". Questions surface in every `vestige context` pack until `vestige-forget`'d (typically when answered via `vestige-record-decision`). Default importance 0.5. Returns the new handle (`mem_<ULID>`).---# Record an open questionCapture an unresolved question / ambiguity / TBD so it isn't lost between sessions. Questions surface in the project context pack so future-you (or a future agent) can either answer them or rule them out.## When to fire- A real ambiguity surfaced — the answer matters but isn't available now.- You're tempted to write "TODO" or "FIXME" but it's a *design* question, not a code task.- The user said "let's come back to that" / "park it" / "we'll figure that out later".- You wrote `## Open Questions` or `### TBD` in your own response.Tie-breakers vs siblings:- *Question vs note* — if the answer is known and you're recording the answer, that's a note (or a decision). Questions are *unknowns*.- *Question vs source TODO* — if it's "write the function, fix the bug", leave a TODO comment in the source. Memories are for *project-level* ambiguities.## How to invoke```bashvestige question add "<the question, framed as a question>" \ --importance 0.5 \ --json```- **body** (positional, required): write it as an actual question. "Should we keep V0 single-process or move to a daemon?" beats "Daemon mode TBD".- **`--importance`** (optional, default 0.5): bump to 0.8+ for blockers; drop to 0.3 for "nice to know eventually".- **`--source`** (optional): when the question was prompted by a specific file or piece of context, attach it.## After invocationThe JSON envelope returns `{ "id": "mem_<ULID>", ... }`. Surface: *"Captured open question `mem_…`. It'll appear in `vestige context` until resolved."*When the question gets answered later:1. Use `vestige-record-decision` (or `-note`) to capture the answer.2. Use `vestige-forget` on the original question's handle so the context pack stops surfacing it.The journal still has the original question — `forget` is soft.## Idempotence & dedupEvery call is a fresh write. Before capturing, dedup:```bashvestige recall "<key phrase>" --type question --json --limit 3```If the same question is already open, don't double-capture — the first one will already keep surfacing in the context pack. Only re-capture if you're rephrasing for clarity, in which case `vestige-forget` the old phrasing.

Frequently asked questions