What problem does this solve?
When I scaffold a team using Harness, I receive the generated agents and skills, but I need to manually visualize how agents interact with each other.
For larger architectures such as Fan-out/Fan-in, Supervisor, or Hierarchical Delegation, understanding communication flow can become difficult without a visual representation.
This makes it harder to review, document, and explain generated team structures to collaborators.
Proposed solution
Add an optional architecture diagram generation step as part of the Harness output.
For example:
- Generate a Mermaid diagram (architecture.mmd)
- Generate a Markdown file containing the diagram
- Include agent relationships, orchestration flow, and skill dependencies
Example:
graph TD
-
Supervisor --> ResearchAgent
-
Supervisor --> BuilderAgent
-
-
This would provide an immediately understandable view of the generated harness structure.
Alternatives considered
- Manually drawing diagrams after generation.
- Using third-party diagramming tools.
These approaches require extra effort and can become outdated when the harness changes.
Related team-architecture pattern (if any)
Supervisor
Additional context (optional)
Visual architecture output would improve onboarding, documentation, reviews, and educational use cases while remaining consistent with Harness's focus on team design and orchestration.
What problem does this solve?
When I scaffold a team using Harness, I receive the generated agents and skills, but I need to manually visualize how agents interact with each other.
For larger architectures such as Fan-out/Fan-in, Supervisor, or Hierarchical Delegation, understanding communication flow can become difficult without a visual representation.
This makes it harder to review, document, and explain generated team structures to collaborators.
Proposed solution
Add an optional architecture diagram generation step as part of the Harness output.
For example:
Example:
graph TD
This would provide an immediately understandable view of the generated harness structure.
Alternatives considered
These approaches require extra effort and can become outdated when the harness changes.
Related team-architecture pattern (if any)
Supervisor
Additional context (optional)
Visual architecture output would improve onboarding, documentation, reviews, and educational use cases while remaining consistent with Harness's focus on team design and orchestration.