skills.rest
deuveme
deuvemeCOMMUNITY
Explore all skills by this author →
GitHub

Collaborative Design

Explore visual scenarios to clarify ambiguous design features before writing specs.

4|Updated Mar 24, 2026
Search Tags:#design#documentation#collaboration#governance#scenarios#decision-making
One-click install
npx skills add https://github.com/deuveme/product-flow --skill collaborative-design-deuveme
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Collaborative Design
Source: https://github.com/deuveme/product-flow/tree/main/plugins/product-flow/skills/praxis.collaborative-design
Command: npx skills add https://github.com/deuveme/product-flow --skill collaborative-design-deuveme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligning ambiguous feature requirements is hard; this skill keeps teams in design mode to explore scenarios visually before committing to specs or implementation.

Core Features & Use Cases

  • Visual storytelling: present before/after states, workflows, and input/output examples to ground decisions.
  • Structured exploration: research, timeline, scenarios, options, decisions, and documentation are tracked in a single session.
  • Decision logging: captures what was decided and why to support governance and onboarding.

Quick Start

Start a collaborative design session and document the scenarios, decisions, and outcomes.

Frequently Asked Questions about Collaborative Design

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

FAQPage Schema
How do I clarify ambiguous feature requirements before writing specs?▼

To clarify ambiguous feature requirements, you explore visual scenarios like before/after states and workflows before committing to final specs. This approach keeps teams in design mode to align on product, UI, or process workflows visually.

What is the best way to document design decisions and governance for onboarding?▼

Documenting design decisions requires structured decision logging that captures what was decided and why during design sessions. This maintains governance and supports onboarding by tracking research, scenarios, and outcomes in a single session.

How do I structure a design session to explore visual scenarios and options?▼

Structure a design session by tracking research, timeline, scenarios, options, and documentation together. This visual storytelling method grounds decisions using input/output examples and before/after states to clarify ambiguous features.

Can I use visual storytelling for both product UI and process workflow design?▼

Yes, visual storytelling applies to design sessions across product UI and process workflows. It clarifies ambiguous features by presenting before/after states and workflows to ground decisions before writing implementation specs.

Does collaborative design require any specific components or dependencies to start?▼

No specific components or dependencies are required to start a collaborative design session. You can immediately begin exploring visual scenarios, logging decisions, and documenting artifacts without external environment setup.

Related Skills

Explore More Design & Creative Skills→
scute-shscute-sh
3

collaborative-design

Guides visual scenario mapping and iterative refinement for software feature design.

Official
Intermediate
MaplumeXMaplumeX

openspec-archive-change

Archive completed openspec changes with validation and delta-spec synchronization checks.

Community
Advanced
hydershahhydershah

bug-debugging

Reproduce bugs, isolate root causes, and verify fixes with structured debugging.

Community
Advanced
SkogAISkogAI
1

brainstorming

Refine rough ideas into concrete designs through collaborative questioning.

Official
Basic