askill
service-design-coordinator

service-design-coordinatorSafety 95Repository

Use when starting or continuing service design analysis for a project — checks what artifacts exist, identifies gaps, recommends which analytical skill to run next

2 stars
1.2k downloads
Updated 2/14/2026

Package Files

Loading files...
SKILL.md

Service Design Coordinator

Core principle: A complete analysis for a service slice requires all 7 artifact types. The coordinator ensures coverage, not perfection.

When invoked, execute this workflow. Do not skip phases.


Phase 1: Inventory

Scan docs/service-design/ for existing slices. For the target slice, list every artifact with its last_updated date. If no slice exists, ask the user to name one before proceeding.

Say: "Slice <name> has N/7 artifacts: [list present], missing: [list absent]."

Flag any artifact older than 30 days as stale — treat stale the same as missing for recommendation purposes.


Phase 2: Recommend Next Artifact

Use this default order. Earlier artifacts feed later ones — but any order works if the user has context to supply.

#SkillRationalePrerequisites
1service-design:actor-profileShared foundation; every artifact references actorsNone
2service-design:stakeholder-mapHow all actors connect; staff experience drives customer experienceActor profiles
3service-design:service-blueprintOperational backbone; other artifacts reference itStakeholder map enriches it
4service-design:empathy-analysisUser's inner world (emotions, information needs)Actor profiles (blueprint enriches it)
5service-design:journey-mapUser's experience sequenced over time and channelsActor profiles (blueprint + empathy enrich it)
6service-design:gap-analysisWhere understanding diverges from realityEmpathy + journey recommended
7service-design:service-diagnosisBottlenecks + improvement designBlueprint + stakeholder map recommended
8service-design:service-design-criticStress-test the whole suite3+ artifacts required

Pick the first missing artifact in this order. If all 7 exist, recommend the critic.

Say: "Recommend running <skill> next because [rationale]. Invoke now?"


Phase 3: Invoke

If the user confirms (or didn't object), invoke the recommended skill immediately. Pass the slice name as context.

After the skill completes, return to Phase 1 — re-inventory and recommend again until the suite is complete or the user stops.


Remember: This is a command. Execute each phase in order. Inventory before recommending, recommend before invoking.

Install

Download ZIP
Requires askill CLI v1.0+

AI Quality Score

78/100Analyzed 2/20/2026

Well-structured service design coordinator skill with clear 3-phase workflow (Inventory → Recommend → Invoke). Excellent actionability with explicit phrases to say and decision criteria. Contains useful "when to use" guidance. Minor gaps: no error handling, tags don't match content, slightly generic file path. Reusability is moderate as it's tailored to a specific service design methodology with 7 artifact types.

95
90
62
72
88

Metadata

Licenseunknown
Version-
Updated2/14/2026
PublisherZempTime

Tags

github-actionstesting