Run APR (Automated Plan Reviser) workflow for FCP specification refinement. Use when asked to run APR, revision rounds, spec review, integrate GPT feedback, or harmonize docs. Handles Oracle remote setup, running rounds, integrating feedback, and syncing README/implementation docs.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
apr
description
Run APR (Automated Plan Reviser) workflow for FCP specification refinement. Use when asked to run APR, revision rounds, spec review, integrate GPT feedback, or harmonize docs. Handles Oracle remote setup, running rounds, integrating feedback, and syncing README/implementation docs.
APR - Automated Plan Reviser for FCP
This skill automates iterative specification refinement using GPT Pro 5.2 Extended Reasoning via Oracle.
Quick Start
Run next round (fully automated):
run apr round <N>
This will:
Run apr run <N> --wait to get GPT Pro feedback
Read and analyze all revisions
Integrate each revision into FCP_Specification_V2.md
Harmonize README.md with changes
Harmonize docs/fcp_model_connectors_rust.md
Commit changes in logical groups with detailed messages
Push to remote
Run continuous rounds:
keep running apr rounds starting from <N>
Overview
The Flywheel Connector Protocol (FCP) specification is refined through multiple rounds of GPT Pro review. Each round:
Sends README + spec (optionally + implementation) to GPT Pro 5.2
Receives detailed revision suggestions with rationale
Integrates feedback into the spec via Claude Code
Harmonizes README and implementation docs
Commits with detailed messages
Oracle Remote Setup (One-Time)
For headless/SSH environments, Oracle can delegate browser automation to a local machine.
On the LOCAL machine (with browser/GUI):
# Install Oracle if needed
npm install -g @steipete/oracle
# Start server (keep this terminal open)
oracle serve --port 9333 --token
# IMPORTANT: Use port 9333 (not 9222) to avoid conflict with Chrome DevTools
"flywheel-apr-2026"
On the REMOTE machine (this server):
# Add to shell config for persistenceecho'export ORACLE_REMOTE_HOST="100.114.183.31:9333"' >> ~/.zshrc
echo'export ORACLE_REMOTE_TOKEN="flywheel-apr-2026"' >> ~/.zshrc
source ~/.zshrc
# Test connection
oracle -p "test connection" -e browser -m "5.2 Pro"
Why port 9333? Oracle serve listens on this port for incoming requests. When it
receives a request, it launches Chrome which uses port 9222 for DevTools Protocol.
Using 9333 for the server avoids the port conflict.
Tailscale IPs for this setup:
Mac Mini: 100.114.183.31
iMac: 100.81.209.68
This server (threadripperje): 100.91.120.17
Commands
Important: Always run APR from the project directory:
cd /data/projects/flywheel_connectors
Check Status
apr status # Check Oracle sessions
apr list # List workflows
apr history# Show revision history
apr dashboard # Interactive analytics
Run a Revision Round
# Standard round (README + spec only)
apr run <N> --wait# Include implementation doc (manual override)
apr run <N> --include-impl --wait# With impl_every_n: 4 in workflow config, impl is auto-included on rounds 4, 8, 12...# Preview without sending
apr run <N> --dry-run
# Render prompt for manual paste
apr run <N> --render --output /tmp/prompt.md
How Documents Are Sent
APR pastes document contents inline (not as file attachments). This is more reliable:
No "duplicate file" errors from ChatGPT
No silent upload failures
Works consistently for documents up to ~200KB
View and Compare Rounds
apr show <N> # View round output
apr diff <N> <M> # Compare two rounds
apr diff <N> # Compare round N vs N-1
Automated Integration Workflow
When user requests a round, Claude Code performs these steps automatically:
Step 1: Run APR and Get Feedback
apr run <N> --wait
Step 2: Read and Analyze Revisions
Read .apr/rounds/fcp/round_<N>.md
Parse all revision suggestions
Create todo list for each revision
Step 3: Integrate Each Revision
For each revision in the GPT Pro output:
Locate relevant sections in FCP_Specification_V2.md
