tasks ready 1

.specify/memory/constitution.md

@@ -67,11 +67,12 @@ All generated contracts (specs, code, tests) MUST be optimized for the attention
 ## Development Workflow
 
 ```text
-/speckit.specify → /speckit.clarify → /speckit.plan → /speckit.tasks → /speckit.implement
+/speckit.specify → /speckit.clarify → /speckit.ux → /speckit.plan → /speckit.tasks → /speckit.implement
 ```
 
 **Rules:**
 - No phase is skipped when `[NEEDS CLARIFICATION]` markers remain
+- `/speckit.ux` produces UX contracts AND generates Screen Model `.svelte.ts` files — these are the design contract for `/speckit.plan`
 - Contract mutation: preview → apply, never immediate apply
 - All feature artifacts in `specs/<feature>/`, never in `.kilo/` or `.ai/`
 

.specify/templates/plan-template.md

@@ -44,8 +44,17 @@ specs/[###-feature]/
 ├── research.md          # Phase 0 output (/speckit.plan command)
 ├── data-model.md        # Phase 1 output (/speckit.plan command)
 ├── quickstart.md        # Phase 1 output (/speckit.plan command)
+├── traceability.md      # Phase 1 output — RTM: Story → Model → API → Task → Test
 ├── contracts/           # Phase 1 output (/speckit.plan command)
-└── tasks.md             # Phase 2 output (/speckit.tasks command - NOT created by /speckit.plan)
+│   ├── modules.md       # Module & function contracts
+│   └── ux/              # UX contracts (if /speckit.ux was run)
+│       ├── alternatives.md  # Design space explored
+│       ├── decisions.md     # Final UX choices
+│       ├── screen-models.md # Model inventory
+│       ├── api-ux.md        # API interaction shapes
+│       ├── <screen>-ux.md   # Per-screen UX contracts
+│       └── design-tokens.md # Applied tokens & reuse
+└── tasks.md             # Phase 2 output (/speckit.tasks command)
 ```
 
 ### Source Code (repository root)

.specify/templates/tasks-template.md

@@ -68,6 +68,8 @@ Examples of foundational tasks (adjust based on your project):
 - [ ] T007 Create base models/entities that all stories depend on
 - [ ] T008 Configure error handling and logging infrastructure
 - [ ] T009 Setup environment configuration management
+- [ ] T00A [P] Materialize canonical fixtures from specs/<feature>/fixtures/api/ into backend/tests/fixtures/
+- [ ] T00B [P] Materialize canonical fixtures from specs/<feature>/fixtures/model/ into frontend/src/lib/models/__fixtures__/
 
 **Checkpoint**: Foundation ready - user story implementation can now begin in parallel
 
@@ -279,3 +281,5 @@ With multiple developers:
 - **Screen Models use `.svelte.ts` extension** — create them in `frontend/src/lib/models/`
 - **Two-layer testing: L1 (model invariants, no render, ~27ms) comes BEFORE L2 (UX contracts, with render)**
 - **Backend tasks are pinned to `backend/src/`, frontend tasks to `frontend/src/`** — cross-stack tasks reference both
+- **Fixture materialization tasks come BEFORE test-writing tasks** — tests import fixtures, not generate data
+- **Canonical fixtures live in `specs/<feature>/fixtures/`** — materialize to `tests/` via tasks, never edit canonical source in test directories