instructor

To create step-by-step instructions for manual server configuration, define the task, purpose, and estimated time, then list exact UI labels, URLs, and verification steps. This structured manual format ensures precise human execution for tasks requiring direct intervention.

The best way to document manual DNS changes is to use a structured template with TASK, WHY, TIME, STEP-BY-STEP, VERIFY, and ROLLBACK sections. This provides exact URLs and UI labels to ensure the human interaction is repeatable and verifiable.

Yes, you can generate a rollback plan for app store submissions by defining the manual task in a structured output format. This format explicitly requires a ROLLBACK section alongside step-by-step instructions to safely reverse changes if the external submission fails.

Yes, this approach works for documenting external service tasks without API automation by producing human-readable manuals. It captures exact UI element references and step-by-step actions for any manual task where an agent cannot perform the action directly.

A manual task template should include TASK, WHY, TIME, STEP-BY-STEP, VERIFY, and ROLLBACK sections. It must require exact URLs, button names, and input values to ensure the manual instructions are clear, repeatable, and leave no ambiguity for the human executor.

Manual infrastructure tasks need a structured output format with verification steps to prevent human error during sensitive operations like server configuration. Defining explicit VERIFY and ROLLBACK sections ensures the manual changes are confirmed and safely reversible.