| name | amplify |
| description | Use when a prompt is rough, vague, or under-specified and you want it rewritten to high quality before running it. Domain-aware: detects the prompt's domain, stitches the matching specialist standards, reads project rules, and scores the result against an 8-dimension rubric. Standalone — ends with a handoff gate to push the amplified prompt into the chain.
Trigger with /hyperflow:amplify, "enhance this prompt", "make this prompt better", "improve my prompt", "rewrite this prompt".
|
| allowed-tools | Read, Glob, Grep, Agent, AskUserQuestion, Skill |
| argument-hint | <raw prompt to enhance> (omit to amplify your previous message) |
| version | 1.0.0 |
| license | MIT |
| compatibility | Designed for Claude Code |
| tags | ["prompt-engineering","enhancement","quality","personas","multi-agent"] |
Amplify
Turn a rough prompt into a high-signal one. Detect the domain, inject the standards that domain demands, score it against a rubric — then offer to run it.
Dispatcher and reviewer — Opus 4.8 (thinking-tier). Searcher/Writer — Sonnet 4.6 (worker-tier).
Amplify does one thing well: it rewrites the prompt you give it into the single strongest version, then hands it off. It does not write code itself — it produces a prompt other skills (or you) execute.
Per-Step Agent Map (DOCTRINE rule 12)
Every substantive step dispatches at least one Agent. Atomic steps (DOCTRINE 12.2.8) are a single Worker → Reviewer pair with no independent angles to fan out.
| Step | Status | Worker tier | Thinking tier | Notes |
|---|
| 1 — Read intent | Atomic (12.2.8) | Searcher (Sonnet) — domain signals + project rules | Analyst (Opus) — triage + gap analysis + persona selection | Single Worker → Reviewer; reads CLAUDE.md, AGENTS.md, .hyperflow/memory/* |
| 2 — Amplify | Atomic (12.2.8) | Writer (Sonnet) — draft the enhanced prompt | Reviewer (Opus) — rubric score, one targeted revision | Writer drafts → Opus scores against the 8-dim rubric → revise once if any dim < 4 |
| 3 — Present + handoff | §12.1 inline | — | — | Print the amplified prompt + rationale; fire the handoff gate (AskUserQuestion) |
Inputs
$ARGUMENTS — the raw prompt to amplify. If empty, amplify the user's previous message in the conversation.- No flags. Amplify always produces the single best version (per the design decision); the rubric, not a flag, governs depth.
Flow
Step 1 — Read intent (atomic · 12.2.8)
Atomic — a single Searcher → Analyst pair. No parallel angles: understanding one prompt is one scope.
-
Dispatch Searcher — detecting prompt domain + gathering project rules (Sonnet). It returns:
- Domain signals — does the prompt concern frontend/ui/creative, api/db backend, mobile, security, performance, refactor/bugfix/test, devops, docs? (A prompt can span several.)
- Project rules — read, when present: , , , , . Extract any rule that should constrain the prompt.
