agents-united 0.5.0

package/registry/workflows/workflow-ux-strategy--benchmark.md

@@ -0,0 +1,60 @@
+---
+name: "Competitive UX Benchmarking & Heuristic Evaluation"
+description: "Workflow for evaluating competitor products, conducting Nielsen-Molich heuristic audits, and identifying UX opportunities."
+bundle: "product-design"
+estimatedDuration: "45-75m"
+---
+
+# Workflow: Competitive UX Benchmarking & Heuristic Evaluation
+
+## Overview & Scope
+The UX Benchmark workflow provides a structured approach for auditing competitor interfaces. It applies Nielsen-Molich 10 Usability Heuristics to score UX quality and uncover competitive advantages.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Start Workflow]) --> P1[Phase 1: Context & Reconnaissance]
+    P1 --> InputCheck{"Prerequisites & Tools Valid?"}
+    InputCheck -->|No| Abort1[Abort & Request Inputs]
+    InputCheck -->|Yes| P2[Phase 2: Execution & Orchestration]
+    P2 --> Gate1{"Verification Gate: Automated Checks Pass?"}
+    Gate1 -->|Fail| Rollback[Execute Automated Rollback Protocol]
+    Rollback --> P2
+    Gate1 -->|Pass| P3[Phase 3: Verification & Closure]
+    P3 --> Gate2{"Final Acceptance Gate Passed?"}
+    Gate2 -->|Fail| P3Fix[Remediate Documentation / Artifacts]
+    P3Fix --> P3
+    Gate2 -->|Pass| Done([Workflow Complete & Logged])
+```
+
+## Required Tool Inputs & Context
+- Target competitor product links / screenshots
+- Nielsen 10 Usability Heuristics checklist
+- UX evaluation scoring template
+
+## Phase 1: Context & Reconnaissance
+- Select 3-5 primary competitor products for benchmarking.
+- Define core user flows for evaluation (e.g. Onboarding, Search & Filter, Checkout/Conversion).
+- Establish scoring criteria (1-5 severity scale for heuristic violations).
+
+## Phase 2: Execution & Orchestration
+- Walk through selected user flows on competitor products, taking structured screenshots.
+- Score each flow across Nielsen's 10 Heuristics (Visibility of system status, User control, Consistency, Error prevention, etc.).
+- Identify UX friction patterns, best practices, and market differentiation opportunities.
+
+## Phase 3: Verification & Closure
+- Synthesize audit findings into a Competitive UX Benchmark Matrix.
+- Highlight top UX opportunities and design recommendations.
+- Publish executive UX Benchmark presentation report.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Tool inputs verified & environment ready | `node dist/cli.js doctor` | Doctor health check succeeds with 0 errors |
+| Phase 2 -> Phase 3 | Execution steps complete | `node dist/cli.js doctor` | Doctor health check confirms benchmark report artifact structure |
+| Phase 3 -> Completion | Verification complete & artifacts signed off | `npm test` | Benchmark score aggregation script runs cleanly |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: All 10 usability heuristics evaluated for each competitor product flow.
+- **Validation Checkpoint 2**: Actionable recommendations backed by documented screenshot evidence.
+- **Automated Rollback Protocol**: Re-evaluate benchmark scores if inter-rater discrepancy between evaluators exceeds 1.5 points.

package/registry/workflows/workflow-ux-strategy--frame-problem.md

@@ -0,0 +1,60 @@
+---
+name: "Problem Framing & User Intent Alignment"
+description: "Workflow for defining core user problem statements, Jobs-to-be-Done (JTBD), success metrics, and project constraints."
+bundle: "product-design"
+estimatedDuration: "30-50m"
+---
+
+# Workflow: Problem Framing & User Intent Alignment
+
+## Overview & Scope
+This workflow aligns product initiatives with genuine user needs. It frames problem statements, constructs Jobs-to-be-Done (JTBD) frameworks, and defines measurable UX success metrics.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Start Workflow]) --> P1[Phase 1: Context & Reconnaissance]
+    P1 --> InputCheck{"Prerequisites & Tools Valid?"}
+    InputCheck -->|No| Abort1[Abort & Request Inputs]
+    InputCheck -->|Yes| P2[Phase 2: Execution & Orchestration]
+    P2 --> Gate1{"Verification Gate: Automated Checks Pass?"}
+    Gate1 -->|Fail| Rollback[Execute Automated Rollback Protocol]
+    Rollback --> P2
+    Gate1 -->|Pass| P3[Phase 3: Verification & Closure]
+    P3 --> Gate2{"Final Acceptance Gate Passed?"}
+    Gate2 -->|Fail| P3Fix[Remediate Documentation / Artifacts]
+    P3Fix --> P3
+    Gate2 -->|Pass| Done([Workflow Complete & Logged])
+```
+
+## Required Tool Inputs & Context
+- User research data, interview notes, or support ticket trends
+- Business goals and strategic objectives
+- Problem framing canvas template
+
+## Phase 1: Context & Reconnaissance
+- Analyze incoming user feedback, support logs, and analytics data.
+- Identify root user pain points vs surface-level feature requests.
+- Define target user persona profiles and context of use.
+
+## Phase 2: Execution & Orchestration
+- Craft core Problem Statement using standard format: "User [X] needs [Y] because [Z]".
+- Develop Jobs-to-be-Done (JTBD) statements: "When [situation], I want to [motivation], so that [outcome]".
+- Formulate "How Might We" (HMW) opportunity prompts for solution generation.
+
+## Phase 3: Verification & Closure
+- Define quantitative UX success metrics (Task Completion Time, Error Rate, System Usability Scale).
+- Validate problem framing canvas with key stakeholders.
+- Publish Problem Framing Canvas artifact.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Tool inputs verified & environment ready | `node dist/cli.js doctor` | Doctor health check succeeds with 0 errors |
+| Phase 2 -> Phase 3 | Execution steps complete | `node dist/cli.js doctor` | Doctor health check confirms problem framing document schema |
+| Phase 3 -> Completion | Verification complete & artifacts signed off | `npm test` | Validation test suite confirms presence of metrics and JTBD fields |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: Problem statement focused on user pain points rather than pre-conceived solution implementations.
+- **Validation Checkpoint 2**: Measurable target metrics explicitly defined for problem validation.
+- **Automated Rollback Protocol**: Refine problem framing scope if statement is determined to be overly broad or solution-biased.

