[Tracking] Merge taskflow-assistant into this repo

Đang mở
#397 0 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
5/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
15/100
Loại issue
Tính năng
Độ rõ ràng
Đặc tả rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
csharp, github-actions
Lĩnh vực
backend-api-design, ci-cd

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

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).
Ngôn ngữ chính
C#
Star
1
Fork
0
Merge trung bình
2 giờ 2 phút
Pull request đã merge (30 ngày)
98

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của nevridge/TaskFlow

Tất cả issue của nevridge/TaskFlow

Issue tương tự

Thêm issue về C#

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.