smith-bank

Smith Idea Bank

Capture ideas mid-conversation and store them in the vault for later processing. The bank is a section of the vault where ideas get deposited for safekeeping until you're ready to withdraw them.

Arguments: $ARGUMENTS

Vault Logging

Log significant events to the vault session log. Read the session log path from .smith/vault/.current-session. If missing, skip logging silently.

Append entries using this format:

### [HH:MM:SS] /smith-bank <event>

**User Request:**
> <verbatim user message or idea description that triggered this action>

**Action:** <banked|listed|processed|edited|removed|prioritized>
**Bank ID:** <BANK-NNN>
**Title:** <idea title>
**Outcome:** <what happened>
**Systems affected:** <system IDs>

Behavior

No Arguments — Bank an Idea

When invoked with no arguments (or via natural language trigger), capture the current conversation's idea:

1. Analyze the conversation to understand the idea being banked — what it is, how it came up, what problem it solves, and any initial requirements discussed
2. Auto-detect systems the idea would likely impact by scanning .specify/systems/system-*/spec.md descriptions against the idea content. Set primary_system and also_affects.
3. Determine next bank ID by scanning .smith/vault/bank/ for existing files. Extract the highest BANK-NNN from frontmatter id: fields, then increment. Start at BANK-001 if none exist.
4. Generate the bank file at .smith/vault/bank/YYYY-MM-DD_HHMMSS-<slug>.md with this format:

---
id: BANK-NNN
title: "<concise title>"
created: "YYYY-MM-DDTHH:MM:SS"
source_session: "<current session log filename>"
primary_system: "<detected system or 'unassigned'>"
also_affects: []
status: banked
priority: medium
---

# <Title>

## Origin

<2-3 sentences describing the conversation context that led to this idea — what were we working on, what triggered the thought, why it seemed worth saving>

## Idea

<Clear description of the feature or improvement, written with enough detail that someone reading this cold could understand what to build>

## Requirements (Draft)

<Bullet points capturing any requirements that were discussed, even loosely. Include edge cases or constraints mentioned>

## Systems Affected

- **Primary:** <system name and why>
- **Also affects:** <other systems and why, or "none identified">

## Open Questions

<Any obvious questions that would need answering before this could be built. Pre-populate with the most important unknowns based on the conversation>

## Conversation Reference

Session: <link to vault session log>
Approximate timestamp: <when in the session this idea came up>