package/registry/workflows/workflow-ux-strategy--strategize.md

@@ -0,0 +1,60 @@
+---
+name: "Comprehensive UX Strategy Roadmap"
+description: "Strategic workflow for synthesizing research, business goals, and technical feasibility into an actionable multi-horizon UX vision."
+bundle: "product-design"
+estimatedDuration: "60-90m"
+---
+
+# Workflow: Comprehensive UX Strategy Roadmap
+
+## Overview & Scope
+The UX Strategy workflow connects user experience vision with product execution. It maps UX initiatives across strategic horizons (Horizon 1 immediate, Horizon 2 next, Horizon 3 future) and aligns stakeholders.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Start Workflow]) --> P1[Phase 1: Context & Reconnaissance]
+    P1 --> InputCheck{"Prerequisites & Tools Valid?"}
+    InputCheck -->|No| Abort1[Abort & Request Inputs]
+    InputCheck -->|Yes| P2[Phase 2: Execution & Orchestration]
+    P2 --> Gate1{"Verification Gate: Automated Checks Pass?"}
+    Gate1 -->|Fail| Rollback[Execute Automated Rollback Protocol]
+    Rollback --> P2
+    Gate1 -->|Pass| P3[Phase 3: Verification & Closure]
+    P3 --> Gate2{"Final Acceptance Gate Passed?"}
+    Gate2 -->|Fail| P3Fix[Remediate Documentation / Artifacts]
+    P3Fix --> P3
+    Gate2 -->|Pass| Done([Workflow Complete & Logged])
+```
+
+## Required Tool Inputs & Context
+- Problem framing canvas and competitive benchmark reports
+- Business product roadmap and resource constraints
+- Technical architecture constraints
+
+## Phase 1: Context & Reconnaissance
+- Gather inputs from problem framing, competitive benchmarking, and technical constraints.
+- Identify core experience principles that will guide design decisions across all features.
+- Audit current user experience debt and friction points.
+
+## Phase 2: Execution & Orchestration
+- Map UX initiatives across 3 Strategic Horizons: H1 (Core optimization), H2 (New capabilities), H3 (Transformational experience).
+- Construct feature prioritization matrix (Impact vs Effort grid).
+- Define experience metrics and key performance indicators (KPIs) for each horizon.
+
+## Phase 3: Verification & Closure
+- Validate roadmap feasibility with engineering leads and business leadership.
+- Document UX Strategy Roadmap artifact with milestones and dependencies.
+- Publish executive UX Strategy Summary.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Tool inputs verified & environment ready | `node dist/cli.js doctor` | Doctor health check succeeds with 0 errors |
+| Phase 2 -> Phase 3 | Execution steps complete | `node dist/cli.js doctor` | Doctor health check validates UX strategy document structure |
+| Phase 3 -> Completion | Verification complete & artifacts signed off | `npm run build` | Build pipeline confirms documentation artifacts compile cleanly |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: UX strategy aligns directly with documented business goals and user needs.
+- **Validation Checkpoint 2**: Technical feasibility verified with engineering leads for Horizon 1 items.
+- **Automated Rollback Protocol**: Adjust strategic horizon assignments if technical feasibility checks fail.