transcriptlisted

# MANDATORY: CLI Invocation for Parsing (Phase 1) > **CRITICAL:** For VTT files, you MUST invoke the Python parser via the `jerry` CLI. > DO NOT use Task agents for parsing. The CLI provides 1,250x cost reduction and deterministic output. ## Phase 1: Parse Transcript (REQUIRED CLI INVOCATION) **ARGUMENT PARSING RULES:** 1. The FIRST positional argument from user input is the `<file-path>` (the VTT/SRT file) 2. The `--output-dir` flag specifies the output directory (default: `./transcript-output`) 3. **IMPORTANT:** If user provides `--output`, treat it as `--output-dir` (alias) **For VTT files, Claude MUST execute this bash command:** ```bash uv run jerry transcript parse "<FILE_PATH>" --output-dir "<OUTPUT_DIR>" ``` Where: - `<FILE_PATH>` = The ACTUAL file path from the user's invocation (first positional arg) - `<OUTPUT_DIR>` = The output directory from `--output-dir` or `--output` flag (default: `./transcript-output`) **Example - user invokes:** ``` /transcript /Users/me/meeting.vtt --output-dir /Users/me/output/ ``` **Claude executes:** ```bash uv run jerry transcript parse "/Users/me/meeting.vtt" --output-dir "/Users/me/output/" ``` **CRITICAL:** Always quote file paths to handle spaces and special characters. **Expected output:** - `index.json` - Chunk metadata and speaker summary - `chunks/chunk-*.json` - Transcript segments in processable chunks - `canonical-transcript.json` - Full parsed output (for reference only, DO NOT read into context) ### Tool Example