You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Should we adopt her two one-line verification rules, and in which skills? #15657
Should we adopt her two one-line verification rules: "replay every model-found bug against the real code; if it does not occur, assume the model is wrong", and "suspect the observation method before suspecting the system"?
From the talk
Chapter 7, slides 27 and 32: formal verification; both lines come from her pstack verification skills.
Take both (immediate takeaway, menu priority P1): the first in /prototype:pressure-test or /verification:confirm, the second in /debugging:debug. The formal-verification work item already applies the first: Model the loop-lane claim protocol in TLA+ as one bounded proof of concept. Basis: judgment; both are cheap and match existing skill intent.
Alternatives
Decline with a reason in the upstream record; take only one.
Done would add
One line in each named skill, with an eval case showing it changes behavior, and a row in the upstream record. Dogfood: the eval runs in this repository.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: intent
Blocked by: none
Understood: you ask whether to add two one-line verification rules to named skills, with an eval case each and a row in the upstream record. The issue leaves the decision, and the first rule's target skill, open. It lists decline or take-one as alternatives. No duplicate or merged fix found; #15648 is related and already applies the first rule.
Adopt both rules? RECOMMENDED: yes, take both. Basis: the issue's own judgment that they are cheap and match existing skill intent.
Which skill gets rule one: /prototype:pressure-test or /verification:confirm? RECOMMENDED: /verification:confirm, since replaying a finding against real code is confirmation. Basis: judgment; the issue names both and picks neither.
To answer, post a comment that starts with this line:
Resolved: take both rules, each in the one place that owns it.
From the talk. Chapter 7, slides 27 and 32 (formal verification and statecharts; transcript 1:12:08 to 1:12:39 and 1:14:05). The two lines themselves are from her plugin, not the talk.
Rule
Her source (cursor/plugins, MIT)
Where it goes
Replay every bug a model finds against the real code; "If a bug does not occur, think that the model is wrong until you show that it is not"
pstack/skills/statechart/SKILL.md:82; the same replay is step 5 of maintain-formal-verification-skill
The formal-verification plugin: the chart skill's hand-off (slice 1) and the refresh action (slice 3). It applies only to models.
"When verification fails, suspect the observation method before suspecting the system"
Why confirm and not debug. The second rule is about reading a failed verification, and confirm is the skill that judges one. Stating it in /debugging:debug as well would put one rule in two places.
Owner, 2026-11-12: "Yes, let's go with recommendations there."
Basis: a search of this marketplace's plugins for the second rule found no equivalent (run by a comparison agent on 2026-11-12, not repeated by hand); the first rule's lines were read by that agent and relayed.
Activity
github-actions commentedon Nov 12, 2026
Size: Small
Complexity: Low
Uncertainty: Known
Flags: intent
Blocked by: none
Understood: you ask whether to add two one-line verification rules to named skills, with an eval case each and a row in the upstream record. The issue leaves the decision, and the first rule's target skill, open. It lists decline or take-one as alternatives. No duplicate or merged fix found; #15648 is related and already applies the first rule.
/prototype:pressure-testor/verification:confirm? RECOMMENDED:/verification:confirm, since replaying a finding against real code is confirmation. Basis: judgment; the issue names both and picks neither.To answer, post a comment that starts with this line:
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 12, 2026
The triage verdict left this issue at
needs-owner-decision:Reason:
intentkyle-sexton commentedon Nov 13, 2026
Resolved: take both rules, each in the one place that owns it.
From the talk. Chapter 7, slides 27 and 32 (formal verification and statecharts; transcript 1:12:08 to 1:12:39 and 1:14:05). The two lines themselves are from her plugin, not the talk.
pstack/skills/statechart/SKILL.md:82; the same replay is step 5 ofmaintain-formal-verification-skillpstack/skills/principle-prove-it-works/SKILL.md:16/verification:confirm, once, with one eval case: Suspect the observation method first when a verification fails in verification:confirmWhy confirm and not debug. The second rule is about reading a failed verification, and confirm is the skill that judges one. Stating it in
/debugging:debugas well would put one rule in two places.Owner, 2026-11-12: "Yes, let's go with recommendations there."
Basis: a search of this marketplace's plugins for the second rule found no equivalent (run by a comparison agent on 2026-11-12, not repeated by hand); the first rule's lines were read by that agent and relayed.
kyle-sexton commentedon Nov 13, 2026
Resolved; see the resolution comment.