Problem
Complex tasks like "set up a MySQL-to-Snowflake pipeline" require 5-10 coordinated steps. Agents figure this out from `kbagent context` + their own knowledge, but:
- They may miss steps (e.g., forgetting to set up orchestration)
- They don't know common pitfalls (e.g., MULTI_STATEMENT_COUNT for Snowflake)
- Each agent rediscovers the same workflow
Proposal
kbagent recipe list
kbagent recipe show mysql-to-snowflake
Output: structured workflow plan:
- Ordered steps with exact commands
- Required parameters per step
- Common pitfalls and how to avoid them
- Estimated duration
- Rollback procedure if something fails
Recipes could cover:
- Database extractor setup (MySQL, Postgres, Snowflake, etc.)
- Transformation pipeline (extract → transform → write)
- Project migration / cloning
- Dev branch workflow (branch → modify → test → merge)
- Data sharing between projects
Implementation options
- Static recipes in YAML/JSON files shipped with CLI
- Dynamic recipes that inspect project state and adapt
- AI-generated recipes via the AI Service API
Context
Discussion from Devil's Advocate analysis of kbagent's agentic capabilities.
Problem
Complex tasks like "set up a MySQL-to-Snowflake pipeline" require 5-10 coordinated steps. Agents figure this out from `kbagent context` + their own knowledge, but:
Proposal
Output: structured workflow plan:
Recipes could cover:
Implementation options
Context
Discussion from Devil's Advocate analysis of kbagent's agentic capabilities.