Use when you have new source material (transcripts, interviews, support logs, docs, code changes) and want to reason about what existing service design artifacts need updating
From service-designnpx claudepluginhub zemptime/zemptime-marketplace --plugin service-designThis skill uses the workspace's default tool permissions.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Core principle: New evidence updates understanding. Process source material and propose specific, traceable updates to existing artifacts.
Accept pasted content, file paths, or URLs. Classify before processing:
| Source type | What it typically reveals |
|---|---|
| Transcript / interview | User mental models, emotions, language, unmet expectations |
| Support log | Failure points, recovery paths, frequency signals |
| Ops runbook / code change | Backstage process shifts, new constraints |
| Business doc | Strategic intent, success metrics, org priorities |
| User feedback | Peak moments, information gaps |
docs/service-design/<slice>/).| Classification | Meaning | Action |
|---|---|---|
| Confirm | Evidence supports an existing [hypothesis] | Upgrade to [confirmed], cite source |
| Contradict | Evidence conflicts with an existing entry | Downgrade or flag [gap], explain conflict |
| Extend | Elaborates on an existing entry | Propose addition with confidence tag |
| Novel | No match in existing artifacts | Propose where it belongs |
docs/service-design/<slice>/sources/ for traceability.The most important output is confidence movement: [hypothesis] → [confirmed], or [confirmed] → [gap] when evidence contradicts. Every ingest should strengthen or challenge what's already written.
Present proposed updates for human review. The human decides what to accept.
Every sibling skill produces artifacts this skill updates: service-design:service-blueprint, service-design:empathy-analysis, service-design:journey-map. Run ingest first, then the relevant skill to incorporate accepted changes.