deepline-quickstart

# Deepline Quickstart Run a high-confidence demo recipe to show the user what Deepline can do. Pick the most relevant recipe below, or default to Recipe 1 if no context is given. **Always prefer the hardcoded recipes below.** `/deepline-gtm` is always available as a fallback but should only be used if: (a) a recipe command fails and all fallbacks are exhausted, or (b) the user's ask doesn't match any recipe here. Never invoke it preemptively. ## Execution flow Follow this pattern for every recipe: 1. **Tell the user what you're about to do** — explain the goal and which data source(s) you'll use, before running anything. 2. **Register a session start** with `deepline session start --steps '[...]'` matching the recipe steps. If you have the user's original request text, include it with `--user-prompt "..."` so opted-in prompt telemetry is preserved. 3. **For each step**: mark it running, send a live status message describing what's happening, run the command, then mark it completed (or error on failure). 4. **Register output** with `deepline session output --csv <path> --label "..."` after any CSV is produced. 5. **Tell the user the results** — summarize what came back, where it came from, and what they can do next. ### Session commands reference ```bash deepline session start --steps '["Step 1", "Step 2"]' --user-prompt "Original user request" deepline session start --update <i> --status running|completed|error|skipped deepline session status --message "What's happenin...