Scope some workflow steps to individual features

.claude/commands/formspec.check.8.md

@@ -17,8 +17,8 @@ Read every artifact that exists (skip gracefully if some don't exist yet):
 - All feature design docs: Glob for `spec/features/*/design.md`
 - `spec/formal/System.tla` and `spec/formal/System.cfg`
 - `spec/formal/traceability.md`
-- `spec/plan.md`
-- `spec/tasks.md`
+- All feature plans: Glob for `spec/features/*/plan.md`
+- All feature task lists: Glob for `spec/features/*/tasks.md`
 - `spec/verification/matrix.md`
 
 Also scan:
@@ -35,13 +35,13 @@ Perform each of these checks and record findings:
 - No TLA+ properties exist in System.tla without a corresponding entry in traceability.md
 - No orphaned entries in traceability.md (property exists in table but not in System.tla)
 
-**TLA+ <-> Implementation (if plan.md and matrix.md exist)**:
-- Every TLA+ property has at least one implementation-level verification method in plan.md
+**TLA+ <-> Implementation (if feature plans and matrix.md exist)**:
+- Every TLA+ property has at least one implementation-level verification method in a feature plan
 - Every verification method has been executed and recorded in matrix.md
 - No FAIL or PENDING entries in matrix.md that lack explanation
-- Verification matrix entries correspond to completed milestones, not individual tasks — flag any property marked PASS whose milestone tasks are not all complete
+- Verification matrix entries correspond to completed milestones, not individual tasks — flag any property marked PASS whose milestone tasks (in the relevant feature's tasks.md) are not all complete
 
-**Design <-> Implementation (if tasks.md exists)**:
+**Design <-> Implementation (if feature task lists exist)**:
 - Every user story (US-N) from every feature design doc is covered by at least one task
 - Every task is marked complete or has a documented reason for incompleteness
 - No tasks reference nonexistent user stories or properties
@@ -65,7 +65,7 @@ Perform each of these checks and record findings:
 - No implementation code files that don't trace back to any task (heuristic — flag files that seem substantial but aren't referenced)
 
 **Tests <-> Specification (if test files exist)**:
-- Every TLA+ property with a runtime verification method (from plan.md's Verification Strategy) has corresponding test cases in the codebase
+- Every TLA+ property with a runtime verification method (from the feature's plan.md Verification Strategy) has corresponding test cases in the codebase
 - Test names or comments reference the TLA+ property or design requirement they verify
 - No test files exist that don't trace back to any task or verification method (heuristic — flag test files that seem unrelated to the spec)
 - Property-based tests (if specified in the plan) exist and cover the properties they claim to verify
@@ -86,7 +86,7 @@ Perform each of these checks and record findings:
 
 ### 3. Run verification
 
-If `spec/hooks/run-checks` exists and is executable, delegate all verification (TLC and language-specific tools) to it (see `/formspec.init` for the hook interface). Build the request from `spec/formal/traceability.md` (TLA+ properties), `spec/plan.md` (verification methods), and detected source files (language-specific checks). The external system runs all checks independently and returns results.
+If `spec/hooks/run-checks` exists and is executable, delegate all verification (TLC and language-specific tools) to it (see `/formspec.init` for the hook interface). Build the request from `spec/formal/traceability.md` (TLA+ properties), feature plans (verification methods), and detected source files (language-specific checks). The external system runs all checks independently and returns results.
 
 If the hook does not exist or fails, run checks locally: