[Tracking] Merge taskflow-assistant into this repo

Abierto
  • ¿Algo no está bien?
#397 0 comentarios 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
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
csharp, github-actions
Área
backend-api-design, ci-cd

Línea de trabajo

This is a tracking issue spanning assistant/, the root .claude/ pipelines, CI, and plugin.json; it explicitly depends on #387 and nevridge/taskflow-assistant#37 and says not to start before they ship. Read the decision in nevridge/taskflow-assistant#32 and follow the listed child issues in order. Done when the five checklist outcomes are met, including CI checks for DTO compatibility and error code mappings and the archived repository README.

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

Descripción

tech-debt

Tracks the move of nevridge/taskflow-assistant (MCP server, plugin, chat skill) into assistant/. The decision and reasons are on nevridge/taskflow-assistant#32.

The goal is to stop API drift: a change to the API and the matching change to the MCP server ship in one PR, and CI fails if they don't.

Order

Do not start until #387 and nevridge/taskflow-assistant#37 have shipped. Each item is its own PR, except the first, which is a checklist.

  1. nevridge/taskflow-assistant#38 Audit the assistant repo, make it public and transfer its open issues
  2. #398 Move the assistant into assistant/. (done 2026-11-06; history restored in #425)
  3. #411 Run the MCP client against the real API in CI. Blocked by #398
  4. #399 Add TaskFlow.Contracts with error codes, enums and a mapping test. Blocked by #398
  5. #400 Merge the two feature-factory pipelines. Blocked by #398

Items 3 to 5 can land in any order, but all three should land before the next API feature, so that feature is the first to run the full pipeline.

Issues that transfer with the move

These moved from nevridge/taskflow-assistant into this repo with nevridge/taskflow-assistant#38 (2026-11-04) and are done here, after the move:

  • #409 Planning reliability in task tools. Already trimmed: parts 1 and 5 shipped as nevridge/taskflow-assistant#28 and nevridge/taskflow-assistant#26, parts 2 to 4 remain (echo the planned day, report moved tasks, backlog view), and part 3 overlaps #412.
  • #410 One-command install and update. Its paths and marketplace URL change with the move.
  • #412 Review the smaller API gaps.

Done before the move, in the assistant repo: nevridge/taskflow-assistant#20 (resolve the project before saving task fields), then nevridge/taskflow-assistant#37.

These API-touching issues wait for this tracker (each is blocked by it), so they are built with the merged pipeline and their MCP change ships in the same PR: #243 (then #369), #241, #328, #365 and #386.

Done when

  • A DTO change that breaks the MCP client fails the PR that makes it.
  • A new API error code fails CI until it is mapped or explicitly marked as not needing a message.
  • feature-factory covers API, web and the assistant (MCP server, plugin and chat skill) from the root .claude/.
  • nevridge/taskflow-assistant is archived with a README pointing here.
  • plugin.json is bumped for the first release from the new location.

Out of scope

  • Sharing DTOs (deferred; see the decision).
  • Install and update automation (#410, transferred with the other issues).
Lenguaje dominante
C#
Estrellas
1
Forks
0
Merge medio
2 h 2 min
PR fusionados (30 d)
98

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 nevridge/TaskFlow

Todos los issues de nevridge/TaskFlow

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.