Context Over Convenience
RepoPrompt's workflows are built on one principle: give the model the right context before it acts. Context Builder handles the discovery, powerful analysis models plan and review, and agents implement through orchestration.
How Context Builder Works
Every workflow starts with Context Builder, a two-stage pipeline that separates discovery from reasoning:
01 Explore
Agent navigates codebase
02 Curate
Select within token budget
Example handoff: auth.ts L5–89, api.ts L22–58, useAuth.ts L1–41, Header.tsx L12–67.
03 Handoff
Structured prompt for analysis
Built-in Workflows
Each workflow is a slash command you can run from Agent Mode or any MCP client:
| Command | What It Does | Best For |
|---|---|---|
/rp-orchestrate | Plans (or accepts a plan), decomposes into tasks, dispatches sub-agents across providers | Any complex work. Replaces /rp-build with better results |
/rp-build | Context Builder gathers files, analysis model creates plan, then implement in one session | Faster alternative when you don’t need sub-agent delegation |
/rp-review | Publishes git diffs alongside codebase context for grounded reviews | Code reviews, PR review |
/rp-refactor | Two-pass: analyze for opportunities, then plan preserving behavior | Refactoring, cleanup |
/rp-investigate | Systematic exploration with evidence gathering | Bugs, root cause analysis |
Orchestration: Multi-Agent Workflows
The /rp-orchestrate workflow goes beyond single-agent execution. Give it a pre-existing plan, or let it generate one on the fly with Context Builder. It freely delegates tasks to sub-agents across providers like Codex, OpenCode, and Gemini, supervising their work and steering as needed.
- Flexible planning: Works with a plan you provide, or uses Context Builder to generate one automatically
- Autonomous delegation: The orchestrator decides when to run tasks in parallel or sequence based on dependencies
- Multi-provider: Sub-agents can use any available provider. Pick the right model for each task
- Verification: The orchestrator checks each result against the plan before continuing
Personal agents like OpenClaw can launch orchestration workflows via the CLI, completing complex engineering work asynchronously while you're away.
ChatGPT Pro Planning
For the highest-quality architectural plans, RepoPrompt has a native ChatGPT Export workflow. Describe what you need, and RepoPrompt assembles the curated context into a prompt ready to paste into ChatGPT Pro for GPT-5.5 Pro's extended reasoning:
GPT-5.5 Pro is a ChatGPT Pro (web) model. For in-app implementation and review, use Codex CLI with GPT-5.5 Medium/High — that's the recommended in-app agent path, not a ChatGPT Export target.
- Click ChatGPT Export in Agent Mode
- Describe your task
- Copy the assembled prompt and paste into ChatGPT Pro
- Hand the resulting plan to your coding agent for implementation
When to export: Use ChatGPT Pro planning for high-stakes architectural decisions. For routine tasks, the built-in workflows handle planning automatically.
Why Context Over Convenience?
Coding agents are convenient but fundamentally limited. When they search and code simultaneously, context fills with noise before they understand the problem:
- Tool calls, grep results, and backtracking exhaust the context window
- By the time the agent understands your code, its effective reasoning is degraded
- Solutions miss architectural patterns and duplicate existing functionality
Context Builder solves this by separating discovery from reasoning. The analysis model receives clean, curated context and spends its entire thinking budget on the solution, not on figuring out which files to read.
Read the full philosophy: Context Over Convenience
Choosing a Workflow
| Situation | Recommended |
|---|---|
| Small feature, quick fix | Just ask the agent directly, no workflow needed |
| Any complex work | /rp-orchestrate: plans and delegates, works at any scale |
| Complex work, want speed over thoroughness | /rp-build: same pipeline, single session, faster |
| High-stakes architecture | ChatGPT Export: GPT-5.5 Pro extended reasoning |
| Review a PR or recent changes | /rp-review |
| Clean up or restructure code | /rp-refactor |
| Bug or mysterious behavior | /rp-investigate |
| Autonomous, overnight work | OpenClaw + /rp-orchestrate via CLI |
Your Role as Engineer
- Scope correctly: Break large tasks into manageable pieces
- Guide discovery: Mention key files or areas in your task description
- Review changes: Validate implementation matches the plan
- Iterate: Use review workflows to catch issues early