design-before-fixlisted
Install: claude install-skill RICK-ORPHEN/agent-discipline-skills
# Design Before Fix — read how it is meant to reach the user
## What this discipline is for
Sometimes **the symptom is real, the fix is technically correct, and the change is still
wrong.** That happens when you close the inconsistency in front of you without reading how
the feature was designed to reach the user. Locally it all adds up, so **you cannot catch it
from the inside.**
## When it triggers
If any of these is true, run this procedure before changing a single line.
- The change touches a product boundary — **who may use it, how it is billed, what they receive**
- **Credentials, permissions or connections** to an external service are involved
- You are changing distribution, publication, contracts or entitlements
- **You are about to conclude "this does not work here", "the customer does not have that",
"this cannot be used"** — the moment just before a flat assertion is the moment you have
read the design least
## Procedure
### 1. Read until you can write the intended flow in one paragraph
What does the user already have, where are they authenticated, which path executes, whose
credentials are used, what gets billed. **If you cannot write it, you are not yet qualified
to fix it.**
⚠️ Do not assume one file holds the answer. A boundary is implemented across
**entry (routing) → decision (authorization) → resolution (credentials) → execution**, and
**reading only the entry gives you the opposite conclusion.** Above all, check whether the
call is **intercept