“Fix the export” leaves the agent guessing what a correct result looks like.
A concrete deliverable, clear boundaries, and evidence for the reviewer.
Write the outcome before the instructions
Start with what should be different when the task is done. “Customers can export all filtered records as CSV” is more useful than “look at the export code.” Add who needs the change and why it matters.
Then identify relevant project knowledge and prior work. Link or reference the material the agent should use instead of embedding unrelated documents in the brief.
Separate access from permission to act
An agent may have credentials for a system without being authorized to take every action in that system. State the allowed scope, the actions requiring review, and when the agent should stop for clarification.
Do not paste secret values into this template. Configure credentials through your chosen execution environment or Norc’s assigned vault secrets. The brief should describe needed access without exposing the credential.
Make review part of the deliverable
Ask for observable evidence: changed files, test output, an artifact, or a concise explanation of unresolved issues. State the acceptance checks before execution so the reviewer and agent share the same definition of completion.
If a task depends on earlier investigation, connect that dependency and use its completed output. In Norc, project context and configured skills can accompany the task without rewriting your operating instructions for every run.
A brief you can adapt.
No account required. Replace the example with your own task.
OUTCOME Customers can export all filtered records as a CSV file. CONTEXT Use the existing export flow and the project’s CSV conventions. Reference the linked issue and the completed investigation task. SCOPE Update the export behavior and its tests. Keep unrelated UI unchanged. Do not deploy or change production data. Ask before expanding scope. TOOLS & ACCESS Use the assigned repository and configured credentials. Never paste secret values into the task or result. ACCEPTANCE CHECKS - Export includes every record matching the active filters. - Empty results produce a valid CSV with column headers. - Existing relevant checks still pass. RETURN FOR REVIEW Summarize changed files, test results, and unresolved questions. Include the branch or pull request when available. IF BLOCKED Explain what is missing and ask for clarification. Do not guess about permissions, customer requirements, or destructive actions.
Keep credential values in your vault, not in the brief.
Practical questions.
Can I use this template without Norc?
Yes. Copy it into your existing task tracker or agent conversation. It is a general task-brief structure and does not require an account.
What should an agent do if the brief is incomplete?
Ask for the missing information when it changes scope, access, or correctness. In Norc, configured context gates can return a thin brief for clarification.
By the Norc team · Product details checked against the Norc project documentation. View the project