Using SDD in the Future

As SDD evolves, users should use it with conventional, low-friction graphical tools, without requiring techical skills. To use SDD with LLMs, no github repo should be needed.

Possible Future SDD App

A user-friendly app should provide friction-free access to SDD.

Possible offerings of an SDD app:

• Simple editing of SDDs
• Flexible visual design for diagrams
• Versioning of SDDs
• Reuse of common elements (templates)
• Preformatted "Packages" of SDD content that can be used for specific tasks
• Fluid browsing of an SDD's graph
• Focused (filtered) views of an SDD's graph
• Representation of links / external concerns in the context of SDD graph nodes

Such an app would unlock SDD to non-technical users, and to non-designers, so SDD can contribute value to in collaborative product definition and product management activities, integrating with existing tools.

Future MCP Server

The current SDD Skill requires the SDD repository to be present locally. A future MCP server would enable an LLM to access equivalent functionality and more by relying on remote resources.

Potential 3rd Party Integrations

When linking SDD dontent to an external application makes sense, it is worth asking if a closer integration ("better-than-links"), via API or plug-in makes more sense - and if it's worth it.

Since SDD relies on diagrams, integrations with existing diagramming tools might make sense: Figma/ Figjam, Miro, etc. But a tool's capability to draw diagrams does not make it a natural integration fit. Practice will tell.