Libero
The free defender behind the line. After the build, read what got through and
clear it. Run this on finished work before calling it done.
Interrogate before you edit
- State the goal in one line, from the request or the plan, not from the
code. If the goal cannot be stated, stop and ask; nothing below works
without it.
- List what the work added or changed: each file, abstraction, flag,
dependency, configuration, and test.
- For each item, name the assumption that justifies it and the evidence for
that assumption. "Might be needed later", "seemed cleaner", and "the
framework usually wants this" are not evidence.
- Sort the items: delete when the goal does not need it, simplify when a
smaller form meets the goal, keep when it is needed as is. Optimize only
what a measurement shows is too slow. Automate only what will run again.
- Report the sorted list, with the assumption and evidence beside each item,
before changing anything.
Then change it, in that order
Delete first. Simplify what remains. Optimize only against a measurement.
Automate last. Take a rung only when the one above it cannot meet the goal.
Rerun the repository's relevant tests, linters, type checks, and builds after
the edits. A deletion that breaks the goal is reverted, not patched around.
The floor
Never cut validation at a trust boundary, error handling that prevents data
loss, security, accessibility, or a documented repository invariant, even when
the goal as stated does not mention them. The repository's own instruction
files name its invariants; read them before sorting. When an item looks
unnecessary but sits on one of these, keep it and say why.
Scope and authority
Invocation authorizes edits to the work just built, within the user's scope.
It never authorizes a commit, push, publication, deployment, or external
message. Inside a QStack execution loop, the implementation ladder and the
adversarial reviewer already cover this ground; use this skill on work outside
a loop, or on a finished branch before opening a pull request.
1---2name: qstack-libero3description: Catch the code that got built because it seemed useful rather than because the goal required it. Restate the goal, test each assumption against evidence, then remove, simplify, optimize, or automate in that order and never further than the goal needs. Does not cut validation, error handling that prevents data loss, security, or a repository invariant. Use as /qstack-libero after a task or feature is built, or when asked what can be deleted or simplified.4license: MIT5---67# Libero89The free defender behind the line. After the build, read what got through and10clear it. Run this on finished work before calling it done.1112## Interrogate before you edit13141. State the goal in one line, from the request or the plan, not from the15 code. If the goal cannot be stated, stop and ask; nothing below works16 without it.172. List what the work added or changed: each file, abstraction, flag,18 dependency, configuration, and test.193. For each item, name the assumption that justifies it and the evidence for20 that assumption. "Might be needed later", "seemed cleaner", and "the21 framework usually wants this" are not evidence.224. Sort the items: delete when the goal does not need it, simplify when a23 smaller form meets the goal, keep when it is needed as is. Optimize only24 what a measurement shows is too slow. Automate only what will run again.255. Report the sorted list, with the assumption and evidence beside each item,26 before changing anything.2728## Then change it, in that order2930Delete first. Simplify what remains. Optimize only against a measurement.31Automate last. Take a rung only when the one above it cannot meet the goal.32Rerun the repository's relevant tests, linters, type checks, and builds after33the edits. A deletion that breaks the goal is reverted, not patched around.3435## The floor3637Never cut validation at a trust boundary, error handling that prevents data38loss, security, accessibility, or a documented repository invariant, even when39the goal as stated does not mention them. The repository's own instruction40files name its invariants; read them before sorting. When an item looks41unnecessary but sits on one of these, keep it and say why.4243## Scope and authority4445Invocation authorizes edits to the work just built, within the user's scope.46It never authorizes a commit, push, publication, deployment, or external47message. Inside a QStack execution loop, the implementation ladder and the48adversarial reviewer already cover this ground; use this skill on work outside49a loop, or on a finished branch before opening a pull request.
hani-q