spec-agent 2.0.6 → 2.0.7

package/.cursor/rules/spec-agent-assistant.mdc

@@ -29,7 +29,7 @@ When user intent is about running `spec-agent`, apply this workflow:
 
 4. Keep responses action-oriented:
    - Provide exact commands.
-   - Explain expected output paths (`output/handoff`, `output/execution`).
+   - Explain expected output paths (`output/handoff`, `output/execution`, `output/prototypes`, `output/prototype_index.json`).
    - Avoid claiming completion without command evidence.
    - Prefer invoking `spec-agent-product-dev-agent` when user asks requirement-to-development end-to-end.
 
@@ -44,3 +44,8 @@ When user intent is about running `spec-agent`, apply this workflow:
    - Frontend-only implementation by default.
    - Prioritize pages, routes, UI states, forms, interactions, and mock data.
    - Backend/API/database tasks are marked as "deferred" and not executed in current round unless user explicitly requests backend implementation.
+
+7. Prototype-aware implementation policy:
+   - If `output/prototype_index.json` exists, prioritize prototype-linked tasks.
+   - For task execution, first read `output/handoff/tasks/<TASK_ID>.md` and use "Prototype References" as primary UI evidence.
+   - Treat "Prototype Candidates" as optional references that need human confirmation.

package/.cursor/skills/spec-agent-execution-orchestrator/SKILL.md

@@ -87,6 +87,8 @@ Inspect:
 
 - `output/execution/inbox/*.md`
 - `output/execution/execution_report.json`
+- `output/prototype_index.json` (if exists)
+- `output/prototypes/*` (if exists)
 
 Return a concise batch summary:
 
@@ -94,6 +96,7 @@ Return a concise batch summary:
 - pending/running/succeeded/failed/blocked counts
 - which task to execute first
 - frontend-only kept tasks vs deferred backend tasks
+- high-confidence prototype references per task
 
 ### Step 4: Collect outcomes
 

package/.cursor/skills/spec-agent-onboarding-agent/SKILL.md

@@ -55,6 +55,12 @@ spec-agent round --workspace ./output --input ./docs --target cursor --max-paral
 
 `pipeline` manual-first; `round` auto-run when possible.
 
+If requirement docs include prototype images, verify these artifacts after `pipeline`:
+
+- `output/prototypes/*`
+- `output/prototype_index.json`
+- `output/prototype_index.md`
+
 ## Step 3: Multi-Agent Execution Bootstrap (Optional)
 
 ```bash
@@ -90,3 +96,4 @@ spec-agent execute --workspace ./output --fail T003 --error "compile failed"
 - Do not skip verification commands.
 - Use `spec-agent round` as the primary one-round action.
 - `handoff` / `round` can be auto-run; `pipeline` remains manual-first.
+- When `prototype_index.json` exists, remind user to use task-level prototype references in `output/handoff/tasks/*.md`.

package/.cursor/skills/spec-agent-product-dev-agent/SKILL.md

@@ -84,9 +84,17 @@ Read:
 
 - `output/execution/inbox/*.md`
 - `output/orchestrator_context.json`
+- `output/prototype_index.json` (if exists)
+- `output/prototypes/*` (if exists)
 
 Then guide user to execute current inbox tasks in coding sessions, with frontend-first filtering.
 
+Prototype-first task guidance:
+
+- In each `output/handoff/tasks/<TASK_ID>.md`, use `Prototype References` as the main UI evidence.
+- `Prototype Candidates (medium/low)` should be treated as optional, require human confirmation.
+- If a task has no high-confidence prototype, ask for manual prototype confirmation before heavy UI coding.
+
 Frontend-first task filter:
 
 - Keep: 页面、路由、组件、表单、校验、状态管理、交互细节、UI 可用性。