Update workflow-preset to v1.3.5

.github/workflows/community-smoke.yml

@@ -59,8 +59,8 @@ jobs:
           registry = json.loads(Path(".specify/presets/.registry").read_text(encoding="utf-8"))
           manifest_version = manifest["preset"]["version"]
           registry_version = registry["presets"]["workflow-preset"]["version"]
-          assert manifest_version == "1.3.4", manifest_version
-          assert registry_version == "1.3.4", registry_version
+          assert manifest_version == "1.3.5", manifest_version
+          assert registry_version == "1.3.5", registry_version
           assert registry_version == manifest_version
           PY
           test -f .specify/presets/workflow-preset/templates/behavior/behavior-scenarios-draft.json

.gitignore

@@ -25,6 +25,7 @@ venv/
 ENV/
 env/
 .venv
+.venv*/
 
 # IDE
 .vscode/

presets/catalog.json

@@ -29,7 +29,7 @@
     "workflow-preset": {
       "name": "Workflow Preset",
       "id": "workflow-preset",
-      "version": "1.3.4",
+      "version": "1.3.5",
       "description": "Behavior-first specification, design artifacts, and agent-native handoff orchestration",
       "author": "bigsmartben",
       "repository": "https://github.com/bigsmartben/spec-kit-workflow-preset",

presets/workflow-preset/README.md

@@ -33,6 +33,7 @@ Requirement capabilities:
 
 - Wraps `/speckit.specify` so it produces or updates `spec.md` only.
 - Wraps `/speckit.clarify` so it resolves requirement ambiguity in `spec.md` only.
+- When a Figma Evidence Packet has already been written into `spec.md`, `/speckit.clarify` clarifies Figma-derived gaps already written in `spec.md` and does not call Figma.
 - Wraps `/speckit.checklist` to add `checklists/behavior-testability.md` as a BDD readiness gate and NFR readiness gate.
 - Checks user stories, acceptance criteria, Given/When/Then readiness, roles, permissions, states, data, validation, boundary, exception, state-conflict behavior, and non-functional requirements directly from `spec.md`.
 - Requires NFR dimensions to be marked Required, Not Applicable, or Unknown in product language before planning.
@@ -123,7 +124,7 @@ Context-load controls:
 Release install:
 
 ```bash
-specify preset add workflow-preset --from https://github.com/bigsmartben/spec-kit-workflow-preset/releases/download/v1.3.4/spec-kit-workflow-preset-v1.3.4.zip
+specify preset add workflow-preset --from https://github.com/bigsmartben/spec-kit-workflow-preset/releases/download/v1.3.5/spec-kit-workflow-preset-v1.3.5.zip
 ```
 
 Local development install:
@@ -348,7 +349,7 @@ Release install smoke validation is intentionally owned by GitHub Actions, not b
 After tagging a release, validate archive installation:
 
 ```bash
-specify preset add workflow-preset --from https://github.com/bigsmartben/spec-kit-workflow-preset/releases/download/v1.3.4/spec-kit-workflow-preset-v1.3.4.zip
+specify preset add workflow-preset --from https://github.com/bigsmartben/spec-kit-workflow-preset/releases/download/v1.3.5/spec-kit-workflow-preset-v1.3.5.zip
 ```
 
 ## Source Rationale

presets/workflow-preset/commands/speckit.clarify.md

@@ -9,6 +9,27 @@ Use `spec.md` as the clarification source. Ask and record clarification only for
 
 Do not read or update behavior draft artifacts. Do not use behavior drafts as clarification inputs, and do not open a separate behavior-question channel. Product requirements stay in `spec.md`; update `spec.md` only after user-provided answers make the requirement clear.
 
+## Figma-Derived Clarification Strategy
+
+When `spec.md` was created from a Figma Evidence Packet, prioritize clarification questions for Figma-derived gaps already written in `spec.md`. Scan `spec.md` first for `Missing / Needs clarification`, `[NEEDS CLARIFICATION]`, `Inferred from structure`, and gaps about Figma-unprovided states, responsive behavior, business rules, permissions, and error handling.
+
+Do not call Figma MCP. Do not re-extract design facts, re-parse Figma links, or turn clarification into a Figma extraction step. `/speckit.specify` owns writing Figma evidence into `spec.md`; `/speckit.clarify` only selects high-impact questions from existing `spec.md` gaps and records confirmed answers.
+
+Ask at most 5 high-impact questions whose answers materially affect requirements, implementation planning, or validation readiness. Prefer questions in this order:
+
+1. Required frames, states, and breakpoints for acceptance.
+2. visual fidelity scope: pixel-perfect, design-system faithful, or functional equivalent.
+3. missing UI states such as loading, empty, error, disabled, hover, and focus.
+4. responsive behavior, scrolling, safe areas, and long-copy handling.
+5. component mapping from Figma components to existing code components.
+6. data semantics for mock copy, API-backed copy, and interface-driven values.
+7. Prototype-uncovered navigation, dialogs, recovery paths, and failure handling.
+8. acceptance evidence, visual-difference tolerance, and exception approval flow.
+
+After the user answers, write confirmed answers back into `spec.md` in the relevant Requirements, User Scenarios, Acceptance Criteria, Assumptions, Open Questions, or visual/responsive/state sections. Do not create a separate Figma clarification document.
+
+Do not generate visual restoration checklists. Clarification fills requirement gaps in `spec.md`; `/speckit.checklist` remains responsible for checking requirement text quality and readiness.
+
 {CORE_TEMPLATE}
 
 ## Clarification Reporting

presets/workflow-preset/docs/extension-governance.md

@@ -44,6 +44,10 @@ Stage ownership:
 - `/speckit.analyze`: vertical consistency checks across requirements, behavior drafts, contracts, and tasks only.
 - `/speckit.implement`: implementation handoff execution only.
 
+When a Figma Evidence Packet has already been written into `spec.md`,
+`/speckit.clarify` may clarify those requirement gaps from `spec.md`, but
+external design extraction is not a clarification responsibility.
+
 ## Structured Artifact Rules
 
 Machine-readable JSON artifacts are contracts, not prose examples. Stable