flow-next-export-context

Export Context Mode

Build RepoPrompt context and export to a markdown file for use with external LLMs (ChatGPT Pro, Claude web, etc.).

Use case: When you want Carmack-level review but prefer to use an external model.

Preamble

CRITICAL: flowctl is BUNDLED — NOT installed globally. which flowctl will fail (expected). Define once; subsequent blocks use $FLOWCTL:

FLOWCTL="${CODEX_HOME:-$HOME/.codex}/scripts/flowctl"
[ -x "$FLOWCTL" ] || FLOWCTL="<plugin-root>/scripts/flowctl"   # <plugin-root> = the directory two levels above this skill's SKILL.md file (the harness gave you that file's absolute path when the skill loaded); substitute it literally
[ -x "$FLOWCTL" ] || FLOWCTL=".flow/bin/flowctl"

Input

Arguments: $ARGUMENTS Format: <type> <target> [focus areas]

Types:

• plan <spec-id> - Export plan review context
• impl - Export implementation review context (current branch)

This skill is phrase-triggered (no slash command) — invoke it by asking in natural language; the host agent parses <type> <target> [focus areas] from the request.

Examples:

• "export context for plan fn-1, focus on security"
• "export impl review context, focus on the auth changes"

Setup

REPO_ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"

Workflow

Step 1: Determine Type

Parse arguments to determine if this is a plan or impl export.

Step 2: Gather Content

For plan export:

$FLOWCTL show <spec-id> --json
$FLOWCTL cat <spec-id>

For impl export:

git branch --show-current
git log main..HEAD --oneline 2>/dev/null || git log master..HEAD --oneline
git diff main..HEAD --name-only 2>/dev/null || git diff master..HEAD --name-only

Step 3: Setup RepoPrompt

eval "$($FLOWCTL rp setup-review --repo-root "$REPO_ROOT" --summary "<summary based on type>" --create)"

Step 4: Augment Selection

$FLOWCTL rp select-get --window "$W" --tab "$T"

# Add relevant files
$FLOWCTL rp select-add --window "$W" --tab "$T" <files>