claude
389ac2e460
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
1.7 KiB
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.
deletewith 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(aremove(index)method or equivalent), mirroring howcompleteworks;cli.pyonly 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/donecommands.