[Tracking] Merge taskflow-assistant into this repo

オープン
  • 何か問題がありますか？
#397 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
15/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
csharp, github-actions
領域
backend-api-design, ci-cd

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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).
主要言語
C#
スター
1
フォーク
0
平均マージ
2時間 2分
マージ済み PR（30日）
98

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

nevridge/TaskFlow のほかの issue

nevridge/TaskFlow の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。