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

Open
#945 6 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
39/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
typescript

Research direction

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.

Written by the indexing model from the issue text.

Description

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!

Dominant language
TypeScript
Stars
25.6k
Forks
2.1k
Avg merge
3h 57m
Merged PRs (30d)
170

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EveryInc/compound-engineering-plugin

All issues in EveryInc/compound-engineering-plugin

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.