Encode intent/decision/plan workflow for Snowflake platform delivery so engagements share a durable recipe instead of one-off LLM chats. Co-authored-by: Cursor <cursoragent@cursor.com>
612 B
612 B
D002 — LLM as front door only
- Status: active
- Date: 2026-07-15
Decision
Cursor/Claude Code skills are an optional UX that load customer intent.yaml + decisions/ and invoke platformctl. The LLM must not emit unaudited GRANT/SQL as the system of record.
Why
Session N+1 with TF state recovers what exists, not why. Skills + decision files fix amnesia without putting the model in the apply path.
Alternatives rejected
- Free-form chat regenerating the whole platform each time
- Requiring every customer engineer to use an agent IDE (CLI-only path remains first-class)