Feature Request: Add Support for Trae AI and Builder Variants (Builder, Builder with MCP, Solo Builder)

[eybersjp]

SpecKit currently supports integrations like Cursor, but does not yet support Trae AI and its builder ecosystem. While Trae shares similarities with Cursor (particularly in handling AI-assisted workflows), the key differentiation lies in its builder agents:

1. Builder (standard build flow)
2. Builder with MCP (multi-component projects and external service linking)
3. Solo Builder (lightweight, independent build process)

Why This Matters

Many teams building AI-driven products are increasingly adopting Trae AI due to its modular approach and streamlined development pipeline.
Without native support in SpecKit, users must manually configure workflows, define schemas, and link prompts across services. This results in unnecessary overhead and duplicated effort.
A dedicated integration would allow SpecKit to eliminate repetitive manual inputs and provide smoother project scaffolding out of the box.

Complexity & Considerations

Unlike Cursor, where the integration is mostly uniform, Trae introduces multiple builder flavors, each with different responsibilities in managing project lifecycles.

Supporting these builders would require SpecKit to:

• Recognize builder type automatically.
• Adjust generation workflows accordingly (e.g., MCP linking vs. single module).
• Handle prompt linking and service orchestration natively instead of relying on user intervention.

Technical Suggestions

To make this integration feasible, a few implementation pathways could be explored:

1. Builder Detection
   Map Trae project config files (e.g., trae.json, mcp.config.ts, or builder.yaml) to identify the active builder type.
   Auto-detect whether the project is using standard Builder, Builder with MCP, or Solo Builder.

2. Workflow Mapping
   Standard Builder → Map directly to SpecKit’s existing schema/generation pipeline.
   Builder with MCP → Extend schema support to handle linked services and multi-agent prompts.
   Solo Builder → Treat as lightweight single-module mode, bypassing orchestration layers.

3. Schema + Prompt Linking
   Introduce a translation layer where Trae’s /plan, /schema, /generate, and /connect commands are represented as SpecKit tasks.
   Allow SpecKit to orchestrate prompt linking automatically rather than requiring users to wire them manually.

4. Fallback Mode
   If builder type cannot be determined, default to manual confirmation once, then persist the choice to avoid repetitive prompts.

Benefits

• Reduces setup friction for teams using Trae AI.
• Makes SpecKit more flexible in modern AI-first dev environments.
• Bridges the gap between supported editors (Cursor) and builder-based AI IDEs.
• Provides a clear, automated pathway to integrate AI builders with minimal user input.