justin/ai-workflow-course
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

style(no-slop): remove every em-dash + banned words across all modules + capstone

Browse Source 
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
This commit is contained in:
Claude (agent)
2026-06-22 23:21:09 -04:00
parent 513d7e7ac8
commit 389ac2e460
99 changed files with 1324 additions and 1315 deletions
Download Patch File Download Diff File Expand all files Collapse all files
modules/26-orchestrating-multiple-agents/lab/orchestration-plan.md
+7 -7
View File
@@ -1,7 +1,7 @@
# Coordination plan — Module 26 lab
# Coordination plan: Module 26 lab
This is the artifact orchestration runs on. With one agent, the plan lived in your head. With a
fleet, it has to live here — because your head doesn't scale and it forgets (Module 2).
fleet, it has to live here, because your head doesn't scale and it forgets (Module 2).
Fill the **Status** column as you go, and answer the questions at the bottom. The plan is the
deliverable, not the code.
@@ -12,15 +12,15 @@ deliverable, not the code.
| Issue | Branch | Worktree | Files owned | Depends on | Status |
|-------|--------|----------|-------------|------------|--------|
| #42 count | `feature/42-count` | `tasks-app-42-count` | `cli.py` (dispatch + new fn) | — | queued |
| #43 docs | `feature/43-docs` | `tasks-app-43-docs` | `README.md`, `CHANGELOG.md` | — | queued |
| #44 clear | `feature/44-clear` | `tasks-app-44-clear` | `cli.py` (dispatch + new fn) | — | queued |
| #42 count | `feature/42-count` | `tasks-app-42-count` | `cli.py` (dispatch + new fn) | none | queued |
| #43 docs | `feature/43-docs` | `tasks-app-43-docs` | `README.md`, `CHANGELOG.md` | none | queued |
| #44 clear | `feature/44-clear` | `tasks-app-44-clear` | `cli.py` (dispatch + new fn) | none | queued |
`main` is reserved as the integration point. No agent works in the main worktree.
---
## Part A — Predict the conflicts BEFORE you launch
## Part A: Predict the conflicts BEFORE you launch
Read the "Files owned" column. Which pairs are genuinely parallel, and which will collide at merge?
Write your prediction here, then watch it come true in Part C.
@@ -32,7 +32,7 @@ Write your prediction here, then watch it come true in Part C.
---
## Part D — Score the orchestration honestly
## Part D: Score the orchestration honestly
- **Did parallel beat sequential?** Agent wall-clock (overlapping) + your serial review time +
conflict resolution, vs. "I'd have done these three myself, in order."