A structural overhaul so agents can resolve vague commands like "📌🤖 Shoot พี่กบ" autonomously — without asking 10 questions first.
When you write "📌🤖 Shoot พี่กบ", the AI needs to: identify the client, find their content plan, pull latest meeting notes, and invoke the right skill. Right now, it can't do any of that.
พี่กบ = G&O = Green & Organic — but the Lead DB only says "🟡 G&O พี่กบ". AI can't match a calendar event to a client without aliases.
Shoot กบ → AI searches Lead DB for "กบ" → 0 results (Name is "🟡 G&O พี่กบ")Lead DB, Content DB, and Tasks DB are isolated silos. Even if AI finds the client, it can't traverse to their content plan or meeting notes.
"คุยงาน 4.3.26" contains notes for 8+ clients in a single page. AI can't extract "latest meeting about พี่กบ" without reading entire multi-client pages.
พี่กบ + พี่ต๋าว + พี่ซุ้ง + LivingStyle + แพร + SJC — all in one pageAI doesn't know "Shoot" = filming, not weapons. No system maps Content Clinic terminology to skills and databases.
shooting-plan skill + Content DB lookup. Currently: AI asks "what do you mean?"AI doesn't know which databases to search, or in what order, for different types of calendar commands.
Shooting plans, content plans, and templates exist as loose pages — not linked to clients, not consistently named.
Each layer solves a different problem. Together, they enable agents to resolve any vague command autonomously.
Here's exactly how the AI resolves vague commands after the foundation is built.
Parse intent: "Shoot" → Domain vocab maps to filming / content production
Resolve entity: Search Lead DB for "พี่กบ" (checks Name + Aliases field) → finds 🟡 G&O พี่กบ (aliases: กบ, G&O, Green Organic)
Gather context: Follow relations → latest meeting notes show "CEO Branding ส่วนตัวต่อ จนถึงเดือน 6, 60 ชิ้น, 3 Pillars: A=CEO certs, B=Podcast, C=Trend" + action items (นัดถ่าย, เขียนสรุปส่งกลุ่ม)
Route to skill: "Shoot" + client context → invoke shooting-plan skill with client data pre-loaded
Execute: Generate shooting plan for พี่กบ's CEO Branding phase, using the 3-pillar strategy from meeting notes
Parse intent: "Make plan" + "LA Trip" → travel/logistics planning
Resolve entity: Search Lead DB + Tasks DB for "LA" → finds P Tommy entry with LA trip details from meeting notes (EVA Air, Pasadena address, dates Mar 12-18)
Gather context: Pull payment details, flight info, accommodation address, outstanding payments from meeting notes
Execute: Generate comprehensive trip plan with flight details, daily schedule, shooting locations, budget reconciliation
Each phase is self-contained. I can execute Phase 1-2 hands-off. Phases 3-4 need your quick review at the end.
Add Contract End (date), Last Contact (date), Source (select), Payment Type (select) — exactly as planned in the PRD.
update_data_source × 4 calls
Free text field for alternative names: "กบ, G&O, Green Organic, กรีนออแกนิค". This is how the AI resolves entities.
update_data_source — ADD COLUMN "Aliases" RICH_TEXT
Split the overloaded Priority field: rename to Action, clean up options to sales-stage only.
update_data_source — RENAME + ALTER
For each lead with payment-type Priority values (⭐️Buffet, 🏦Monthly, 💵เงินสด), move to new Payment Type field.
update-page × ~15 leads
Fill Aliases for the ~20 most active clients (Paid + Closing status). E.g., P Tommy → "ทอมมี่, Tommy, พี่ทอมมี่"
update-page × ~20 leads
Extract dates from Note field for known contracts (per PRD table: พี่ป๊อป → 2026-08-31, BSG → 2026-03-31, etc.)
update-page × ~10 leads
Two-way relation so each lead links to their content entries, and each content entry links back to the client.
update_data_source — ADD COLUMN "Content" RELATION('content_ds_id', DUAL)
Two-way relation for meeting notes, tasks, and action items linked to specific clients.
update_data_source — ADD COLUMN "Tasks" RELATION('tasks_ds_id', DUAL)
For active clients (Paid status), find their content entries in Content DB and link them via the new relation.
update-page × estimated 30-40 links
For recent task pages that reference specific clients, add the relation link back to Lead DB.
update-page × estimated 15-20 links
A new Cowork skill that contains: domain vocabulary map, intent-to-skill routing table, entity resolution logic, and database search priority rules.
skill-creator → SKILL.md with full routing logic
Shoot/ถ่าย → filming/content production → shooting-plan skill. Deal/ดีล → sales proposal → proposal-generator. ปิด → close deal → Lead DB update. Report/รีพอร์ต → content-clinic-report skill. Plan/แผน → context-dependent (content plan vs trip plan vs daily plan).
For client-related tasks: 1) Search Lead DB (Name + Aliases) → 2) Follow Relations to Content DB → 3) Follow Relations to Tasks DB → 4) Search recent meeting notes. For non-client tasks: 1) Tasks DB → 2) AI Use Case DB → 3) Knowledge DB.
A reusable function: given a name fragment → search Lead DB → return client page URL + status + latest meeting notes + content plan links + contract dates. This becomes the "context packet" that any skill can use.
Updated prompt that: reads context-router skill first, uses entity resolution to find clients, gathers context before acting, routes to appropriate skills.
Prompt Library → Notion
Dry-run the full pipeline: parse → resolve → gather → route → execute. Verify each layer works.
Verify cross-entity resolution (P Tommy + LA) and context gathering from meeting notes.
Log the Context Engineering Foundation as a new AI Use Case, and save the Calendar Worker v2 prompt to Prompt Library.
I can execute Phase 1-3 fully hands-off. Here's the small list of things only you can provide.
I'll fill aliases based on what I can infer from Notion data. You do a 2-min scan to catch any I missed or got wrong.
Need this to migrate "Rosme" Priority entries to the Person field. I'll look this up from your workspace.
Try "📌🤖 Shoot พี่กบ" and "📌🤖 Make LA Trip Plan" in a real Calendar Worker session to validate the full pipeline.