Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

feat(aidd-orchestrator): route by discovered capability, not hardcoded plugin

Cerrado
  • ¿Algo no está bien?
#146 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
typescript
Área
developer-experience, tooling

Línea de trabajo

Start with docs/ARCHITECTURE.md, then inspect the orchestrator routing and check-sdlc references described in the issue and the call sites in #406. Use #406 as the acceptance fixture and review #250's CI check. Done means plans are derived from installed capabilities, shown before execution, and degrade when a plugin is removed without naming a plugin directly.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Problem

The orchestrator's route is hardcoded. It names aidd-dev by address in its routing regexes and its check-sdlc step, which violates the cross-plugin orthogonality rule in docs/ARCHITECTURE.md — see #406, the concrete violation.

It has no choice today: nothing lets a skill discover, at runtime, what the installed plugins can do. So the pipeline is written down instead of derived.

Scope

An orchestrator that, on every request, reads what is available and proposes a plan, instead of replaying a fixed pipeline.

Its inputs:

  • The installed plugins — context, dev, pm, vcs, ui, plus stack and craftsmanship plugins (#148). It reads their skills and agents directly; no separate declaration contract.
  • The project — its state, its memory, its detected stack.
  • The request — what the user actually asked for.

Its output: an orchestration plan, presented, then run.

Acceptance criteria

  • The orchestrator names no plugin by address. Remove the hardcoded aidd-dev and the routing regexes of #406, and nothing breaks.
  • Installing a new plugin changes the plan it proposes, with no code change.
  • Uninstalling a plugin degrades the plan instead of breaking it.
  • The plan is shown before it runs.

Related

  • #406 — the violation this feature makes impossible. Its call sites are the acceptance fixture.
  • #250 — the CI check that stops the next violation from landing.
Lenguaje dominante
TypeScript
Estrellas
481
Forks
45
Merge medio
13 h 56 min
PR fusionados (30 d)
73

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ai-driven-dev/framework

Todos los issues de ai-driven-dev/framework

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.