When should platform skills (vercel, stripe, neon, etc.) be formally consulted within the CE workflow loop?

Aperta
#810 0 commenti 1 reazione 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
38/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
typescript
Ambito
devtools

Direzione di ricerca

Start by reading the CE workflow definitions for /ce-brainstorm, /ce-plan, /ce-work, and the ce-best-practices-researcher guidance, then check where platform skills are documented. Propose a lightweight trigger and phase ownership that answers whether research alone is sufficient; done looks like a clear, documented rule for deliberate platform skill coverage.

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

Descrizione

When should platform skills (vercel, stripe, neon, etc.) be formally consulted within the CE workflow loop?

Background

The CE spine (/ce-brainstorm → /ce-plan → /ce-work → /ce-code-review → /ce-compound) doesn't currently specify when platform-specific skills should be formally invoked, or whether using ce-best-practices-researcher to hit official docs directly is a sufficient substitute.

I ran into this concretely while brainstorming a Vercel Cron feature. During the brainstorm, ce-best-practices-researcher fetched Vercel's official cron docs and returned accurate factual coverage — frequency limits, no-retry behavior, maxDuration, etc. But vercel:vercel-functions (the curated platform skill) was never explicitly invoked. The information came in through research; the skill's opinionated patterns and conventions did not.

The question

Is there an intended trigger rule for when platform skills should be formally consulted in the CE loop? A few sub-questions:

  1. Which phase owns it? Is formal platform skill invocation a /ce-plan responsibility (before implementation decisions are locked), a /ce-work responsibility (during coding), or both?

  2. Does ce-best-practices-researcher satisfy the same intent? If the researcher fetches the same official docs the skill would consult, is that equivalent — or does the skill add curated guidance, project conventions, or sequenced setup steps that a raw fetch misses?

  3. Should brainstorms touch platform skills at all? For feasibility grounding (e.g. "can Vercel Crons run every minute on Pro?"), invoking a platform skill during brainstorming seems useful. But it also feels like it might be pulling implementation-layer concerns in too early.

  4. Should there be a named trigger? Something like: "when a plan touches a platform domain (Vercel, Stripe, Neon), explicitly invoke the relevant skill before drafting implementation steps" — added to workflow documentation or AGENTS.md.

Why it matters

Without a clear rule, platform skill coverage is ad hoc — dependent on whether the model happens to recognise the domain in time. For infrastructure features where the wrong architectural choice gets baked into a plan before any code runs, missing the skill at planning time is more costly than missing it during coding.

What I'm not asking

Not asking for platform skills to be auto-invoked on every task — that would add noise. Looking for a lightweight trigger rule that makes coverage deliberate rather than accidental.

Curious whether others have run into this and what patterns you've settled on.

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.