Proposal: Optional planning-with-files integration in ce-plan handoff (5.3.9)

オープン
#945 コメント 6 件 リアクション 0 件 担当者 0 名 GitHub で見る

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

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

評価

難易度
4/5
見積もり時間
1〜2日
初心者へのやさしさ
39/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
静か
技術スタック
typescript

調査の方向性

Read skills/ce-plan/references/plan-handoff.md, especially section 5.3.9, and the existing load-by-reference steps in ce-plan. The proposal names a new skills/ce-plan/references/planning-with-files-integration.md for the detection and write protocol. Done means an optional integration updates task_plan.md when present, skips silently when absent, and continues to 5.4; the issue is still asking maintainers whether they want this integration.

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

説明

Hi! I'm a user of both compound-engineering and planning-with-files (23K+ GitHub stars) and wanted to float a small, optional integration between them before investing in a PR.

The problem

ce-plan writes detailed plans to docs/plans/. planning-with-files tracks live agent state in task_plan.md, which re-injects before every turn via a UserPromptSubmit hook. Today these are disconnected — a ce-plan run populates docs/plans/ but leaves task_plan.md stale, so the agent's turn-by-turn context doesn't reflect the plan just generated.

The current workaround is a CLAUDE.md instruction ("after /ce-plan, write to task_plan.md") — it works but can be forgotten or skipped.

The proposed fix

A small, optional detection-and-write step in ce-plan's 5.3.9 Final Checks phase:

  1. Check if task_plan.md exists in the project root — if not, skip silently (no error, no output, no disruption to the post-generation menu)
  2. If yes: extract the plan goal and ### U<N>. headings, write a concise ## Current Plan section to task_plan.md
  3. Continue to 5.4 as normal

Zero coupling to planning-with-files internals — detection is purely task_plan.md file existence. Works for any project that has the file; gracefully skips for everyone who doesn't.

Minimal footprint

The change would touch:

  • skills/ce-plan/references/plan-handoff.md (section 5.3.9) — one new paragraph: "Load references/planning-with-files-integration.md and execute the integration step"
  • skills/ce-plan/references/planning-with-files-integration.md (new file) — the full detection-and-write protocol, following the same load-by-reference pattern already used throughout ce-plan

I've already written a full implementation plan as a planning exercise. Happy to share the specifics if useful.

Before I open a PR

Wanted to check a few things first:

  • Is this kind of optional third-party integration something you'd consider for the CE plugin?
  • Any concerns about using task_plan.md existence as the detection signal (vs. something more explicit)?
  • Would you prefer this live somewhere else — a separate bridge skill, or a contribution to the planning-with-files side instead?

Thanks for maintaining such a solid plugin!

主要言語
TypeScript
スター
25.6k
フォーク
2.1k
平均マージ
3時間 57分
マージ済み PR(30日)
170

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

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

EveryInc/compound-engineering-plugin のほかの issue

EveryInc/compound-engineering-plugin の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

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

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