ce-ideate / ce-brainstorm: ideation HTML lands untracked in docs/ideation with no stated lifecycle

Aperta
#1,626 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

  • #1631 di @khsaurabh — chiusa senza merge

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
typescript

Direzione di ricerca

Start by reading the ce-ideate and ce-brainstorm skill text, especially where each chooses the output root and writes the HTML file; compare this with ce-plan and ce-compound output handling. Decide and document a lifecycle for ideation artifacts, then check that the proposed behavior covers repositories with and without a docs root. A linked pull request exists, but it is closed and unmerged, so check the issue thread and current skill text before starting.

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

Descrizione

Observation

ce-ideate (SKILL.md: "a ranked ideation artifact is written to <root>/ideation/ when that root is present, else to a CE temp dir") and ce-brainstorm write their HTML output to <root>/ideation/<date>-<slug>-ideation.html, which resolves to docs/ideation/ inside the user's repository whenever a docs root exists. On my machine that left untracked HTML files sitting in four separate repos (git status --porcelain --untracked-files=all | grep docs/ideation), because the file lands in a tracked docs/ tree but nothing tracks or ignores it, and the skill does not say what should happen to it afterwards.

ce-plan (docs/plans, committed via PR) and ce-compound (docs/solutions, committed) are durable outputs and fit docs/. The ideation HTML is a one-time read for the person who ran the skill, which is a different lifecycle: it should either be gitignored by convention or written somewhere that dies with the work.

Suggestion

One of:

  1. Write ideation HTML under a gitignored location the plugin owns (for example .claude/deliverables/ce-ideate/ or the plugin's existing tmp/compound-engineering-<uid>/ space used by ce-prototype), and print the path.
  2. Keep docs/ideation/ but add it to the repo's .gitignore on first write (with a one-line note in the skill about why), so a read-once artifact never shows up as an untracked file in git status.
  3. At minimum, document the intended lifecycle in the skill text: is the file meant to be committed, deleted after reading, or left?

Context: I maintain a harness-wide rule for this on my side (a gitignored <repo>/.claude/deliverables/<skill>/ tier plus a cross-platform opener), and the plugin's ideation output is the one producer I could not align locally because the skill text lives in the auto-updated plugin cache.

Version observed: compound-engineering 3.23.3 (every-marketplace).

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.