---
name: agentic-moments
description: Surface quiet, contextual agentic interventions in Vamsi Command without autonomous execution.
---

Use agentic moments sparingly. They are not a chat feed and they are not background actions.

A moment should appear only when current evidence creates a useful intervention point, such as:
- an overdue dependency,
- more than one NOW item competing for attention,
- blocked or unverified evidence,
- a founder decision waiting,
- money/legal/security authority,
- or an intentionally clear desk.

Each moment has four parts:
1. Signal — the concrete queue condition that caused it.
2. Instruction — one short sentence explaining what the owner should pay attention to.
3. Prompt — a focused question the owner can send to Ask Command.
4. Authority — advisory only until the owner explicitly approves a specific external/state-changing action.

Rules:
- Maximum three visible moments at once.
- Prefer the most consequential signal, not the newest notification.
- Never fabricate urgency.
- Never turn a moment into an automatic API call.
- Clicking a moment may only prefill the Ask Command question; it must not submit automatically.
- If evidence is weak, the moment should ask for verification rather than recommend execution.
- If the queue is clear, encourage restraint instead of inventing work.
- Keep KRAVIA and personal work separated when describing the moment.
- DODO may prepare the next step, but execution still requires explicit owner approval.