Skip to main content
Use this page when the Studio starter prompt or user request asks Veryfront Agent to create a plan.

​
Agent-facing flow

  1. Load the Veryfront router skill: load_skill({ "skillId": "veryfront" }).
  2. Load this page as the canonical docs resource for the task.
  3. If the request is broad, ask exactly one short form_input with one required brief field, then continue from the submitted brief. The starter text is routing intent, not the planning brief.
  4. Inspect only the project files, routes, docs, and history needed to plan the requested work.
  5. Write a concise plan with outcome, assumptions, steps, verification, risks, and stop condition.
  6. For the bare Studio “Create a plan” starter, save the plan as Markdown under plans/ with create_file or update_file when file tools are available. Choose a concise slug from the submitted brief for the file name.
  7. For other planning requests, save the plan when the user asks for a file or gives an exact path.

​
Guardrails

  • Do not load a removed plan sub-skill.
  • Do not delegate on the first turn just to acknowledge the starter prompt.
  • Do not treat the starter label, generic starter prompt, or storage location instruction as the work topic.
  • Do not ask for output paths, depth, mode, audience, or option fields by default.
  • Do not create app, page, route, or chat UI files for a planning-only request.
  • Do not finish the bare Studio starter with inline-only output when file tools are available.

​
Example pattern

Keep examples close to the product domain without baking in a single customer workflow. A good default plan theme is an AI agent capability, tool boundary, or verification path. 
<!-- plans/support-triage-agent.md -->
# Plan: Support Triage Agent

## Outcome

Create an AI agent that reads incoming support requests, classifies severity, drafts a suggested reply, and escalates cases that need a human.

## Assumptions

- The agent can read support tickets through an approved integration.
- The agent drafts responses but does not send them automatically.
- High-risk or billing-related cases require human review.

## Steps

1. Define the agent goal, stop condition, and escalation rules.
2. Select the minimum required tools for listing, reading, and drafting ticket responses.
3. Add instructions for severity classification, reply drafting, and handoff notes.
4. Add a verification checklist with sample tickets for low, medium, and urgent cases.
5. Test that the agent refuses unsupported actions and asks for approval before state changes.

## Verification

- The agent classifies sample tickets consistently.
- Draft replies include evidence from the ticket.
- Escalation cases produce a concise human handoff summary.
- The agent never sends a message without explicit approval.
In the MCP tool call, path is the saved plan path and content is the Markdown artifact. When updating an existing plan, read it first and use update_file with the returned version or checksum when available.

​
Output shape

For the bare Studio starter, return the saved file path plus a short summary. For other planning requests, return the plan in the conversation unless the user requested a file.