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

Aperta
#945 6 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
39/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Tranquilla
Stack tecnologico
typescript

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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!

Lingua principale
TypeScript
Stelle
25.6k
Fork
2.1k
Merge medio
3h 57m
PR unite (30g)
170

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di EveryInc/compound-engineering-plugin

Tutte le issue di EveryInc/compound-engineering-plugin

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.