Practical Agent workflows

Give the Agent a goal, the relevant Space or repository, and the boundary between drafting and applying. These examples can be adapted to your project; replace names and IDs with resources you can access.

Understand an unfamiliar system

Ask: “Read the architecture and deployment pages in the Payments Space. Explain the main services, dependencies, and how a request moves through the system. Link each source.”

Read the cited pages if an answer affects an implementation decision. If documentation is incomplete, ask the Agent to identify what it could not establish and inspect connected source where available. Do not treat a fluent answer as evidence for a missing fact.

Improve an existing guide

Ask: “Read the deployment guide. Draft a troubleshooting section for the documented failure cases. Show the proposed change before updating the page.”

Check the target page, the replacement content, and whether unrelated sections remain intact. Approve only the version you want, then open the page to verify the result. If the page changed during review, refresh the proposal instead of applying an old version.

Triage documentation maintenance

Ask: “Show pending Autopilot suggestions for the Engineering Space. Summarize the affected pages and changes without applying them.” Choose a suggestion, inspect its diff, and request the desired action. Your plan and permissions still determine which Autopilot actions are available.

Generate a focused deliverable

Ask: “Show the supported generators and help me produce a README for this imported repository.” Identify the repository and desired output. Review the generator proposal and credit impact before approval. For Full Tree documentation, complete the tree-preview review before creating the Space.

Get help with a blocked task

Ask: “Help me diagnose this failed export. If support is needed, draft a message with the relevant details for me to review.” Inspect the support draft before sending. Include the affected resource and observable error, without pasting credentials.

Verify outcomes

For reads, expect source pages or a clear statement that the information could not be found. For writes, expect the target resource and confirmed result. For long-running work, expect progress or a link to its status rather than an immediate completion claim. See actions and approvals.