Files
ai-workflow-course/modules/25-autonomous-agents/lab/issue-delete-command.md
T
claude fbec36cb67 feat(course): build out all 27 modules, capstone, scaffold, and conventions
Scaffold the course repo and author the full curriculum in dependency-chain
order, following the settled build decisions in handoff.md.

- Scaffold: course README, vendor-neutral AGENTS.md (dogfoods Module 5),
  _TEMPLATE.md (the fixed 9-section module shape), root .gitignore, ship config.
- Modules 1-2: reference exemplars (locked for tone/depth/lab style).
- Modules 3-27: full lessons + runnable labs, each following the template,
  respecting the chain, vendor/model-agnostic, with "feel the pain" labs.
- Module 8 hosting comparison web-researched and date-stamped (as of 2026-06-22),
  not written from memory; expansion-zone modules carry Verify-before-publish.
- Capstone: the full loop end to end on the running tasks-app example.

Lab code syntax-checked (Python/shell/YAML); every module has the 7 core
template sections.

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

1.7 KiB

Add a delete <index> command to the CLI

Type: feature · Priority: p2 · Labels: cli, ready, agent

Context

tasks-app can add, list, and mark a task done, but there's no way to remove a task. Once a task is added by mistake it stays forever. The done command already takes an index and mutates the list through a method on TaskList, so a delete command should follow the exact same shape — this is a patterned change, not a design problem.

Acceptance criteria

  • python cli.py delete <index> removes the task at that 0-based index and saves the list.
  • After deleting, the remaining tasks keep their relative order.
  • delete with an out-of-range or non-integer index prints a clear error (e.g. no task at index 99) and exits non-zero, instead of dumping a traceback.
  • The logic lives on TaskList (a remove(index) method or equivalent), mirroring how complete works — cli.py only parses arguments and calls it.
  • A test covers: a successful delete removes the right task, and an out-of-range delete is handled.

Out of scope

  • Changing how tasks are stored or numbered.
  • Bulk delete, undo, or a confirmation prompt.
  • Reworking the existing add / list / done commands.