aytuncyildizli/reprompter/reprompter

RePrompter v13.3.1

Your prompt sucks. Let's fix that. Two intents — improve my prompt, or build this whole thing — with /goal, Workflow, team execution and cross-model delivery as places the result can go. v13 (RePrompter v2) restructures six lanes into two intents: a specifiability router picks spec-XML or an autonomous build prompt inside Improve, and Build can run as one prompt or split across a team. Every v12 trigger that asks for RePrompter keeps working; generic build phrases such as "vibe a game" route to Build once RePrompter is selected but no longer select it on their own.

Two intents

Users learn two sentences. Everything else is machinery underneath them.

Output formats (Improve): these apply to spec-XML results only — an outcome-prose build brief or a design-loop prompt is delivered as-is (it must not be compressed to /goal or compiled to a workflow, which would discard its staffing plan, its critic and its checklist). paste (default) · compress to a /goal <objective> command (Codex CLI, Claude Code v2.1.139+, Hermes) · compile to a runnable .workflow.js (Claude Workflow tool) · deliver to another model via headless-relay (post-output step). The /goal and Workflow sections below define these formats; their triggers ("before /goal", "workflow preflight", "compile to workflow", "dynamic workflow", ...) jump straight to Improve with that format.

Team execution (Build and beyond): "repromptverse", "reprompter teams", "smart run", "smart agents", "run with quality" and the swarm triggers route to the Repromptverse machinery below — either standalone as today, or seeded by a Build brief.

Advanced: Reverse mode (extract the prompt DNA from a great output — "reverse reprompt", "prompt dna") keeps working exactly as before and feeds the flywheel; it lives in its own section below.

Specifiability rule (Improve): the prose shapes (outcome-prose and the design loop) are exempt from every spec-XML rule in this file; see the precedence rule under Shape decision. When the router picks outcome-prose, announce it in one line — "This looks like a whole-product ask — generating an autonomous build prompt; say 'spec' for the structured version." — and switch shapes if the user objects. Outcome-prose always keeps a constraints sentence (the home for "never touch auth"); it is not scored on the six dimensions.

Only inside an already-selected RePrompter workflow: if the prompt being improved mentions 2+ systems, "audit", or "parallel", ask: "This looks like a multi-agent task. Want to use Repromptverse mode?" This cue chooses between Single and Repromptverse after skill selection; it never selects the skill. Quoted keywords, ordinary audits, and parallel implementation requests do not select RePrompter or trigger this offer.

Definition — 2+ systems means at least two distinct technical domains that can be worked independently. Examples: frontend + backend, API + database, mobile app + backend, infrastructure + application code, security audit + cost audit.

Don't use when

• User wants a simple direct answer (no prompt generation needed)
• User wants casual chat/conversation
• Task is immediate execution-only with no reprompting step
• User wants an ordinary audit, review, research task, or parallel implementation without prompt improvement or an explicit Reprompter workflow
• Reprompter-like words appear only in quoted logs, examples, file contents, or discussion
• Scope does not involve prompt design, structure, or orchestration

Clarification: RePrompter does support code-related tasks (feature, bugfix, API, refactor) by generating better prompts. It does not directly apply code changes in Single mode. Direct code execution belongs to coding-agent unless Repromptverse execution mode is explicitly requested.

Format: /goal command (Improve output)

When the user mentions /goal, before /goal, for /goal, "Codex /goal", "Claude Code /goal", "Hermes /goal", or asks to improve a goal prompt, run RePrompter before the goal is submitted.

This lane works on Codex CLI (any version exposing the goals feature), Claude Code CLI v2.1.139+ (the release that shipped a native /goal slash command on 2026-05-11), and Hermes Agent (persistent goals documented in the v0.13.0 / 2026.5.7 release). These runtimes accept the same /goal <objective> shape, so the compression flow is identical; only the setup check and a few runtime-specific operational notes differ. If the target runtime is Claude surfaces without /goal support, OpenClaw, Grok CLI, Gemini, or another LLM, use Improve (spec-XML) or Repromptverse instead; do not emit a /goal command for runtimes that have no /goal surface.

