Explore Prompts

Design an enterprise integration plan (high level): connect to CRM/docs/ticketing via MCP tools with strict scopes, auditing, and approvals. Include a rollout plan and risk controls.

Create a red-team scenario library focused on MCP and A2A: injection attempts, privilege escalation, tool misuse, delegation loops, and data leakage. Include severity scoring.

Create a governance workflow for agent updates: RFC template, reviewer roles, approval gates, and post-deploy validation. Include change logs and accountability.

Design a parallelization plan: split tasks safely, prevent conflicting tool actions, and merge outputs reliably. Include concurrency limits and a merge-verification step.

Create a model selection strategy: route tasks by complexity, use smaller models for substeps, and add verifier checks. Include quality/cost tradeoffs and metrics.

Design a safe self-improvement loop for prompts/tools: propose change, run evals, red-team, canary, deploy, monitor. Include stop rules and audit artifacts.

Create a plan quality rubric: completeness, dependency ordering, risk controls, verification steps, and rollback. Provide examples of high-quality vs low-quality plans.

Design a questioning strategy: when to ask, how to propose defaults, and how to avoid excessive back-and-forth. Include a “progress-first” interaction model.

Create policy profiles for user tiers: consumer, enterprise, regulated. Include stricter tool permissions, logging requirements, and human approval gates by tier.

Design an enterprise multi-tenant architecture: per-tenant tool scopes, data isolation, policy profiles, and audit reporting. Include threat model and testing plan.

Design secrets handling: vault integration, short-lived tokens, environment isolation, and audit trails. Include tests to ensure secrets never appear in outputs or logs.

Design a privacy-by-design approach: data minimization, redaction, retention limits, and access controls for agent logs and memory. Include a compliance-friendly checklist.