Files
ai-workflow-course/modules/26-orchestrating-multiple-agents/lab/agent-prompts/agent-44-clear.md
T
claude f925fd9645 fix(M7-27+capstone): apply AI-drives-git reframe, lesson=theory, de-slop course-wide
Phase 2 sweep — all modules are post-pivot, so the learner directs the AI agent
(Claude Code as the worked example) to do the git/setup work and verifies, instead
of typing commands by hand; no re-teaching basics. Lesson sections are theory with
example output; all execution lives in the labs. De-slopped ("prose" etc. gone
course-wide, em-dash density thinned). /path/to placeholders -> ~/ai-workflow-course.

Every deliberate teaching device verified intact: M10 ai-change.patch trap,
M12 bad-clear-snippet, M13/M27 planted pending_count bug, M15 secret+typosquat+MD5,
M18 BREAK=1, M21 absent-.gitignore, M22 poisoned skill, M24 no-op patch, M25 --simulate.
Labs compile/parse (py/sh/yaml/json); no junk.

Closes #83
Closes #86
Closes #89

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

1.2 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.