| name | ctx-kb-note |
| description | Lightweight capture into .context/ingest/findings.md. Single argument is the note text. Never writes to a topic page or to evidence-index.md. The pipeline's ad-hoc escape hatch for "park this for the next ingest". |
Park a Finding for the Next Ingest
Append a short note to .context/ingest/findings.md so a later
/ctx-kb-ingest pass can pick it up. This is the pipeline's
escape hatch for "I want to remember this, but I'm not running
a full ingest right now." No closeout, no ledger update, no
topic-page edit, no EV-### minting. Just typed memory landing
in one well-known file.
Authoritative background reading:
.context/ingest/KB-RULES.md §Authority boundary;
specs/kb-editorial-pipeline.md §Interface.
When to Use
- The user says "drop a note", "capture this for the next
ingest", "park this finding", or invokes the explicit slash
form with note text.
- A conversation surfaces a fact, link, or observation that
should land in the kb later but does not justify running
/ctx-kb-ingest right now.
- Mid-session, a sibling skill (architecture, brainstorm, etc.)
surfaces something kb-shaped and the user wants it parked
cheaply.
When NOT to Use
- The user has sources in hand and wants them ingested (use
/ctx-kb-ingest).
- The user is asking a content question (use
/ctx-kb-ask).
- The note is actually a task / decision / learning / convention
for the code-dev side (use
/ctx-task-add /
/ctx-decision-add / /ctx-learning-add /
/ctx-convention-add; those write to canonical files, this
one does not).
- The note is empty (refuse-on-empty; see below).
Authority Boundary (vs Other Skills)
