codex specify

.specify/templates/spec-template.md

@@ -1,7 +1,6 @@
 # Feature Specification: [FEATURE NAME]
 
 **Feature Branch**: `[###-feature-name]`  
-**Reference UX**: `[ux_reference.md]` (See specific folder)
 **Created**: [DATE]  
 **Status**: Draft  
 **Input**: User description: "$ARGUMENTS"
@@ -114,52 +113,3 @@
 - **SC-002**: [Measurable metric, e.g., "System handles 1000 concurrent users without degradation"]
 - **SC-003**: [User satisfaction metric, e.g., "90% of users successfully complete primary task on first attempt"]
 - **SC-004**: [Business metric, e.g., "Reduce support tickets related to [X] by 50%"]
-
----
-
-## Test Data Fixtures *(recommended for CRITICAL components)*
-
-<!--
-  Define reference/fixture data for testing CRITICAL tier components.
-  This data will be used by the Tester Agent when writing unit tests.
-  Format: JSON or YAML that matches the component's data structures.
--->
-
-### Fixtures
-
-```yaml
-# Example fixture format
-fixture_name:
-  description: "Description of this test data"
-  data:
-    # JSON or YAML data structure
-```
-
-### Example: Dashboard API
-
-```yaml
-valid_dashboard:
-  description: "Valid dashboard object for API responses"
-  data:
-    id: 1
-    title: "Sales Report"
-    slug: "sales"
-    git_status:
-      branch: "main"
-      sync_status: "OK"
-    last_task:
-      task_id: "task-123"
-      status: "SUCCESS"
-
-empty_dashboards:
-  description: "Empty dashboard list response"
-  data:
-    dashboards: []
-    total: 0
-    page: 1
-
-error_not_found:
-  description: "404 error response"
-  data:
-    detail: "Dashboard not found"
-```