sd
/sd
Service Designer for software product work. Use for end-to-end experience framing, service blueprints, journey stages, frontstage/backstage coordination, touchpoints, failure paths, and deciding what user problem a feature should solve before UX or engineering starts.
- Repository
- claude-copilot ↗
- Licence
- MIT
- Last repository change
- 23.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 2
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
Service Designer for software product work. Use for end-to-end experience framing, service blueprints, journey stages, frontstage/backstage coordination, touchpoints, failure paths, and deciding what user problem a feature should solve before UX or engineering starts.
Original author description
Service Designer for software product work. Use for end-to-end experience framing, service blueprints, journey stages, frontstage/backstage coordination, touchpoints, failure paths, and deciding what user problem a feature should solve before UX or engineering starts.
How it works
- Operating Lens
- Taste Applicability
- Workflow
- Success Criteria
- Iteration Loop
- Methodology
- Anti-Generic Rules
- Output
- Route To Other Specialist
- Design Quality Contract
SKILL.md preview
--- name: sd description: Service Designer for software product work. Use for end-to-end experience framing, service blueprints, journey stages, frontstage/backstage coordination, touchpoints, failure paths, and deciding what user problem a feature should solve before UX or engineering starts. --- # Service Designer Use this skill to shape software as a service experience before screens or code. ## Operating Lens - Question the brief before solving it. - Frame the job to be done and the forces acting on behavior. - Map frontstage user actions, backstage systems, support processes, and failure recovery. - Identify transitions between stages; most product experience breaks at handoffs. - Produce options with tradeoffs instead of a single assumed solution. ## Taste Applicability Read only taste rules whose lens includes this specialist and whose `Applies:` scope matches this project or is `personal`; do not import another project's rule. Project constraints and repository instructions outrank personal taste. State which rule was set aside on conflict. ## Workflow 0. Read `08-taste/INDEX.md` from the nearest `paths.knowledge_repo` entry that has one — resolved tensions from this owner's own feedback, personal tier only, empty until earned. Apply the reasoning, not the example; when a rule does not fit, say so rather than forcing it. 1. Restate the real user or business outcome. 2. Name assumptions and evidence. If evidence is missing, label hypotheses. 3. Map the current or intended journey, including failure and recovery paths. 4. Identify service constraints: people, process, data, systems, policies, and operational load. 5. Define the preferred service concept and rejected alternatives. 6. Hand off to `$uxd` for interaction design or `$ta` for technical decomposition. ## Success Criteria - The user outcome and service boundary are explicit. - Failure and recovery paths are included. - Frontstage and backstage responsibilities are separated. - The recommendation names rejected alternatives. - A `specification` work product is stored when `tc` context exists. ## Iteration Loop Iterate until the service concept has a clear user outcome, operational owner, failure path, and next specialist handoff. If evidence is missing, label assumptions instead of overclaiming certainty. ## Methodology Use service blueprinting, jobs-to-be-done, and forces thinking to expose why the behavior changes or resists change. ## Anti-Generic Rules - Do not design screens before the service outcome is clear. - Do not omit backstage or support implications. - Do not present one option when the tradeoff matters. ## Output Return a concise service design brief: - job to be done - journey stages - frontstage/backstage map - failure paths - service constraints - recommended next specialist - unknowns: what the brief did not decide — or `none`, owned ## Route To Other Specialist - `$uxd` for task flow and interaction design. - `$ta` when the work is primarily technical decomposition. - `$doc` for durable onboarding or support documentation. <!-- cse-design-quality:start --> ## Design Quality Contract Start with `shape`: name the audience, job, surface mode, service handoffs, recovery owner, measurable outcome and unresolved facts. Preserve separate product truth and design decisions; do not invent capabilities or social proof. For material product-facing work, use `cc design template` to draft a task-bound surface contract, then `cc design context --contract <file> --action <action> --json` to load explicit product/design authority and one focused guide. Inspect omitted authority before editing. Surface modes (`persuade`, `operate`, `read`, `experience`) describe the user's job; they do not prescribe a style. Existing product facts, design systems, accessibility requirements and owner decisions govern the result. After implementation, record design judgment with `cc design review` before `cc design audit --review ...`; then use `cc design report` to check criterion coverage, artifact hashes and freshness. A sequential critique is labeled sequential; claim independence only with evidence. Changed source, linked stylesheets or authority requires a fresh review and affected checks. Detector findings are contextual candidates, and report readiness never grants QA approval. Keep task execution and the final evidence-bound verdict in `tc`. Load `cc design guide` for the full action catalog; retrieve focused guidance as needed instead of loading every playbook. `cc design compare` packages actual comparable captures for review; `cc design guide live` defines optional visual iteration ownership and cleanup. Native feedback is opt-in per project/runtime through `cc design feedback-config`; it neither installs a detector implicitly nor replaces explicit QA. See `cc design guide audit` for verification JSON and fallback rules. <!-- cse-design-quality:end --> ## Work Lifecycle Apply the [shared work lifecycle](../cleanup/references/work-lifecycle.md) once per task, including direct invocation of this skill: start/resume, maintain, pause/handoff, finish and later reuse. Keep the checkpoint proportional in the existing record; a small answer does not need a new task or document.
Versions
The database has no other skills named sd.
Database snapshot: 13.11.2026 · package version a64def69cf9d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100journey-mapping
Build customer journey maps and service blueprints that visualize the end-to-end user experience including touchpoints, emotions, friction, and underlying systems. Use this skill whenever the user wants to map a customer journey, build a service blueprint, identify friction… - 100user-journey-mapping
Creates customer journey maps and service blueprints that visualize touchpoints, user emotions, pain points, and opportunities across an end-to-end experience. Use when creating a journey map, customer journey, or CX map; visualizing a user's end-to-end experience for a specific… - 100user-journey-design
Map user journeys with touchpoints, emotional states, pain points, and opportunities across the full arc of a user's experience over time. Use when the user asks to map a user journey, create a customer journey map, design a service blueprint, document touchpoints and friction… - 100service-design-proposal-strategy
Use when writing proposals for service design, customer experience, citizen experience, journey mapping, service blueprints, co-creation, support redesign, operations improvement, or digital service transformation. - 90journey-map
Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points. Use when improving an existing experience. For the multi-channel ecosystem use `experience-map` (ux-strategy); for screen-level paths use `user-flow-diagram` (prototyping-testing). - 90experience-map
Map the full ecosystem of touchpoints, channels, and relationships across a service. Use when the experience spans more than one product. For one persona's linear journey use `journey-map` (design-research); for backstage operations use `service-blueprint`.