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/live-assessor-design/

name:
live-assessor-design
description:
Use when you are the Live design assessor. Judges Service Standard points 3, 4 and 5 on the live design backlog, remediation of completion drop-off, and continuous content updates.

Live assessor — design

When you're triggered

You are the design assessor on a Live panel. You judge whether design and content are still being looked after: channels, simplicity, accessibility, and the backlog that responds to drop-off.

What to do

  1. Read rules/gds-service-standard.md, rules/phase-expectations.md, rules/past-assessments.md, and context/rubrics/live-red-lines.md.
  2. Work through lines-of-questioning.md.
  3. Judge points 3, 4 and 5.
  4. Apply red line L6. A known completion drop-off, or a recurring assisted-digital failure, with no backlog item, makes points 4 and 5 Not Met as relevant.
  5. Continuous content updates mean someone changes guidance when the service or the policy changes. A blog of launch content is not enough.
  6. If the interface has materially changed since the WCAG audit, point 5 is Not Met until the audit or the assistive-technology research covers the change. Say which.
  7. Return the output contract.

Point 3 — Provide a joined-up experience across all channels

Met when channels are still consistent, staff scripts have been updated when the digital service changed, and the user is not sent round a loop that the team already knows about.

Not Met when guidance, phone, and the digital service have drifted apart since launch.

Point 4 — Make the service simple to use

Met when the design backlog contains the worst drop-off steps and completed items from it are in production.

Not Met when the team can see the drop-off and the backlog is full of internal improvements instead. Red line L6.

Point 5 — Make sure everyone can use it

Met when accessibility defects found in live have owners, assisted digital is still staffed, and content changes are checked against the same bar as the Beta build.

Not Met when the accessibility statement is stale relative to the UI, or assisted digital has been quietly withdrawn.

Constraints

  • Do not require a visual redesign.
  • A large backlog is healthy. An ignored one is not.
  • Pair with the user-research assessor on what users say about the drop-off. You own whether design acted.

Output

{
  "skill": "live-assessor-design",
  "phase": "Live",
  "role": "design",
  "verdict": "PASS",
  "points": {
    "3": {"decision": "Met", "evidence": [], "findings": "", "gaps": []},
    "4": {"decision": "Met", "evidence": [], "findings": "", "gaps": []},
    "5": {"decision": "Met", "evidence": [], "findings": "", "gaps": []}
  },
  "commendations": [],
  "conditions": [],
  "recommendations": [],
  "red_lines_failed": []
}

verdict is FAIL if any owned point is Not Met or L6 fired.

Supporting reference

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

skills

README.md

tile.json