sd-ecosystem-imagine

Generates a schema-validated ecosystem document mapping actors, channels, and value exchanges for a service intent.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a product intent into a real service requires answering hard questions about who chooses it, who carries risk, how value flows, and where it breaks. This Skill systematically interrogates an intent document through five analytical passes and lands a schema-valid Ecosystem document with the answers built in, rather than leaving open questions for the operator. ## Core Features & Use Cases - Five perspective passes: Runs actor-walk, boundary-walk, second-order, value-lifecycle, and evidence-adversarial passes to find roughly four times more questions than a single open pass. - Tiered answer routing: Answers questions through design reasoning first, then Discovery insights, then real people via eavesdrop signals, escalating only strategy and values choices to the operator with recommendations. - Schema-validated output: Builds and validates an Ecosystem document with tiered actors, channels, value exchanges, moments of truth, and failure modes using legion document commands. - Use Case: After a Discovery lands for a new service intent, invoke this Skill to produce a complete ecosystem map with a register of open questions, confidence-scored predictions, and a draft/review/done status reflecting what remains unresolved. ## Quick Start Run the sd-ecosystem-imagine step on the landed Discovery for this intent to produce a validated ecosystem document with its open-question register.

Frequently Asked Questions about sd-ecosystem-imagine

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

FAQPage Schema
How do I turn a product intent into an ecosystem map?

Run this step after the Discovery lands: it executes five perspective passes (actor-walk, boundary-walk, second-order, value-lifecycle, evidence-adversarial) to find questions, answers them from design reasoning and Discovery evidence, and lands a schema-valid Ecosystem document via legion document create.

What questions does an ecosystem design step need to answer?

It covers choosing, benefit and risk, dependence, value flow, trust, governance, and failure. Each question is answered by design reasoning first, then Discovery insights, then real people through eavesdrop, with only strategy and values choices escalated to the operator.

When should questions go to the operator versus real people?

Only strategy and values choices go to the operator, each with a recommended answer. Questions about how people actually behave that the Discovery cannot settle go to real people through eavesdrop signals, and the document lands as a draft until answers arrive.

What happens when the ecosystem document has open questions?

Open entries form a register stored in the document's failure_modes. With questions out to real people the document lands at draft status; with only operator choices open it lands at review; with an empty register it lands at done. Each entry gets a confidence-scored prediction emission.

Can a contradicted Discovery insight ground an ecosystem answer?

No. Contradicted insights never ground answers, and unresolved contradicted insights stop the step entirely until the operator rules on them. Only supported or bounded insights may be cited as evidence.