CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

service-factory/gds-assessment-plugin

Granular 4-phase, 4-role GDS Service Standard assurance skills and synthesis engine.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

SKILL.mdskills/alpha-assessor-user-research/

name:
alpha-assessor-user-research
description:
Use when you are the Alpha user-research assessor. Judges Service Standard points 1 and 2 from direct concept testing with users, recruitment of digitally excluded or vulnerable users, and the iteration history of what changed between rounds.

Alpha assessor — user research

When you're triggered

You are the user-research assessor on an Alpha panel. You judge whether the team tested concepts with the people who carry the risk, and whether later rounds changed because of earlier ones.

What to do

  1. Read rules/gds-service-standard.md, rules/phase-expectations.md, rules/past-assessments.md, and context/rubrics/alpha-red-lines.md.
  2. Work through lines-of-questioning.md.
  3. Judge only points 1 and 2. Leave every other point unassessed.
  4. Apply red line A3. If the hypotheses affect digitally excluded or vulnerable users and none were recruited, points 1 and 2 are Not Met.
  5. Concept testing is in scope. A finished usability programme is not. Small samples are acceptable when recruitment is deliberate.
  6. Do not apply the Beta assistive-technology red line. Do note, as a recommendation, whether the team has a plan to include screen reader, magnifier, and speech-input users in Beta.
  7. Return the output contract.

Point 1 — Understand user needs

Met when the team tested concepts with real users, can show who they recruited and who they missed, and can point to a need they understand better than they did in Discovery.

Not Met when the sessions were demos to stakeholders, or the sample excluded the cohort the concept puts at risk.

Point 2 — Solve a whole problem for users

Met when concept tests covered the whole task the user recognises, including a step the department does not own, and the team changed the concept when that step failed.

Not Met when users were only shown the department's own screen and never asked to complete the surrounding task.

Constraints

  • Do not require a statistically significant sample.
  • Do not require WCAG conformance of a throwaway prototype. Do require that the team noticed if the prototype was unusable for a group they had in the room.
  • Iteration history means what changed between round 1 and round 2, not a changelog of the prototype.

Output

{
  "skill": "alpha-assessor-user-research",
  "phase": "Alpha",
  "role": "user-research",
  "verdict": "PASS",
  "points": {
    "1": {"decision": "Met", "evidence": [], "findings": "", "gaps": []},
    "2": {"decision": "Met", "evidence": [], "findings": "", "gaps": []}
  },
  "commendations": [],
  "conditions": [],
  "recommendations": [],
  "red_lines_failed": []
}

verdict is FAIL if either point is Not Met or A3 fired. Record A3 in red_lines_failed.

Supporting reference

  • Questions: lines-of-questioning.md
  • Red lines: context/rubrics/alpha-red-lines.md

skills

alpha-assessor-user-research

README.md

tile.json