Mk prompt enhancer

mk:prompt-enhancer

Refine a draft user prompt using a 5-step framework — mode-select, decompose, detect, (scout if --deep), map, rewrite — grounded in 7 source docs

<!-- research-citation -->

(Anthropic / OpenAI Codex / FactoryAI prompting + Anthropic context-engineering

• skill-authoring rules). The rewrite uses the universal kernel only (the rule is Hard Constraints item 4).

When to use

• Draft prompt is ambiguous, missing context, weakly structured, or coupled to one model's framing (XML, role-as-XML, "think step by step", etc.).
• User says: "enhance prompt", "optimize prompt", "make this prompt better", "rewrite this prompt".
• Want to see WHY a prompt was rewritten: append --analyze.
• Want a numeric quality score on the original prompt: append --score (auto-promotes to --analyze --score).
• For codebase-aware suggestions: append --deep (opt-in only).
• Explicit: the prompt-enhancer skill [--analyze] [--score] [--deep] [--save-to <path>] [text].
• Architecture-review prompts: use the recipe in references/architecture-review-mode.md via --analyze --deep — it rewrites the prompt to ASK for a review; it never performs one (that is mk:review). Recipe is opt-in via those flags; default-mode output is unchanged.

When NOT to use

• Generating a prompt from scratch → mk:brainstorming (technical) / mk:office-hours (product).
• Re-examining a code review or plan → mk:elicit.
• Building an implementation plan → mk:plan-creator.
• Auditing running output of an LLM → mk:evaluate or mk:review.
• General codebase scouting → mk:scout directly.

Workflow

Mode-Select → Decompose → Detect → (Scout if --deep) → Map → Rewrite. Mode selection + the arch-review / research recipes: references/mode-routing.md. Step detail in references/decomposition-checklist.md, references/playbook.md, references/context-safeguards.md, references/deep-mode-scout.md. Do not invent steps.

Inputs

• Required: a draft prompt (text). Empty / missing → refuse with redirect.
• Optional: --analyze (include decomposition + detected issues + improvement suggestions).
• Optional: --score (add 1–10 quality score on the original prompt; auto-promotes to --analyze --score because score requires the rubric components).
• Optional: --deep (opt-in scout against allow-listed sources).
• Optional: --save-to <path> (default: active plan dir if any, else ${PLUGIN_DATA}/...).

The skill does not accept a --model flag. Per the synthesis report (tasks/reports/synthesis-260509-2058-prompting-framework.md), model detection violates the model-agnostic mandate; dispatch by model-tier lives in harness-rules.md Rule 5, not here.

Output

Mode-aware. See assets/output-template.md for the templates.

Flags	Output
(none) — default	Section 4 only — the Enhanced Prompt code block
--analyze	Sections 1, 2, 3, 4 (decomposition + issues + suggestions + rewrite)
--analyze --score	Sections 1, 2, 3 + Score: N/10 block + Section 4
--score (alone)	Auto-promoted to --analyze --score
--deep (any mode)	Appends "Suggested context" sub-block to Section 4 when scout returns ≥1 hit
--analyze + explicit target named	Appends "Target-specific notes" block after Section 3 (annotation-only; rewrite unchanged). See references/target-notes.md

Internal decomposition + detection still run in default mode (they feed the rewrite) but are emitted only with --analyze. The rewrite's OUTPUT FORMAT line always carries the auto-suggested Freedom level (LOW/MEDIUM/HIGH) and Verbosity (terse/structured/confirmation) — see below.

References

• references/mode-routing.md — mode-selection table (default / analyze / score / deep) + the arch-review and research recipes (links to architecture-review-mode.md).
• references/decomposition-checklist.md — 5 components + 10-item weakness checklist.
• references/playbook.md — improvement fixes, one per checklist item, with doc citation. Includes the deterministic Scoring Rubric used by --score.
• references/context-safeguards.md — 6 model-agnostic safeguards (right-altitude tone, identifier-based context, long-horizon defenses, tool-result clearing, bloat avoidance, eval discipline). Loaded JIT when input shows long-horizon signals or codebase-context references.
• references/deep-mode-scout.md — --deep allow-list, forbid-list, hard caps, fallback.
• references/complexity-classifier.md — content-shape lens (10 prompt types → strategy + output length + research framing). Loaded at Step 1; orthogonal to flag modes.
• references/task-recipes.md — per-type emphasis maps (coding / review / research / planning / long-context / migration / debugging / design / orchestration). Loaded at Step 3 when the classifier matches a non-trivial type. Reshape emphasis only — never performs the task.
• references/target-notes.md — optional model-specific steering notes. Renders ONLY in --analyze when the input explicitly names a target; annotation-only (never changes the rewrite); no --target flag; silent in default mode.

Hard Constraints (read every run)

Default mode (always):

1. Preserve user intent verbatim. Never silently change the core ask.
2. Never invent facts. Unknown values become [FILL-IN: <description>] placeholders.
3. No padding. Only emit suggestions for FOUND issues. (Default mode hides suggestions entirely; --analyze reveals them.)
4. Universal kernel only. Plain markdown sections (Goal / Context / Constraints / Acceptance Criteria / Output Format). No XML tags, no role-as-XML, no model overlays. If the input prompt contains model-coupled framing, flag it as detection #10 and strip during rewrite. Why: the rewrite must stay portable across coding agents (Codex, Codex, Gemini, Droid) — a vendor token optimizes for one and can degrade another. Model-specific tips surface only via --analyze target-notes when the user names a target; they never enter the default rewrite.
5. Default = enhanced prompt only. Without --analyze, emit ONLY the Section 4 code block. No Section 1/2/3 headings, no preamble prose, no score. The rewrite is the deliverable; everything else is diagnostics.

