task-analysis

Decompose route and onboarding UX feedback into goals, tasks, and subtasks.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/jacob-balslev/skill-graph --skill task-analysis-jacob-balslev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-analysis
Source: https://github.com/jacob-balslev/skill-graph/tree/main/marketplace/skills/task-analysis
Command: npx skills add https://github.com/jacob-balslev/skill-graph --skill task-analysis-jacob-balslev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Task-analysis turns vague UX critique like “this page feels confusing” into an explicit, evidence-based decomposition of the user’s goal, top task, and sequential subtasks for a specific route or flow.

Core Features & Use Cases

  • Goal → Task → Subtask decomposition for any route/flow you need to audit, including skip paths and blocked states.
  • Top-task extraction with a primary/secondary/supporting hierarchy contract for what must appear in the first viewport.
  • Five-dimension task friction scoring (discoverability, cognitive load, effort, trust, recovery) to identify exactly where the journey breaks.

Quick Start

Use task-analysis to audit a target onboarding or route flow by naming the actor and scenario, extracting the top task and first-viewport hierarchy contract, then listing subtasks with friction scores and breakpoints.

Frequently Asked Questions about task-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn vague UX feedback into a structured task decomposition?

UX task decomposition translates subjective critique into an evidence-based structure of user goals, top tasks, and sequential subtasks. It identifies skip paths, blocked states, and breakpoints for a specific route or onboarding flow. This structure clarifies exactly where user journeys break down.

What is first viewport hierarchy and how does it support route contracts?

First viewport hierarchy establishes a primary, secondary, and supporting task contract for what must appear immediately visible to the user. It validates route contracts by ensuring the most critical top-task elements are prioritized over aesthetics in the initial screen layout.

How do I audit a multi-step wizard for dead-ends and blocked states?

Auditing a multi-step wizard involves mapping the actor and scenario, extracting the primary task hierarchy, and listing sequential subtasks. This process diagnoses dead-ends by applying friction scoring to identify exact breakpoints where users cannot recover or proceed.

Can I use this task analysis approach for onboarding flows and setup wizards?

Yes, this task analysis approach applies directly to onboarding flows, setup wizards, and multi-step processes. It validates whether the flow's explicit task structure adequately supports the user's goal through an actor/scenario identification and a verification checklist.

When should I prioritize task structure validation over visual aesthetics?

Task structure validation should take priority over aesthetics when user goal support matters most, such as during onboarding setups, route contract auditing, and first-viewport hierarchy decisions. Friction scoring reveals that visual polish cannot compensate for discoverability and recovery failures.