spectre-ux

ux

Turn requirements into a behavioral spec — what users see/do and the system response, not visual taste. Align flows, then write ux.md.

Inputs

• $ARGUMENTS — explicit feature name/root or descendant requirements artifact.
• Requirements — first present, read fully:
  1. {OUT_DIR}/concepts/scope.md (canonical, preferred)
  2. {OUT_DIR}/specs/prd.md
  3. {OUT_DIR}/task_summary.md
• If none exist → ask for scope context or recommend $spectre:spectre-scope first; do not invent scope.

Working Set (late-bound — read at run-time, never inline)

• Reuse a managed FEATURE_ROOT only when explicit/current-thread evidence ties it to this work (physical directory wins; never branch/recency/lifecycle/scans); distinct work ignores ambient roots. Otherwise, including on collision, standalone MUST first load and follow Skill(spectre-feature-root) through DONE; orchestrated calls escalate. Keep writes beneath it and pass it unchanged.
• Repair stale feature/root metadata in artifacts this workflow touches.
• OUT_DIR = FEATURE_ROOT.
• Existing UI: one Stage-1 @spectre_patterns dispatch for similar screens/tokens — ≤~2K in-thread, no files.

Method / guardrails

Stage 1 — Flow discovery & alignment (align before specifying).

• Identify user segments: first-time/returning, anon/signed-in, free/paid, role-based.
• Identify goals, entry points, and completion states.
• Narrate each flow: Goal · Entry · User sees → User does → System responds · branches · success · Questions; call out segment divergence.
• Present a take and ask for pushback. Every initial or feedback-revised flow presentation ends with the compact handoff table:

Handoff	Details
🧭 Current phase	Flow approval.
📦 What was just done	Initial or revised flows.
▶️ Proposed next step	Render resolved action.

• CONTINUATION: Prototype when interaction, layout, visual validation, or stakeholder review materially matters; otherwise Plan when Scope + flows suffice. Render $spectre:spectre-prototype {FEATURE_ROOT} FROM_UX=true or $spectre:spectre-plan {FEATURE_ROOT}; at most one explicit conditional alternative.
• Flows approved: complete {OUT_DIR}/ux.md, then Prototype or Plan with resolved values.
• GATE: Never write {OUT_DIR}/ux.md before explicit flow approval + selected continuation. Feedback without approval → revise and re-present. Ambiguous approval or missing route authority → ask only the unresolved choice.