Ai and Orin
Define a useful task for Orin
A useful request states the goal, the target, the limits and the expected result. You do not need to write a formal plan before you ask, but these details make the work easier to review.
| Decision | Example instruction |
|---|---|
| Goal | "Turn these notes into a tracking table." |
| Target | "Use only the Decisions section of the selected workshop." |
| Result | "Create columns Task, Owner, Due date and Status." |
| Unknown data | "Leave missing owners or dates unassigned; do not invent them." |
| Way of working | "Plan first and explain the changes before applying them." |
| Access | "Do not browse the internet, edit external files or publish links." |
| Acceptance | "Propose the result next to the originals so I can review it." |
#Reusable preferences and project context
Define terms, document structure and project rules explicitly. When your Orin settings offer memory or skills, use them for recurring preferences and procedures. A skill is a reusable guide for a task; a tool is the action that does the work. Neither should silently expand the permissions you granted.
#Review scope and consequences
Before you approve, compare the proposed action with your request. Check which board, objects, files or service will change. Review usage and cost during the task. Canceling stops later steps, but it does not automatically undo steps already completed. Undo on the board reverts its edits, not external actions.