Index of every page on this site: llms.txt
All skills
tristanmanchester avatar

/good-services-service-design

@3323bc9
by Tristan Manchestertristanmanchester/agent-skills3 stars
2
Run it yourself

Audit or improve an end-to-end service with Lou Downe's Good Services principles, journey maps, operational blueprints, and evidence-linked improvement work. Use for service outcomes across digital, human, and offline channels, not pure visual styling or a narrow code defect without a service-design question.

Use this Skill: https://skilld.dev/gh/tristanmanchester/agent-skills/good-services-service-design

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesworkshop-agenda.md

≈605 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Workshop agenda: Good Services audit + improvement plan

This is a lightweight format you can run with 4–10 stakeholders (design, ops, engineering, policy, support).

Prep (before the session)

Ask participants to bring:

  • Top 10 support contacts/complaint themes
  • Any analytics: drop-offs, completion rates, time-to-complete, escalation rates
  • Known policy/legal constraints
  • A frontline representative (calls/appointments/casework)

Print or share templates:

  • templates/service-definition-canvas.md
  • templates/service-map.md
  • templates/principles-scorecard.md
  • templates/improvement-backlog.md

2-hour version (fast alignment)

0:00–0:10 — Opening

  • Agree the outcome: “At the end we will have a shared service definition, top problems, and a prioritised backlog.”
  • Set ground rules: user-first, plain language, be explicit about assumptions.

0:10–0:30 — Define the service

  • Fill the Service Definition Canvas.
  • Confirm start/done boundaries and the primary user group.

0:30–1:05 — Map the journey (happy path + key exceptions)

  • Build a 6–12 step journey map.
  • Mark: drop-offs, handoffs, and “where users seek help”.

1:05–1:30 — Principles scan

  • Review the 15 principles for the agreed service, user groups, and channels.
  • Mark each principle assessed, unverified, or out of scope using the scorecard. Assign a local 0–2 score only when assessed evidence supports it; leave the score blank for unverified or out-of-scope principles.
  • Record sources, coverage gaps, and disagreements. An unresolved disagreement is an evidence question, not a reason to manufacture or average a numeric score.

1:30–1:55 — Backlog & ownership

  • Convert top failures into backlog items (Now/Next/Later).
  • Assign an owner and first next step per item (research, prototype, policy check, ops change).

1:55–2:00 — Close

  • Confirm: what will be shared out, and when the next review is.

1-day version (deeper)

Add:

  • Service blueprinting (frontstage/backstage/support)
  • Accessibility review and inclusion risk mapping
  • Decision transparency audit (Principle 14)
  • Support model design (Principle 15)
  • Measures/incentives review (Principle 12)

Outputs to produce after the workshop

  • Filled templates (definition, map, scorecard, backlog)
  • A short narrative summary (1 page)
  • “Top unknowns / evidence needed next” list

Source: SKILL.md on GitHub

Skill behaviors

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

Third-party checks

No alerts1mo5 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    The skill is a set of markdown-based instructions and templates for service design based on the 'Good Services' principles. It contains no executable code, network operations, or suspicious patterns and is entirely safe to use.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

  • Runlayer7mo

    2/11 files flagged

  • ZeroLeaks6mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 3323bc9. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 weeks ago.

Steadyupdated last month

Capability

Other metadata
compatibility
Core review works from supplied evidence without special tools. Current regulatory, accessibility, or operational claims require appropriate sources and access; artifact creation depends on available tools.
metadata
{
  "version": "2.0.0",
  "author": "generated-skill",
  "category": "service-design",
  "tags": "service-design, journey-mapping, service-blueprint, good-services"
}

README badge

README badge for tristanmanchester/agent-skills/good-services-service-design