Skip to content

Latest commit

 

History

History
72 lines (45 loc) · 1.86 KB

File metadata and controls

72 lines (45 loc) · 1.86 KB

Week 5 Write-up

Tip: To preview this markdown file

  • On Mac, press Command (⌘) + Shift + V
  • On Windows/Linux, press Ctrl + Shift + V

INSTRUCTIONS

Fill out all of the TODOs in this file.

SUBMISSION DETAILS

Name: TODO
SUNet ID: TODO
Citations: TODO

This assignment took me about TODO hours to do.

YOUR RESPONSES

Automation A: Warp Drive saved prompts, rules, MCP servers

a. Design of each automation, including goals, inputs/outputs, steps

TODO

b. Before vs. after (i.e. manual workflow vs. automated workflow)

TODO

c. Autonomy levels used for each completed task (what code permissions, why, and how you supervised)

TODO

d. (if applicable) Multi‑agent notes: roles, coordination strategy, and concurrency wins/risks/failures

TODO

e. How you used the automation (what pain point it resolves or accelerates)

TODO

Automation B: Multi‑agent workflows in Warp

a. Design of each automation, including goals, inputs/outputs, steps

TODO

b. Before vs. after (i.e. manual workflow vs. automated workflow)

TODO

c. Autonomy levels used for each completed task (what code permissions, why, and how you supervised)

TODO

d. (if applicable) Multi‑agent notes: roles, coordination strategy, and concurrency wins/risks/failures

TODO

e. How you used the automation (what pain point it resolves or accelerates)

TODO

(Optional) Automation C: Any Additional Automations

a. Design of each automation, including goals, inputs/outputs, steps

TODO

b. Before vs. after (i.e. manual workflow vs. automated workflow)

TODO

c. Autonomy levels used for each completed task (what code permissions, why, and how you supervised)

TODO

d. (if applicable) Multi‑agent notes: roles, coordination strategy, and concurrency wins/risks/failures

TODO

e. How you used the automation (what pain point it resolves or accelerates)

TODO