Guided Configuration
Help a person complete protected configuration without pretending the agent performed or verified inaccessible work.
Workflow
- Confirm the desired outcome, authoritative product documentation, current state, target account or environment, and actions the user permits.
- Separate steps the agent can verify from steps only the user can perform or observe.
- Present one material step at a time with its purpose, expected visible result, and safe recovery path.
- Ask the user to perform protected authentication, approval, credential, billing, device, or administrative actions themselves.
- After each step, verify the result through authorized readback or ask for the smallest non-sensitive observation needed.
- Stop on an unexpected account, environment, permission request, destructive effect, cost, or security warning.
- Summarize completed, unverified, failed, and reversed steps without claiming inaccessible success.
Boundaries
- Never ask the user to paste secrets, recovery codes, private keys, or full tokens into chat.
- Do not generate commands that broaden privileges beyond the stated need.
- Do not bypass security prompts or describe a warning as harmless without evidence.
- Configuration does not authorize publication, deployment, billing, or data migration unless those actions were separately approved.
Output
During a step, return Current step, Expected result, and relevant Recovery or Security boundary. At a checkpoint or completion, reconcile Goal, Authoritative source, Observed result, and Remaining steps, preserving failed and unverified work.
Continuity and evidence
During configuration, present the current human step, expected result, and relevant recovery or security boundary. Keep the complete state reconciliation for a checkpoint or final response. Preserve failed and unverified steps, and reuse observed completion when it remains current.
Read the original acceptance example when checking this behavior.
1---2name: guided-configuration-33description: Guide a person through configuration steps that require their account, device, approval, credential, or external interface while verifying each observable result. Invoke explicitly when the agent cannot or should not perform the protected step itself.4license: MIT5---67# Guided Configuration89Help a person complete protected configuration without pretending the agent performed or verified inaccessible work.1011## Workflow12131. Confirm the desired outcome, authoritative product documentation, current state, target account or environment, and actions the user permits.142. Separate steps the agent can verify from steps only the user can perform or observe.153. Present one material step at a time with its purpose, expected visible result, and safe recovery path.164. Ask the user to perform protected authentication, approval, credential, billing, device, or administrative actions themselves.175. After each step, verify the result through authorized readback or ask for the smallest non-sensitive observation needed.186. Stop on an unexpected account, environment, permission request, destructive effect, cost, or security warning.197. Summarize completed, unverified, failed, and reversed steps without claiming inaccessible success.2021## Boundaries2223- Never ask the user to paste secrets, recovery codes, private keys, or full tokens into chat.24- Do not generate commands that broaden privileges beyond the stated need.25- Do not bypass security prompts or describe a warning as harmless without evidence.26- Configuration does not authorize publication, deployment, billing, or data migration unless those actions were separately approved.2728## Output2930During a step, return `Current step`, `Expected result`, and relevant `Recovery` or `Security boundary`. At a checkpoint or completion, reconcile `Goal`, `Authoritative source`, `Observed result`, and `Remaining steps`, preserving failed and unverified work.3132## Continuity and evidence3334During configuration, present the current human step, expected result, and relevant recovery or security boundary. Keep the complete state reconciliation for a checkpoint or final response. Preserve failed and unverified steps, and reuse observed completion when it remains current.3536Read [the original acceptance example](references/continuity-example.md) when checking this behavior.
JovaniPink