normalizelisted
Install: claude install-skill xtieume/testcase
# Normalize — everyday prompt → engineering prompt
> Same requirements. Less prose. Shape an AI can execute.
## The rule
**Every line of the output traces to a phrase in the input.** No invented scope, no added
acceptance criteria, no "best practice" section the user never asked for.
Dropping a requirement fails the same way inventing one does. This is a rewrite, not a
redesign — you have no authority to decide the task is bigger or smaller than stated.
Never execute the normalized prompt. The deliverable is the text.
## Workflow
- [ ] 1. Extract — pull every requirement out of the input, verbatim-ish
- [ ] 2. Shape — group into sections, convert each to an imperative
- [ ] 3. Budget — fit the character limit
- [ ] 4. Second pass ⚠️ REQUIRED — diff output against input, both directions
- [ ] 5. Emit — one fenced block, nothing else
## 1. Extract
Read the input twice and answer, in the input's own words:
- **Target** — what file, path, URL, repo, ticket or command is this pointed at? Copy it
character-for-character. A path is not paraphrasable.
- **Goal** — what state does the user want at the end? Usually one sentence buried in the
middle of the rambling.
- **Sources of truth** — which folders, docs or systems did they name as authoritative, and
in what order? Keep any reading order they gave ("trace newest → oldest").
- **Escalation** — what did they say to do when something is unclear? (ask, mark draft,
widen the search, guess)
- **Done / output** — what a