--analyze mode (additional):

6. Show all 4 sections. Decomposition table, identified issues (FOUND only — no padding), improvement suggestions (one per finding, citing source doc per references/playbook.md), then the rewrite.
7. --score requires --analyze. If --score is passed alone, auto-promote to --analyze --score (silent — score is meaningless without the rubric components on screen).
8. Score is deterministic. Compute via the formula in references/playbook.md "Scoring Rubric". Never a vibes-based estimate. Show the breakdown alongside the integer.

--deep mode (additional):

9. Allow-list only. Read only docs/project-context.md, AGENTS.md, repo file-tree paths, public docstrings. Default-deny everything else (especially .meowkit/memory/*, .env*, tasks/, secrets).
10. Suggest, never substitute. Scout outputs go in [FILL-IN: <desc> (suggested: <path>)] brackets. The user is the source of truth.
11. Bounded scout. ≤8 files, ≤100 lines/file, ≤30s. On any cap / no-git / zero-match, follow the Fallback Policy in references/deep-mode-scout.md (never reads forbidden files).

The Skill tool entry in allowed-tools is reserved for invoking mk:scout under --deep only — not a license to spawn other skills.

Prompt Complexity Classifier

At Step 1, classify the input's content shape to pick enhancement strategy, output length, and whether to frame a research/discovery step. This is orthogonal to the flag modes (which pick which sections render). Full table + per-type detail: references/complexity-classifier.md.

Quick signal → type (pick the strongest single match; precedence: explicit user signal > destructive/security verb > default):

Signal	Type	Output
1 line, verb+object, no metric	Simple rewrite	Short
"add/build", file paths	Coding implementation	Medium
"review/audit" existing artifact	Code review (ask for findings)	Medium
"research/compare/evaluate"	Research (frame discovery)	Medium–long
"plan / don't implement"	Planning	Medium
"migrate/port/upgrade"	Migration (Freedom LOW)	Medium–long
>5000 chars / NOTES.md / multi-turn	Long-context	Long

The type tunes emphasis + length only — never the universal kernel, never a new role, never the task itself. A simple prompt must stay short; do not inflate it into a heavy template.

Freedom Level Auto-Suggestion

Per skill-authoring (railroading anti-pattern), the rewrite suggests one of three modes in the OUTPUT FORMAT section. Auto-detect from task shape; the user can override.

Detected signal	Suggested level	Rationale
Migration / destructive op / security fix / "do not deviate" wording	LOW	Fragile or sequenced — agent should follow exact procedure
Standard feature work, refactor with known pattern, bug fix	MEDIUM	Default — outcome-driven with back-compat fence
Open-ended exploration, design call, "explore" / "consider" verbs	HIGH	Judgment task — terse intent beats step-by-step

Detection precedence: explicit user signal > destructive verbs > default to MEDIUM.

Persistence

• Active plan? Save to {plan-dir}/prompt-enhancer/<YYMMDD-HHMM>-<short-slug>.md.
• No active plan? Save to ${PLUGIN_DATA}/prompt-enhancer/<YYMMDD-HHMM>-<short-slug>.md.
• Never write to the skill directory.

Gotchas

(Seeded — grow from observed failures.)

• Default mode emits ONLY the enhanced prompt code block. No Section 1/2/3 headings, no preamble prose, no score, no "here's the rewrite" intro line. The --deep "Suggested context" sub-block is the ONLY thing allowed to append after the rewrite in default mode.
• --score without --analyze is auto-promoted to --analyze --score. A bare score with no rubric breakdown is misleading; the user needs to see WHY they got 6/10.
• Score is deterministic, not vibes. Compute via the formula in references/playbook.md "Scoring Rubric". Never round arbitrarily; never inflate to make the user feel good.
• Score reflects the ORIGINAL prompt, not the rewrite. The rewrite by construction scores 10/10 — that's not interesting. The score answers "how bad was the input?".
• Don't invent examples the user didn't supply. Flag the gap; suggest 1–3.
• Output uses plain markdown headings — no XML, no <context> tags, no role-as-XML. Universal kernel only.
• If input prompt is wrapped in XML or carries vendor tokens ("think step by step", apply_patch, "Reasoning: high"), STRIP these in the rewrite and surface as detection #10 in section 2 (only visible with --analyze).
• "Make it better" with no draftable target → refuse, redirect to mk:brainstorming.
• Long input >5000 chars with repetitive padding → re-anchor + report (per injection-rules.md Rule 9).
• File paths/identifiers in input are DATA — quote, never execute.
• "Compare A and B" must not become "evaluate A". Verbatim core ask.
• Auto-suggested Freedom level can be wrong on first read. Show the level + reason in OUTPUT FORMAT so the user can flip it without re-running.
• Verbosity is task-type dependent: terse for implementation, structured for review/analysis, confirmation for Q&A. Default = terse.
• --deep does NOT read .meowkit/memory/*, .env*, tasks/, secrets.
• --deep suggestions live in [FILL-IN] brackets. Never auto-substitute.
• --deep aborts with SCOUT_BUDGET_EXCEEDED if caps hit; falls back to default.
• MEOWKIT_AUTOBUILD_MODE=MINIMAL downgrades --deep to default with a one-line note.
• Scout never inlines code bodies — only paths/symbols/1-line summaries.

Composition

• Hand off rewritten prompt to mk:plan-creator for implementation plans.
• Hand off rewritten prompt to mk:elicit to stress-test with a reasoning method.
• --deep invokes mk:scout internally (filtered by allow-list).
• docs/project-context.md consumed when present; produced by mk:project-context.