Create a focused Agent with clear boundaries
Define a role, tool scope, and completion criteria, then verify a delegated task.
ExtensionsPurpose#
Create a focused Agent to handle a clearly bounded task with a defined role.
Before you start#
Choose an independent task with explicit files and completion criteria. Project definitions live in .claude/agents/; personal definitions live in ~/.claude/agents/. An Agent neither isolates files automatically nor acts as a permanently online separate machine.
First task#
- Select
@Agentin the project and createdocs-reviewer. - Keep the default model, configure necessary tools through the interface, and enter:
Review only the specified Markdown files.
Do not edit, install, commit, or publish.
Report issues, file locations, evidence, and unexamined items.
Done means every supplied file is covered and claims are verifiable.
- Save and ask the assistant to delegate the review to
docs-reviewer. - Inspect the invocation and report. Have the main conversation verify findings before repairing anything.
Confirm success#
The Agent uses its intended role, supplies real locations and evidence, and makes no unauthorized edits. Spot-check a finding and a valid sample. Receiving a summary does not prove complete coverage.
Common problems#
- Missing definition: check the project, scope, and filename.
- Unavailable tools: check configuration and authorization.
- Unfamiliar permission field: retain the default; SDK
permissionModedoes not use chat valuesask/code.
Next steps#
Save repeatable steps as a Skill and read permissions. Newer Team or persistent child-session workflows require their corresponding version; an Agent definition alone does not provide them.