sd-service-design

Orchestrates a service design pipeline from intent review through discovery to personas, journeys, and blueprints.

3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/runlegion/legion --skill sd-service-design-runlegion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sd-service-design
Source: https://github.com/runlegion/legion/tree/main/plugin/skills/sd-service-design
Command: npx skills add https://github.com/runlegion/legion --skill sd-service-design-runlegion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a product intent into a defined service requires structured discovery, evidence validation, and consistent artifacts. This Skill conducts that first-diamond pipeline so personas, journeys, and blueprints are grounded in verified insights rather than guesswork. ## Core Features & Use Cases - Pipeline orchestration: Runs intent-review, discover, ecosystem-imagine, then the persona, journey, and blueprint writers in dependency order, with a validation gate between steps. - Evidence-gated artifacts: Every persona, journey, and blueprint statement traces to a Discovery insight or intent field; contradicted or blocked insights never leak into artifacts. - Park and resume: Steps that cannot finish write draft documents, store checkpoint anchors via legion reflect, and arm timed or signal-based wakes to resume later. - Use Case: A repo with an intent document starts its service design; the agent runs the pipeline, eavesdrops on real users for evidence, and produces a validated Discovery, Ecosystem, and per-persona journey and blueprint documents in the legion store. ## Quick Start Ask the agent to run the service design pipeline for a repo that already has an intent document, starting with intent review and proceeding through discovery to the persona, journey, and blueprint writers.

Frequently Asked Questions about sd-service-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a service design discovery pipeline for a repo?

Start with the repo's intent document, found via legion document list --doc-type intent. The pipeline then runs intent-review, discover, ecosystem-imagine, and the persona, journey, and blueprint writers in order, with a validation gate between steps.

What happens when a service design step cannot finish?

The step parks instead of guessing: it writes its output as a draft document naming blocked items, stores a checkpoint reflection with the resume point, and arms a timed defer or a signal-based wake. On wake it recalls the anchor and continues from the named items.

Does the pipeline require an intent document before starting?

Yes. A repo with no intent document stops the pipeline immediately, because the intent is the root input for every downstream artifact. Writing the intent itself is outside this pipeline's scope.

Can personas, journeys, and blueprints be written in parallel?

Only separate chains parallelize. Within one chain the order is strict: persona first, then its journey, then its blueprint, and each writer refuses a missing input document. Different personas' chains can progress independently.

What are the limitations of this service design pipeline?

It covers only the first diamond: problem discovery and service definition. It never produces solutions, specs, or code, refuses to call sd-write-spec, and depends on the legion store, eavesdrop listening, and the watch daemon for evidence and coordination.