/flow-next-export-context
Export RepoPrompt context to a markdown file for review with an external LLM (ChatGPT, Claude web, etc.). Use when you want Carmack-level review but prefer an external model. Triggers on "export context", "export for external review", "export plan for ChatGPT", "export impl
$ npx -y skills add gmickel/flow-next --skill flow-next-export-context --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/flow-next-export-context
Context preview
The summary Claude sees to decide when to auto-load this skill.
Export RepoPrompt context to a markdown file for review with an external LLM (ChatGPT, Claude web, etc.). Use when you want Carmack-level review but prefer an external model. Triggers on "export context", "export for external review", "export plan for ChatGPT", "export impl
SKILL.md
flow-next-export-context.SKILL.mdname: flow-next-export-context
description: Export RepoPrompt context to a markdown file for review with an external LLM (ChatGPT, Claude web, etc.). Use when you want Carmack-level review but prefer an external model. Triggers on "export context", "export for external review", "export plan for ChatGPT", "export impl review context", "review with an external model", "export review 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="${DROID_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}/scripts/flowctl"
[ -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>
Step 5: Build Review Prompt (file composition — no content re-typing)
**Path-persistence rule:** bash vars do NOT survive across tool calls. Compose a literal unique prompt path in agent context — `${TMPDIR:-/tmp}/flow-export-prompt-<target>-<agent-chosen 4-char suffix>.md` — and type it verbatim in every block that references it.
Build the prompt by deterministic composition — the handoff is captured via redirection, never pasted into a heredoc; only the static review criteria (same criteria as plan-review or impl-review) are typed, once, in the quoted heredoc:
PROMPT_FILE="${TMPDIR:-/tmp}/flow-export-prompt-<target>-<suffix>.md" # literal path
# 1. Builder handoff — captured via redirection, never re-typed
$FLOWCTL rp prompt-get --window "$W" --tab "$T" > "$PROMPT_FILE"
# 2. Review criteria (static, quoted heredoc — same criteria block as
# plan-review or impl-review, per the export type)
cat >> "$PROMPT_FILE" << 'EOF'
<review criteria — static block>
EOF
$FLOWCTL rp prompt-set --window "$W" --tab "$T" --message-file "$PROMPT_FILE"Step 6: Export
OUTPUT_FILE=~/Desktop/review-export-$(date +%Y%m%d-%H%M%S).md
$FLOWCTL rp prompt-export --window "$W" --tab "$T" --out "$OUTPUT_FILE"
open "$OUTPUT_FILE"
Step 7: Inform User
Exported review context to: $OUTPUT_FILE
The file contains:
- Full file tree with selected files marked
- Code maps (signatures/structure)
- Complete file contents
- Review prompt with Carmack-level criteria
Paste into ChatGPT Pro, Claude web, or your preferred LLM.
After receiving feedback, return here to implement fixes.
Note
This skill is for **manual** external review only. It does not work with Ralph autonomous mode (no receipts, no status updates).
Read more
name: flow-next-export-context description: Export RepoPrompt context to a markdown file for review with an external LLM (ChatGPT, Claude web, etc.). Use when you want Carmack-level review but prefer an external model. Triggers on "export context", "export for external review", "export plan for ChatGPT", "export impl review context", "review with an external model", "export review 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="${DROID_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}/scripts/flowctl"
[ -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>
Step 5: Build Review Prompt (file composition — no content re-typing)
**Path-persistence rule:** bash vars do NOT survive across tool calls. Compose a literal unique prompt path in agent context — `${TMPDIR:-/tmp}/flow-export-prompt-<target>-<agent-chosen 4-char suffix>.md` — and type it verbatim in every block that references it.
Build the prompt by deterministic composition — the handoff is captured via redirection, never pasted into a heredoc; only the static review criteria (same criteria as plan-review or impl-review) are typed, once, in the quoted heredoc:
PROMPT_FILE="${TMPDIR:-/tmp}/flow-export-prompt-<target>-<suffix>.md" # literal path
# 1. Builder handoff — captured via redirection, never re-typed
$FLOWCTL rp prompt-get --window "$W" --tab "$T" > "$PROMPT_FILE"
# 2. Review criteria (static, quoted heredoc — same criteria block as
# plan-review or impl-review, per the export type)
cat >> "$PROMPT_FILE" << 'EOF'
<review criteria — static block>
EOF
$FLOWCTL rp prompt-set --window "$W" --tab "$T" --message-file "$PROMPT_FILE"Step 6: Export
OUTPUT_FILE=~/Desktop/review-export-$(date +%Y%m%d-%H%M%S).md $FLOWCTL rp prompt-export --window "$W" --tab "$T" --out "$OUTPUT_FILE" open "$OUTPUT_FILE"
Step 7: Inform User
Exported review context to: $OUTPUT_FILE The file contains: - Full file tree with selected files marked - Code maps (signatures/structure) - Complete file contents - Review prompt with Carmack-level criteria Paste into ChatGPT Pro, Claude web, or your preferred LLM. After receiving feedback, return here to implement fixes.
Note
This skill is for **manual** external review only. It does not work with Ralph autonomous mode (no receipts, no status updates).
Repeatable agentic engineering. The workflow layer that turns AI coding agents into a disciplined factory: durable specs, fresh-context workers, adversarial cross-model reviews, receipts. Everything in your repo, zero dependencies. Claude Code · Codex · Cursor · Droid.
Other skills on flow-next.
- /flow-next-audit
Audit .flow/memory/ entries against current code and keep, update, consolidate, replace, delete, or harden each. Use when asked to audit memory or graduate a recurring lesson into a gate.
Open skill - /flow-next-capture
Synthesize the current conversation into a flow-next spec with read-back gating. Use when asked to capture this as a spec.
Open skill - /flow-next-chart
Decision-map discovery for one oversized unclear idea before capture. Resolve one decision per invocation, brief for capture. Use when asked to chart an idea or work a chart decision.
Open skill - /flow-next-deps
Show spec dependency graph and execution order. Use when asking 'what's blocking what', 'execution order', 'dependency graph', 'what order should specs run', 'critical path', 'which specs can run in parallel'.
Open skill - /flow-next-drive
Drive any UI surface like a real user - a web app, a Chromium-backed desktop app (Electron / WebView2, reached over CDP), or a genuinely native app (macOS AppKit/SwiftUI, or a non-CDP webview) reached via the Cua Driver / Computer Use. Detects the surface, picks the best
Open skill - /flow-next-guide
Recommend the smallest sufficient flow-next workflow from the starting state. Stateless router. Use when unsure which command or stage applies next.
Open skill

