convergence-design

Coordinate collaborative design sessions and produce a formal design document.

2|Updated Mar 31, 2026

Search Tags:#design #collaboration #patterns #human-in-the-loop #decision-making #design-document #design-approaches

Ready to run

npx skills add https://github.com/c-sonnier/convergence --skill convergence-design

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: convergence-design
Source: https://github.com/c-sonnier/convergence/tree/main/plugins/convergence/skills/design
Command: npx skills add https://github.com/c-sonnier/convergence --skill convergence-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative design decisions are often conflicted by ambiguous requirements and missing early-state documentation. This skill surfaces assumptions, patterns, and open questions to produce a formal, human-approved design document before implementation, reducing waste and rework.

Core Features & Use Cases

Collaborative design sessions with a human to align on goals and constraints.
Surface patterns and decisions from the codebase to inform design.
Produce a ~200-line design document capturing current state, desired end state, approaches, and decisions.

Quick Start

Start a collaborative design session with the human and generate a ~200-line design document summary.

Frequently Asked Questions about convergence-design

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

FAQPage Schema

How do I facilitate a collaborative design session to align product decisions?▼

To facilitate a collaborative design session, you guide a human-in-the-loop discussion to surface patterns, decisions, and open questions, ultimately recording formal current state, desired end state, and proposed approaches within a standardized design document.

What is a formal design document and when do I need one for my project?▼

A formal design document is a structured record capturing current state, desired end state, patterns, proposed approaches, and decisions. You need one after research or when implementing well-understood changes requiring human approval to reduce waste and rework.

How do I document current state and desired end state for software design approaches?▼

You document current state and desired end state by collaborating in a human-guided design session to surface assumptions and codebase patterns, then recording these elements alongside proposed approaches and decisions in a standardized design doc.

Can I use this collaborative design approach for well-understood changes requiring human approval?▼

Yes, you can use this collaborative design approach for well-understood changes requiring human approval, as it specifically applies to aligning product decisions and producing a formal design document before implementation begins.

What are the limitations of human-in-the-loop design collaboration for pattern documentation?▼

A limitation of human-in-the-loop design collaboration is that it requires active human participation to surface assumptions and open questions, meaning it cannot autonomously generate design approaches or make final product decisions without direct interactive input.

What's the best way to reduce rework caused by ambiguous requirements in design collaboration?▼

The best way to reduce rework from ambiguous requirements is to produce a formal, human-approved design document early, surfacing assumptions, patterns, and open questions before implementation to ensure alignment on goals and constraints.