Files
ai-workflow-course/modules/26-orchestrating-multiple-agents/lab/agent-prompts/agent-44-clear.md
T
claude 389ac2e460 style(no-slop): remove every em-dash + banned words across all modules + capstone
Apply the no-ai-slop standard (now binding in AGENTS.md): the em-dash character is
banned outright (restructured, not blind-replaced), plus the banned word/phrase
list (delve, leverage, robust, seamless, truly, unlock, etc.). 0 em-dashes remain
in modules + capstone; the only "robust" left is the planted M10 ai-change.patch
trap. Module H1 titles use a colon separator.

All deliberate teaching devices preserved; labs compile/parse (py/sh/yaml/json);
no junk. AGENTS.md updated with the hard no-slop rules.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TfzV5QvtPDz8LJS3Pu5VLT
2026-06-22 23:21:09 -04:00

1.1 KiB

Agent prompt: issue #44, branch feature/44-clear

Run this in the tasks-app-44-clear worktree. This agent deliberately collides with #42. Both add a new elif to the same dispatch chain in cli.py: same file, same region. That's the agent-vs-agent merge conflict the lab wants you to predict in Part A and resolve in Part C. It is not a mistake in the lab; it is the lesson. Two agents on the same file is a joint, not a seam.


You are working in this worktree only. Do not touch any other folder.

Task: Add a clear command to cli.py that removes all tasks.

  • Add a new elif command == "clear": branch to the dispatch in main() in cli.py.
  • It should empty the task list and save, then print cleared.
  • Reuse the existing load() / save() helpers. Do not change tasks.py.

Acceptance criteria:

  • python cli.py clear removes all tasks and prints cleared.
  • python cli.py list afterward shows (no tasks yet).

When done, commit your work on this branch with a message referencing #44, then push the branch. Stop there; the human opens and reviews the PR, and should expect a conflict against feature/42-count at merge.