prompt-improver

# Prompt Improver Optimize code-related prompts for clarity, investigation-first thinking, and verification. ## Input ``` $ARGUMENTS ``` --- ## Step 1: Analyze the Prompt Evaluate the input prompt across these dimensions: | Dimension | What to check | |-----------|---------------| | Task Clarity | Is the task type clear? (implement, fix, refactor, review, test) Are boundaries defined? | | Investigation | Does it specify reading/understanding before acting? | | Verification | Are there appropriate checks? (run tests, build, lint) | | Context Anchoring | Does it reference specific files, functions, or patterns? | | Action Specificity | Is the desired outcome explicit? Quality expectations stated? | | Scope Control | Is it appropriately scoped? Clear stopping points? | Identify which dimensions are weak or missing in the input prompt. ### Gates (sequenced) Complete in order; do not skip steps. 1. **Audit gate (end of Step 1):** **Pass when** the forthcoming Analysis names the task type and either lists each weak or missing dimension from the table or explicitly states all dimensions are adequate, with a brief reason for any dimension you treat as already sufficient. 2. **Transform gate (Step 2):** **Pass when** every improvement you will list under "Improvements Applied" maps to a gap from the audit (or to deliberate strengthening when the prompt was already adequate). 3. **Output gate (Step 3):** **Pass when** the Optimized Prompt block appears only after Gates 1–2 p...