Files
ai-workflow-course/modules/26-orchestrating-multiple-agents/lab/agent-prompts/agent-43-docs.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.2 KiB
Raw Blame History

Agent prompt: issue #43, branch feature/43-docs

Run this in the tasks-app-43-docs worktree. This agent owns documentation only, different files from every other agent in the fleet, so it merges cleanly no matter what the others do. This is what a genuinely parallel split looks like: disjoint files, no shared interface.


You are working in this worktree only. Do not touch any other folder, and do not edit cli.py or tasks.py; code is owned by other agents.

Task: Document the tasks-app and start a changelog.

  • In README.md, add a "Commands" section documenting the existing commands: add <title>, list, and done <index>. Show an example invocation for each.
  • Create CHANGELOG.md with a "Keep a Changelog"style ## [Unreleased] section and an ### Added list. (Other agents are adding commands in parallel; leave a placeholder line noting that new commands are landing; the human will reconcile the exact list at merge.)

Acceptance criteria:

  • README.md documents the three existing commands accurately.
  • CHANGELOG.md exists and is valid markdown.
  • No code files change.

When done, commit your work on this branch with a message referencing #43, then push the branch. Stop there; the human opens and reviews the PR.