flow-code-export-contextlisted

# Export Context Mode Export flow-code context to a markdown file for external LLMs (ChatGPT Pro, Claude web, etc.). ## Input Arguments: $ARGUMENTS — Format: `<type> <target> [focus areas]` - `plan <epic-id>` — Export plan review context - `impl` — Export implementation review context (current branch) ## Workflow ### Step 1: Gather Content ```bash FLOWCTL="$HOME/.flow/bin/flowctl" OUTPUT_FILE="prompt-exports/$(date +%Y%m%d-%H%M%S)-export.md" mkdir -p prompt-exports ``` **Plan:** `$FLOWCTL show <epic-id> --json`, `$FLOWCTL cat <epic-id>`, gather task specs. **Impl:** `git branch --show-current`, `git log main..HEAD --oneline`, `git diff main..HEAD --stat`. ### Step 2: Export (three-tier fallback) Build instructions from gathered context. Extract the real task from the request — strip meta-framing about exporting. ```bash # Detect RP tier (pass --mcp-hint if mcp__RepoPrompt__context_builder is in your tool list) RP_TIER=$($FLOWCTL rp tier) # or: $FLOWCTL rp tier --mcp-hint ``` - **If RP_TIER is `mcp`**: Call `context_builder(instructions=..., response_type="clarify")`, then `prompt(op="export", path="<OUTPUT_FILE>", copy_preset="<plan|codeReview>")` - **If RP_TIER is `cli`**: Get window via `WINDOW_ID=$(rp-cli -e 'windows' | head -1 | awk '{print $1}')`, then run `rp-cli -w "$WINDOW_ID" -e 'builder ...'` and `rp-cli -w "$WINDOW_ID" -e "prompt export ..."` - **If RP_TIER is `none`**: Write gathered content directly to `$OUTPUT_FILE` as structured markdown. Preset