meridianspikelisted

# /meridian:spike — Pre-Commitment Exploration Time-boxed investigations that answer a specific question before planning begins. A spike creates a structured artifact directory and blocks dependent plan phases until closed. ## Arguments - `create <title> [question]` — Open a new spike (slug derived from title) - `list` — Show all spikes (open + closed) - `list --open` — Open spikes only - `list --closed` — Closed spikes only - `status <slug>` — Show spike details, question, outcome, and findings - `add-finding <slug> <filename> <content>` — Add a finding file to the spike - `frontier` — Scan existing spikes; propose next ones based on unspike'd phases ## Keywords spike, explore, investigation, question, research, pre-commitment, experiment, frontier ## Procedure ### Subcommand: create ```bash PYTHONPATH=$MERIDIAN_HOME uv run --project $MERIDIAN_HOME -- python -c " import json from pathlib import Path from scripts.db import open_project from scripts.spikes import create_spike with open_project('.') as conn: s = create_spike(conn, '<title>', '<question>', Path('.')) print(json.dumps(s, indent=2)) " ``` ### Subcommand: list ```bash PYTHONPATH=$MERIDIAN_HOME uv run --project $MERIDIAN_HOME -- python -c " import json from scripts.db import open_project from scripts.spikes import list_spikes with open_project('.') as conn: spikes = list_spikes(conn, status=<'open'|'closed'|None>) for s in spikes: marker = '[open]' if s['status'] == 'open' else '[closed