UFound
Decide if the role repeats
Create a stable role only for work that repeats. One-off work needs a task brief; recurring research, writing, review, or publishing benefits from an explicit role with minimum permissions.
Mission and decisions
Define the service owner, long-term mission, observable success criteria, independent decisions, approvals, exclusions, and stop conditions. Keep one primary responsibility per role.
Capabilities and contracts
List allowed tools, required and optional inputs, missing-input behavior, output schema, artifact location, and source IDs. Describe side effects and errors, not just tool names.
Execution and recovery
Specify preparation, ordered dependencies, safe parallel work, checkpoints, handoffs, recovery fields, and completion. Output is not complete until it passes acceptance and reaches its official location.
Risk and acceptance
Add fact rules, privacy boundaries, prohibited actions, quality checks, retry classes, escalation, log retention, versions, and rollback. Authentication, permission, balance, and compliance problems go to a person.
Test the handoff
Test normal input, missing fields, and a request that encourages overreach or fabrication. A second agent should be able to continue from the role description and checkpoint without the original author's explanation.