[FEATURE] built-in prompts/prompt templates

[EItanya]

📋 Prerequisites

• I have searched the existing issues to avoid creating a duplicate
• By submitting this issue, you agree to follow our Code of Conduct

📝 Feature Summary

Built in prompts and prompt templates which can be used by agents in kagent to ease adoption and use

❓ Problem Statement / Motivation

Currently when building custom agents for kagent, users have to build and design their own system prompts from scratch, but this can be very difficult. It would be great if users could take advantage of built-in prompts or tempaltes from their own agents.

For example, if a user is using skills, we could have a system prompt template for skill-use agents which could explain to the agent how to properly use skills, and then append the users system prompt.

💡 Proposed Solution

I recommend a 2 step approach:

1. Adding the ability to include prompts/prompt templates from the agent CRD
2. Add a set of basic prompts/templates to the kagent controller which can serve them via its own MCP server.

🔄 Alternatives Considered

No response

🎯 Affected Service(s)

Multiple services / System-wide

📚 Additional Context

No response

🙋 Are you willing to contribute?

• I am willing to submit a PR for this feature

[fl-sean03]

Great feature idea! This would significantly lower the barrier to entry for new users building custom agents.

A few thoughts on the proposed approach:

Step 1 - Agent CRD prompt templates: This aligns well with the existing staticInstruction field we just added in #1394. We could extend the CRD with a promptTemplateRef field that references named templates, and the controller would resolve these at agent creation time — similar to how toolServerRef works today.

Step 2 - Built-in templates via MCP server: This is clever — serving prompts as MCP resources means any agent could discover and use them dynamically. The controller's existing MCP server infrastructure could be extended for this.

One consideration: should templates be composable? For example, a user might want to combine a "skill-use" template with a "kubernetes-admin" template. A simple merge strategy (or ordered concatenation with separators) could handle this.

Happy to help with implementation if this gets scoped out further.

[EItanya]

Decided on a slightly different approach for now. We can always re-open later for extended support. see #1401