ReddRadar
Agent skill
flow-next-export-context
Export RepoPrompt context for external LLM review (ChatGPT, Claude web, etc.). Use when you want to review code or plans with an external model. Triggers on /flow-next:export-context.
Install this agent skill to your Project
npx add-skill https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-export-context
SKILL.md
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.
CRITICAL: flowctl is BUNDLED — NOT installed globally. which flowctl will fail (expected). Always use:
FLOWCTL="${DROID_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}/scripts/flowctl"
$FLOWCTL <command>
Input
Arguments: $ARGUMENTS
Format: <type> <target> [focus areas]
Types:
plan <epic-id>- Export plan review contextimpl- Export implementation review context (current branch)
Examples:
/flow-next:export-context plan fn-1 focus on security/flow-next:export-context impl focus on the auth changes
Setup
FLOWCTL="${DROID_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}/scripts/flowctl"
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 <epic-id> --json
$FLOWCTL cat <epic-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
Get builder's handoff:
$FLOWCTL rp prompt-get --window "$W" --tab "$T"
Build combined prompt with review criteria (same as plan-review or impl-review).
Set the prompt:
cat > /tmp/export-prompt.md << 'EOF'
[COMBINED PROMPT WITH REVIEW CRITERIA]
EOF
$FLOWCTL rp prompt-set --window "$W" --tab "$T" --message-file /tmp/export-prompt.md
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).
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
gmickel/flow-next
flow-next-impl-review
John Carmack-level implementation review via RepoPrompt or Codex. Use when reviewing code changes, PRs, or implementations. Triggers on /flow-next:impl-review.
gmickel/flow-next
flow-next
Manage .flow/ tasks and epics. Triggers: 'show me my tasks', 'list epics', 'what tasks are there', 'add a task', 'create task', 'what's ready', 'task status', 'show fn-1-add-oauth'. NOT for /flow-next:plan or /flow-next:work.
gmickel/flow-next
flow-next-plan
Create structured build plans from feature requests or Flow IDs. Use when planning features or designing implementation. Triggers on /flow-next:plan with text descriptions or Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).
gmickel/flow-next
flow-next-worktree-kit
Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
gmickel/flow-next
flow-next-rp-explorer
Token-efficient codebase exploration using RepoPrompt CLI. Use when user says "use rp to..." or "use repoprompt to..." followed by explore, find, understand, search, or similar actions.
gmickel/flow-next
flow-next-deps
Show epic dependency graph and execution order. Use when asking 'what's blocking what', 'execution order', 'dependency graph', 'what order should epics run', 'critical path', 'which epics can run in parallel'.
Didn't find tool you were looking for?