Start with observable behavior
“Add search” leaves several decisions open. Who uses it? What data does it search? Should it include drafts? Before the agent changes files, describe the result from the user's perspective.
For a lesson catalog, a requirement might be: “A signed-in learner searches published PHP lessons by title. An empty query shows the existing list. No matches produce a message with a way to clear the field.” This lets you assess a solution without prescribing every line of code.
This is an example project brief, not a claim that Kodivo has this search interface. The principle applies to a new feature in any project: describe what a user does and what they see.
Give the existing project context
Ask the agent to read the existing implementation and related tests first. Point to the screen or files if you know them. Name behavior that must stay intact, such as lesson ordering or the restriction to published material.
Many projects already have validation, access controls and interface components. The agent can reuse them when it has the context. Before requesting a new layer or package, check whether the codebase or framework already provides the needed behavior.
Write constraints with reasons
A constraint helps when it describes a real cost or boundary. “Add no dependency because the current framework handles this task” gives the agent a reason. “Do not change the publication process” protects a specific area. A general request for “the best architecture” leaves the judgment without criteria.
You can use this brief:
Inspect the existing catalog and tests. Add title search for published lessons. Preserve the existing ordering and access restrictions. Use the current form input and framework mechanisms. Explain any proposed dependency or extra layer before implementing it. Check an empty query, no results and the exclusion of drafts.
Agree on evidence of completion
Request a description of the changed behavior, results from relevant tests and unresolved decisions. Check that the evidence matches the requirement: a title-search test does not replace checking that drafts remain inaccessible. Request focused corrections and check the affected cases again.
You can build the knowledge for these conversations through short Kodivo lessons. With MCP connected, the agent fetches material and learning context, so you can discuss a rule before requesting a change in your own project. Kodivo does not need access to your project files to supply a lesson.
