d2s-options
/d2s-options
Stage 3 (options) of a discovery-to-spec design exploration. Helps the team lay out 2 to 4 genuinely different design directions, with Figma links, pros, cons, the insight each relies on and what each changes in the product. Use whenever the user wants to explore alternatives, compare design directions or brainstorm solutions for a framed problem.
- Author
- eranlipi ↗
- Repository
- discovery-to-spec ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Stage 3 (options) of a discovery-to-spec design exploration. Helps the team lay out 2 to 4 genuinely different design directions, with Figma links, pros, cons, the insight each relies on and what each changes in the product. Use whenever the user wants to explore alternatives, compare design directions or brainstorm solutions for a framed problem.
Original author description
Stage 3 (options) of a discovery-to-spec design exploration. Helps the team lay out 2 to 4 genuinely different design directions, with Figma links, pros, cons, the insight each relies on and what each changes in the product. Use whenever the user wants to explore alternatives, compare design directions or brainstorm solutions for a framed problem.
How it works
SKILL.md has no level-two headings · 12 lines, 233 words
SKILL.md preview
---
name: d2s-options
description: Stage 3 (options) of a discovery-to-spec design exploration. Helps the team lay out 2 to 4 genuinely different design directions, with Figma links, pros, cons, the insight each relies on and what each changes in the product. Use whenever the user wants to explore alternatives, compare design directions or brainstorm solutions for a framed problem.
---
# d2s: options (stage 3 of 6)
Input: $ARGUMENTS is the exploration id. If it is empty, run `{{cli}} status` and ask which one.
1. Read `.d2s.json` and write in its `lang`. Read `{{dir}}/context.md`, `brief.md` and `insights.md` first; every direction must address the problem and the desired outcome in the brief, starting from where it lives in the product today.
2. Help the user describe 2 to 4 directions that differ in approach, not only in visuals. If two directions are variations of the same idea, say so and help find a real alternative.
3. For each direction write a short name, its Figma or prototype link, the idea in a sentence or two, pros, cons, the insight it relies on, and what changes in the product: the screens that change, the design-system components it reuses, any new components, and the effect on other flows.
4. Ask the user for the Figma links; never make up a link. If the Figma MCP server is available, read the linked frames so the descriptions match the designs, read the current screens linked under "Where it lives today" in the brief, and search the team's design-system library. Prefer existing components, and name every new one.
5. Write the recommendation section, but make clear that the decision belongs to the team at the decision gate.
6. Run `{{cli}} check <id>`. Next step: `{{cli}} next <id>`, then `/d2s-decide`.
Versions
The database has no other skills named d2s-options.
Database snapshot: 13.11.2026 · package version 0585bda943b6 (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
- 100d2s-discovery
Design discovery the discovery-to-spec (d2s) way, for designers and product managers working in chat. Runs a discovery session that takes a new request through the problem, the evidence and 2 to 4 directions in one conversation, or helps with one stage at a time: frame a… - 100design-directions
Plan several clearly different UI directions for an existing product before building them, grounded in how real products, including competitors' help docs, solve the same job. Use when someone asks for options, directions, alternatives, explorations, or "a few ideas" for a… - 10021st-ui-explore
Explore and compare multiple meaningfully different UI directions grounded in the current project's design system and 21st inspiration. Use when the user wants options, variants, concepts, a redesign direction, visual experimentation, or is unsure how a new interface should… - 100prototype-wall
Explore a piece of UI by building many genuinely different variants and laying them out live on one pan-and-zoom board (a Figma-style wall), so the user can compare them at a glance, kill the weak ones, and leave pinned notes that copy back to the agent as precise, element-level… - 100design-ideate
Generate several distinct UI directions for a screen or flow before committing to one. Produces 2-4 named interface directions with layout logic, component choices, and tradeoffs, optionally with generated mockup images. Use when the user says "ideate the UI", "give me layout… - 90explore-design-directions
Develop and compare materially different UI/UX directions, choose the smallest decision-useful artifact, and present a recommendation for human selection. Use when a material design choice remains open; route explicit prototype, mockup, or design-lab work to prototype-design-directions.