Skip to content

Instantly share code, notes, and snippets.

@iamhenry
Created August 21, 2026 22:37
Show Gist options
  • Select an option

  • Save iamhenry/b5d3b5dcb63c32d732b4de68d84b57dd to your computer and use it in GitHub Desktop.

Select an option

Save iamhenry/b5d3b5dcb63c32d732b4de68d84b57dd to your computer and use it in GitHub Desktop.
ISA Mac Keyboard Shortcut
### Problem
[Describe what is wrong or missing, who or what it affects, and why resolving it matters.]

### Goal
[State the smallest exact, measurable outcome that will count as complete.]

### Current State
[Describe how it works today. Include direct baseline evidence such as observed behavior, commands, screenshots, logs, or file references.]

### Ideal State
[Describe what should be true or what the user should experience when the work is complete. Do not describe implementation steps.]

### Boundaries
[Define what is included, excluded, constrained, or dependent. Identify anything that must not change.]

### Success Criteria

#### C1 — [State one atomic, observable, binary claim about the completed state.]
- Probe: [Specify the exact command, test, file check, query, or browser assertion that directly verifies this claim.]
- Expected: [State the precise output, behavior, value, or threshold required to pass.]
- Falsifier: [State the specific observation that would prove the claim false.]
- Result: [Record PASS, FAIL, or BLOCKED only after executing the probe.]
- Evidence: [Record fresh observed output, screenshot, link, or file reference. Include the tested revision or environment when relevant.]

[Repeat this block for each additional criterion.]

### Deliverable
[Specify exactly what the agent must create, modify, or return, including the expected format or location.]

### Completion Gate
[Declare the work complete only when every criterion has fresh PASS evidence produced by its declared probe. Do not infer completion from implementation, file existence, or unchecked assumptions.]

### Escalation
[State when the agent must stop and ask instead of guessing—for example: ambiguous intent, missing access, unavailable dependencies, an unverifiable criterion, or a required change outside the stated boundaries.]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment