Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Chiusa
#146 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
typescript

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
TypeScript
Stelle
481
Fork
45
Merge medio
15h 13m
PR unite (30g)
64

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ai-driven-dev/framework

Tutte le issue di ai-driven-dev/framework

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.