premise-checklisted
Install: claude install-skill SeanoChang/seanock
# premise-check
An agent builds in hours what once took weeks, so a wrong idea no longer fails
at the build. It fails later, after the design, the review and the tests were
spent on it. The cheap moment to catch it is before the design starts.
An idea usually arrives as a solution. Some of its parts answer a real need.
Other parts came along because the user liked them in another tool. This
skill separates the two, with proof for each, in the words the design will
use afterwards: P0, P1, and left out on purpose.
## Input
- **The idea,** in the user's own words.
- **The source:** the text that says what is wanted. An assignment, a ticket,
a spec, the user's notes or earlier messages. Read all of it first.
Ask no questions. Where you must guess, guess, and mark it as a guess.
## Output
Five parts, in this order, under these headings with their numbers. Part 3
is left out when it is empty.
### 1. Parts
Split the idea into three to seven parts, each one a thing that would be
built. Trace every part to where it comes from. A part has one source: when
half of it is asked and half is borrowed, split it in two.
| Part | Comes from | Proof |
| --- | --- | --- |
| Comes from | Meaning | Proof to give |
| --- | --- | --- |
| `asked` | The source asks for it | The quote, and where it is |
| `seen` | A record shows the need: a log, a metric, an incident, a benchmark | The record |
| `wanted` | The user wants it, and nothing records a need | The user's words |
| `borrowed` | I