Using Kangentic as an optional visual orchestration layer for AIDD

[waewoo007]

Hello

I have been looking at several visual orchestration tools for AI coding agents, and although Kangentic is still a young project, it currently seems to me one of the most promising options.

I am not specifically attached to Kangentic though. If the AIDD maintainers or community know another visual orchestration tool that would fit AIDD better, I would be very interested in hearing about it.

What I find interesting is the potential complementarity:

AIDD = methodology and reusable skills
Kangentic = visual orchestration and execution

Kangentic already provides:

• Kanban workflows
• Git worktrees
• multi-agent execution
• human-in-the-loop gates
• session monitoring
• per-column agent configuration

AIDD already provides:

• planning
• implementation
• testing
• review
• debugging
• refinement
• VCS workflows
• reusable skills and rules

A Kangentic workflow could map naturally to AIDD skills, for example:

• Planning → aidd-dev:01-plan
• Executing → aidd-dev:02-implement
• Validation → aidd-dev:06-test / aidd-dev:03-assert
• Code Review → aidd-dev:05-review
• Debug → aidd-dev:08-debug
• PR / MR → aidd-vcs:02-pull-request

This can already be done today by installing both tools and configuring Kangentic's "Message to agent" field.

So perhaps no deep technical integration is needed at all.

A lightweight approach could simply be:

• documenting that AIDD and Kangentic work well together
• providing an optional example/template
• documenting recommended skill-to-stage mappings
• sharing Feature / Bugfix / Spike workflow examples

I also noticed the new aidd-ui plugin. Since it is still at a very early stage, I wonder whether it could be useful to explore existing visual orchestration tools before building overlapping capabilities.

This would remain entirely optional.

I do not think AIDD should depend on Kangentic or replace terminal-based workflows.

The idea would simply be:

terminal-based agents and AIDD skills underneath, with an optional visual orchestration layer for users or teams who benefit from it.

There could also be a mutual ecosystem benefit:

• AIDD users looking for visual orchestration could discover Kangentic
• Kangentic users looking for a structured development methodology could discover AIDD

Kangentic could remain framework-agnostic, and AIDD could remain orchestration-tool agnostic.

Would this kind of lightweight relationship fit AIDD's philosophy?

Would it make sense to:

• document Kangentic as one possible visual orchestration option,
• provide a community/example template,
• and potentially discuss this with the Kangentic maintainers so both projects can reference each other?