AB product-ux-workflow
End-to-end product UX lifecycle methodology — four-stage workflow from requirements research and user scenario modeling to information architecture, low-fidelity wireframing, and developer handoff. Focuses on macro product UX: user journey maps, content hierarchy, IA, and design system alignment. Use when: planning product UX from 0 to 1, drafting user journey flows, defining PRD user scenarios, structuring information architecture, or creating low-fidelity wireframe prototypes. Keywords: 产品设计, UX流程, 用户旅程, 需求分析, 流程图, 低保真线框图, 原型规划, 体验设计, user journey, wireframe, user flow, information architecture, product UX, PRD.
End-to-end product UX lifecycle methodology — four-stage workflow from requirements research and user scenario modeling to information architecture…
As a process B 65/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice
How to improve
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 65/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 85Steps. 72 steps, 1 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2574 tokens
- medium 2 test cases, all positive: not one "should refuse" or "should ask first"
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +2Single-language instructions
- +3Description length 621: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 72 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.