ComputerConnection/scope-check

Scope Check: $ARGUMENTS

Verify we haven't drifted from the original intent.

---

Step 1: Find the Anchor

Locate the original scope definition:

1. ORIGINAL_BRIEF.md (if NEXUS project)
2. CURRENT_STATE.yaml → original_intent field
3. First commit message or PR description
4. Initial conversation about this task
5. Ask Zach if nothing exists

The anchor is sacred. We're checking against it.

---

Step 2: Extract Boundaries

From the anchor, identify:

Original Intent

[Quote or summarize the original goal]

Explicit In-Scope

• [ ] Item 1
• [ ] Item 2
• [ ] Item 3

Explicit Out-of-Scope

• Item A
• Item B
• Item C

Implicit Boundaries

Things not stated but clearly outside the spirit:

• [inference]

---

Step 3: Audit Current Work

List everything we've done or are about to do:

| Work Item | In Scope? | Justification | |-----------|-----------|---------------| | [thing 1] | ✅ / ❌ / ⚠️ | [why] | | [thing 2] | ✅ / ❌ / ⚠️ | [why] | | [thing 3] | ✅ / ❌ / ⚠️ | [why] |

Legend:

• ✅ Clearly in scope
• ❌ Out of scope - should not do
• ⚠️ Gray area - needs Zach's call

---

Step 4: Drift Detection

Red Flags (Likely Drifting)

• [ ] Adding features not in original ask
• [ ] "Improving" adjacent code
• [ ] Refactoring for style/preference
• [ ] Adding "nice to haves"
• [ ] Scope expanded without explicit approval
• [ ] Original intent unclear or forgotten
• [ ] Working on something that wasn't asked for

Yellow Flags (Watch Carefully)

• [ ] Reasonable extension of original ask
• [ ] Prerequisite work for the actual task
• [ ] Bug fix discovered during work
• [ ] Security issue found

Green Flags (On Track)

• [ ] Work directly serves original intent
• [ ] Staying within stated boundaries
• [ ] Can trace each change to the ask

---

Step 5: Verdict

┌─────────────────────────────────────────┐
│  SCOPE CHECK: [PROJECT]                 │
├─────────────────────────────────────────┤
│  Status: ✅ ON TRACK / ⚠️ DRIFTING / ❌ OFF TRACK │
│                                         │
│  Original Intent:                       │
│  [one line summary]                     │
│                                         │
│  Current Focus:                         │
│  [what we're actually doing]            │
│                                         │
│  Alignment: [percentage or rating]      │
└─────────────────────────────────────────┘

---

Step 6: Corrective Action

If Drifting:

1. Stop current work
2. List out-of-scope items that crept in
3. Move to technical_debt or future backlog
4. Refocus on original intent
5. Resume only in-scope work

If Gray Area:

Ask Zach:

Scope Question:

Original intent: [X]
Current work includes: [Y]

Is [Y] in scope or should I defer it?

Options:
1. Yes, include it (expand scope)
2. No, defer it (stay focused)
3. It's prerequisite (do it, but minimal)

If On Track:

Continue. No action needed.

---

When to Run This

• Before starting significant new work
• When you feel scope expanding
• After getting interrupted and returning
• Before handoff to another agent
• When someone asks "why are we doing this?"
• Regularly on long-running tasks (every few hours)

---

Output

1. Show the Verdict box
2. List any drift items found
3. Recommend corrective action (if needed)
4. Confirm refocused scope before continuing