Detecting the target runtime

Pick the runtime once, at the start of the lane, and pass it through to the Card:

Process:

1. Treat the input as Single prompt mode unless it clearly needs Repromptverse.
2. Detect the target runtime (table above). Carry the runtime label through the rest of the lane.
3. Render the Goal Command Card first, with Runtime populated from step 2.
4. Infer the user's real intent from the rough prompt: desired outcome, hidden constraint, success signal, and likely risk.
5. Build the rich expanded prompt first, using the normal RePrompter structure: goal/task, context, assumptions, requirements, constraints, execution notes, and success criteria.
6. Compress that expanded prompt into a dense one-line goal summary. This should feel like a summary of a long XML prompt, not a slightly polished copy of the user's rough sentence. The compression rule is identical across runtimes — both Codex's alpha /goal and Claude Code's v2.1.139+ /goal consume <objective> as a single argument.
7. Generate an exact copy-paste command: /goal <summary of expanded prompt>.
8. Do not put the full XML or Markdown document after /goal; only the compressed summary belongs in the command.
9. Include the expanded prompt basis after the command so the user can inspect what was compressed or send it as a follow-up normal message after the goal is set.
10. Tell the user to run the exact /goal <summary of expanded prompt> command in the runtime chosen at step 2.
11. Do not claim RePrompter can automatically intercept /goal; slash commands are user-invoked in both Codex and Claude Code unless the local runtime adds a separate hook.

Goal Command Card

Both runtimes shape the slash command as /goal <objective>. Render this card before the generated command:

Then output:

/goal {dense single-line summary of the expanded prompt}

Then show the expanded prompt basis:

<goal>{specific outcome}</goal>
<context>
- {known repo/runtime/user context}
</context>
<assumptions>
- {reasonable default applied because this autonomous goal should not block on a low-value question}
</assumptions>
<requirements>
- {measurable requirement}
</requirements>
<constraints>
- {boundary or non-goal}
</constraints>
<execution_notes>
- Start with discovery before edits.
- Keep changes scoped and reversible.
- Run the verification checks listed in the Goal Command Card.
</execution_notes>
<success_criteria schema_version="1">
  <criterion id="{kebab-case-id}" verification_method="manual">
    <description>{testable pass condition}</description>
  </criterion>
</success_criteria>

Runtime-specific operational notes

The compression flow is shared, but the two /goal surfaces have small behavioral differences worth surfacing in the expanded prompt's <execution_notes> block:

Claude Code CLI (≥ v2.1.139):

• /goal sets a thread-level persistent objective that survives /resume, terminal close, and context compaction. Only one goal per session — setting a new /goal replaces the previous one.
• After each turn a separate fast evaluator model (Haiku) checks the completion condition against the transcript. If not met, the runtime triggers another turn without user input.
• The evaluator only judges what Claude surfaces in the transcript, so the expanded prompt should require the agent to print artifact paths, file contents, or test results — proof must be visible.
• Pause / resume controls: /goal pause and /goal resume (handy for long-running goals interrupted by ad-hoc work).
• Optional budget constraints (token or wall-clock) prevent runaway costs.
• `/goal` requires hooks. When disableAllHooks or allowManagedHooksOnly is set in settings.json, /goal is unavailable. v2.1.139 silently hung in this case; v2.1.140 changed the failure mode to a clear error message but did not make /goal work under those settings. If you operate in a managed environment that blocks hooks, the /goal preflight lane cannot run on Claude Code until hooks are permitted — use Single mode in that case.

Codex CLI:

• /goal is an experimental alpha feature gated by features.goals = true in ~/.codex/config.toml. The local alpha binary exposes Usage: /goal <objective>, ThreadGoal.objective, tokenBudget, /goal pause, /goal resume, and /goal clear.
• Codex's /goal is invoked the same way (/goal <objective>), but config-gated — a fresh session is required after enabling.