[Tracking] Assistant work after the move

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

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

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

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
csharp
領域
backend-api-design

調査の方向性

Read the linked issues #414, #415, #409, #412, and #410 to understand their scope and dependencies, then check blockers #400 and #398. The tracking issue is done when all five are closed or closed as not wanted, each with a one-line reason.

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

説明

tech-debt

Groups the assistant (assistant/) work that follows the monorepo move (#397, done: #398 closed 2026-11-06). All of it except #410 waits for #400, because assistant feature work uses the merged pipeline.

Suggested order

  1. #410 — One-command install and update: the plugin and MCP server run from a runtime folder outside the repo, not from the clone (redesigned 2026-11-06; needs grooming; not blocked by #400, and first because it changes how the assistant is run every day)
  2. #414 — Report created tasks when create_tasks hits a transport error (bug; also set_journal_todos). Independent of the others.
  3. #415 — Stop get_journal from silently creating entries and carrying tasks forward (bug; needs a design decision first). Decide with #409 part 3 and #412 item 1, since all three change how moved tasks are reported.
    3a. [ ] #422 — Show planned subtasks in the planned list and count them in the Planned tasks (N) header of get_journal (needs grooming; changes the same tool output as #415, so build them together)
  4. #409 — Planning reliability in task tools (parts 2 to 4; part 3 is decided with #415).
  5. #412 — Review the smaller API gaps (item 1 is decided with #415; items 7 to 9 came from asst#37).

Notes

  • #411 (run the MCP client against the real API in CI) is not here: it is part of the move and is listed in #397.
  • #414, #415, #409, #412 and #422 are blocked by #400 on GitHub. #410 is not (the blocker was removed on 2026-11-06), so it can be done before the pipeline merge.
  • #409, #410 and #412 were transferred from nevridge/taskflow-assistant on 2026-11-04; their old references redirect.

Done when

All six are closed or closed as not wanted, each with a one-line reason.

主要言語
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 を短くまとめたダイジェスト。