hse-agent-public

Plugin hse-agent-public in CD-UX/hse-agent. Commands read from the repo's manifest — 13 days ago.

Skills (22)

• backlog-story-origination-development

  Originate, refine, split, and communicate delivery-ready Agile or Azure DevOps backlog stories with human-centered rationale, implementation notes, and Gherkin acceptance criteria. Use after or alongside requirements definition when the requested output is backlog work items.

• bdx-behavior-driven-experience

  Apply BDX to support discovery and inquiry, investigate adoption and interaction concerns, and identify and prioritize evidence-informed improvements to systems and human-computer interactions.

• data-availability-feasibility

  Assess data availability, quality, semantic definitions, technical feasibility, gaps, risks, and MVP impact for product experiences.

• design-system-context

  Apply a practitioner-supplied design system and delivery conventions when defining prototype or UI implementation guidance.

• domain-context-adaptation

  Adapt analysis to a practitioner-supplied domain profile when industry, roles, operating conditions, terminology, or specialist constraints affect the work.

• executive-team-narrative

  Create leadership-ready narratives, strategic summaries, decision framing, status updates, and team alignment communications.

• heuristic-evaluation-usability-review

  Review an existing interface, prototype, dashboard, or workflow against usability heuristics; identify and severity-rank concrete interaction and comprehension issues. Use for heuristic evaluation rather than broad workload, safety, or cognitive-theory analysis.

• human-ai-interaction-design

  Design human-AI interaction models with roles, review points, confidence, uncertainty, overrides, escalation, governance, and validation.

• human-centered-product-strategy

  Frame product opportunity, user and business value, outcomes, prioritization, MVP scope, principles, tradeoffs, assumptions, and roadmap direction. Use when the primary need is product direction rather than an end-to-end discovery engagement or blueprint artifact.

• human-centered-systems-discovery-prototyping

  Guide a broad discovery-to-prototype engagement spanning human systems, product strategy, workflows, requirements, prototype direction, validation, and delivery implications. Use when the request crosses several phases rather than asking for one specialized artifact.

• human-factors-review

  Evaluate a product or operational system when workload, error risk, safety, environment, accessibility, trust, recovery, or human performance is central. Use for contextual human-factors analysis rather than a checklist-style interface heuristic review.

• human-system-decision-modeling

  Model human-system decisions, inputs, thresholds, uncertainty, accountability, escalation, feedback loops, and decision-support needs.

• human-systems-framing

  Frame complex systems around users, roles, workflows, tasks, decisions, information needs, constraints, outcomes, and human-system boundaries.

• information-design-decision-support

  Design and critique dashboards, KPI displays, status views, information hierarchy, alerts, and decision-support experiences.

• product-experience-blueprinting

  Create a Product Experience Blueprint that links users, workflows, value, MVP scope, information needs, risks, assumptions, and validation. Use when the requested outcome is the integrated blueprint artifact.

• product-lifecycle-progress-map

  Create and update a Product Lifecycle Progress Map for stakeholder and executive communication, linking lifecycle progress to evidence, ownership, risks and next decisions. Use for living project overviews and lifecycle status reporting, including requests loosely called a project charter; distingui

• prototype-direction

  Define prototype scope, screens, flows, interaction model, assumptions, fidelity, validation focus, and product decisions to inform.

• requirements-definition

  Translate product intent, research, workflow evidence, and constraints into structured product, UX, data, and acceptance requirements. Use when defining what the solution must do; use backlog-story development for delivery-ready Agile or ADO work items.

• ux-principles-cognitive-laws-review

  Explain or review a design through selected cognitive and UX principles involving attention, perception, memory, choice, effort, hierarchy, and workload. Use when theoretical reasoning will clarify a design decision, not for a general heuristic audit.

• ux-research-synthesis

  Synthesize research notes, interviews, observations, survey findings, and discovery inputs into themes, needs, insights, and opportunities.

• validation-planning

  Plan validation for usability, comprehension, workflow fit, trust, decision quality, adoption, product value, and implementation risk.

• workflow-task-analysis

  Analyze workflows, tasks, roles, handoffs, decisions, friction, cognitive load, failure modes, and improvement opportunities.

Similar plugins