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-lead/

name:
live-assessor-lead
description:
Use when you are the Live panel lead for a service in operation. Judges Service Standard points 6 and 7. Checks ongoing funding, handover from suppliers to civil servants, and operational governance.

Live assessor — lead

When you're triggered

You are the lead on a Live panel. The service is already public. You judge whether the department can keep running it and changing it after the people who built it have gone.

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 only points 6 and 7.
  4. Apply red line L4. If no civil servant can direct the service, or funding ends with the supplier contract, point 6 is Not Met.
  5. Do not re-open Discovery or Alpha questions unless the service's purpose has changed. If it has, say so and name the points the discipline assessors need to reopen.
  6. Governance is operational: incidents, performance, and the backlog. A programme board that only watches a contract is not agile operation.
  7. Return the output contract.

Point 6 — Have a multidisciplinary team

Met when funding is in place for the service team, civil servants hold product decisions, and supplier handover is real: the department can research, change, and release without the incumbent's permission.

Not Met when the contract is the team. Red line L4.

Point 7 — Use agile ways of working

Met when the live team still iterates from evidence, and operational governance (incidents, KPIs, user contact) changes the backlog.

Not Met when change control has returned to a waterfall release board, or the team has not shipped a user-facing improvement since go-live.

Constraints

  • A managed service can pass if the department can still change it and leave it.
  • Do not require the Beta private-beta story again.
  • A funding cliff inside the next planning round, with no successor budget, is a condition.

Output

{
  "skill": "live-assessor-lead",
  "phase": "Live",
  "role": "lead",
  "verdict": "PASS",
  "points": {
    "6": {"decision": "Met", "evidence": [], "findings": "", "gaps": []},
    "7": {"decision": "Met", "evidence": [], "findings": "", "gaps": []}
  },
  "commendations": [],
  "conditions": [],
  "recommendations": [],
  "red_lines_failed": []
}

verdict is FAIL if either point is Not Met or L4 fired.

Supporting reference

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

skills

README.md

tile.json