[BUG] Incorrect Inference of checkboxes in spec file

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

CC Made incorrect assumption about the purpose of checkboxes in spec file section titled '## Scope'.

Here's what CC suggested I post:
... the concrete sequence: spec file had checked boxes, I grepped the codebase, found no implementation, concluded the boxes were wrong, and only later found the skill's own drafting instructions defined "checked = in scope" rather than "checked = built." That's a specific, reproducible reasoning failure, which is more useful to the team than a general description.

In a previous paragraph it also said this:
... the general risk class is real: any time I see a UI element (a checkbox, a toggle, a status flag) and infer its meaning from how it looks rather than from what the code actually defines it to do, the same mistake is possible. It's why the verification habit matters generally, not just here.

The section title seems to have been ignored - explicitly says Scope.

What Should Happen?

I expected CC to recognise the common word with 'standard' meaning to affect its interpretation of the content rather that pattern matching on checkboxes. I think the use of checkboxes is generic enough that searching for context should be a priority well above looking for pattern-matched use for context.

Error Messages/Logs

Steps to Reproduce

Here's a spec file snippet that should have worked:
---

Scope

• [x] apps/api/ — user_consents migration + model; ToS re-consent gate endpoint
• [x] apps/rails/ — user_consents migration + model (shared-DB, Laravel owns schema)
• [x] apps/web/ — ToS step in onboarding, cookie banner, OSS Licenses screen, ToS re-consent gate
• [ ] apps/expo/ — ToS step in onboarding, OSS Licenses screen (no cookie banner — native app)
• [ ] apps/flutter/ — ToS step in onboarding, OSS Licenses screen

Expo and Flutter are out of scope for Phase 2. Mark them unchecked; add when those tracks open.

---

Here's another:
---

Scope

• [x] apps/api/ — legal_documents migration + seeder
• [x] apps/rails/ — legal_documents migration + seeder
• [x] Landing site (Laravel Blade) — /privacy and /terms static pages

---

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

I don't know. It never happened before.

Claude Code Version

2.1.159 (Claude Code)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

I actually run using the vsCode extension most of the time.
I don't know when the versions update, never checked before, however I noticed lots of similar problems started cropping up in the last week. Lots of assumptions, etc., it never used to make (or not with any sort of similar frequency). I think the question how am i doing ??? with answer "Bad" "Fine" "Good" buttons, in the extension, started being added around the same time.
Makes me wish I could go back to whatever version I was using before. (Frustration result)