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

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

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

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

評価

難易度
4/5
見積もり時間
1〜2日
初心者へのやさしさ
38/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
静か
技術スタック
typescript
領域
devtools

調査の方向性

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.

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

説明

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.

主要言語
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 を短くまとめたダイジェスト。