AGENT SKILL

improve-prompt

User-invoked shortcut that rewrites a rough ask with visible assumptions and never treats rewriting as authority to execute.

License 许可
MIT
所属仓库
adriancodes/skills
最近更新
2026-11-12
Stars
★ 1
Forks
0

01 前言 Front Matter

name
improve-prompt
license
MIT
metadata
{ "summary": "Explicit shortcut for clarifying a rough ask, marking assumptions, and naming its target without silently executing it.", "category": "Authoring" }
description
User-invoked shortcut that rewrites a rough ask with visible assumptions and never treats rewriting as authority to execute.
disable-model-invocation
true

02 资源文件 98

03 SKILL.md 正文

Improve Prompt

Rewrite is not authority. Clarify the ask without changing its intent. Expose every inference. Stop unless the original request authorized execution.

Scope

Use only when explicitly invoked as /improve-prompt <rough ask> or by name.

Do not use when:

  • The request is a multi-decision plan: use create-spec when installed.
  • The request is conversational, not text to rewrite: answer it directly.

Workflow

  1. Rewrite. Preserve the goal, scope, constraints, and key phrases. Add structure only when it clarifies the request. If the ask is already precise, return it unchanged with Assumed: none.

    Done when the prompt stands alone without changing intent.

  2. Expose inference. Mark unsupported details inline as [assumed: …]. List the same assumptions below the prompt. If the rewrite would need more than three assumptions, ask one question in place of the rewrite and wait for the answer.

    Done when no invention is hidden and at most three assumptions remain.

  3. Name the target. Honor a named destination. Otherwise name the narrowest matching installed skill or plain task. Never invent a tool or broaden authority.

    Done when exactly one target is visible.

  4. Stop or execute. Stop after the rewrite unless the original request said to run, implement, or execute it. When authorized, hand the target the rewritten prompt with the inline [assumed: …] marks removed and the assumptions listed above it under Assumed:. Do only what the original request asked for.

    Done when no side effect occurs without original authorization.

Output Format

**Improved prompt**

> <standalone rewritten request with inline [assumed: …] marks>

**Assumed:** <none, or up to three items>
**Target:** <installed skill or plain task>
**Execution:** <not started, or authorized by the original request>

Example

Input: /improve-prompt make the login errors less confusing

Output:

Improved prompt

Improve the login form’s error feedback so failed attempts explain what happened without exposing account-security details [assumed: the current failure is vague user-facing feedback]. Preserve existing authentication behavior [assumed: wording and presentation are the intended scope].

Assumed: vague feedback; behavior remains unchanged

Target: plain task

Execution: not started; rewriting did not authorize implementation

Verification

  • The original intent and constraints remain intact.
  • Every unsupported detail is visibly marked and listed.
  • At most three assumptions appear before a clarifying question.
  • Exactly one target is named.
  • Execution begins only when the original request authorized it.

Stop Conditions

  • More than three assumptions are needed: Ask one question instead of writing a speculative plan.
  • Intent conflicts with visible context: Show the conflict; never silently choose a new goal.
  • No installed skill fits: Label the target plain task.

Preserve intent. Expose every assumption. Stop unless execution was already authorized.

04 同仓库更多 Skills

adriancodes
adriancodes/skills

write-agent-instructions

Make the smallest evidence-backed change to persistent project instructions and test downstream behavior.

★ 1
adriancodes
adriancodes/skills

verify-work

Use when a finished, runnable artifact (a script, config, parser, prompt, or CLI, not a diff under review) must survive hostile input before shipping: the user asks to "verify this script", "find the loopholes", "test this properly against bad input", or asks "is this ready to ship" about one. Also when a shipped artifact failed on an input nobody tried, or when verification so far is a happy-path smoke test.

★ 1
adriancodes
adriancodes/skills

understand-codebase

Use when the user asks to "understand this codebase", "how does this feature work in this repo?", "trace this feature through the code", or needs onboarding, an architecture explanation, or answers about unfamiliar code. Also use for read-only code-path questions before a change.

★ 1
adriancodes
adriancodes/skills

tdd

Use when writing or changing production behavior: implementing a feature, fixing a bug whose cause is already known, or altering stored, transformed, migrated, serialized, or externally transmitted data. Also use when a user says "use TDD", "test first", or "red-green-refactor", and when code is being written before a failing test. For a failure whose cause is unknown, diagnose first.

★ 1
adriancodes
adriancodes/skills

simplify-code

Use when the user asks to "simplify this code", "remove the fluff", or "clean up this over-engineered module", or wants working code that is bloated, duplicated, over-abstracted, or dependency-heavy reduced without changing behavior.

★ 1
adriancodes
adriancodes/skills

review-session

Review an agent session for evidence-backed friction and the smallest measurable remedies.

★ 1