De-slop: remove every em-dash + banned words across all modules + capstone (#94)
Sync course wiki / sync-wiki (push) Successful in 4s
Sync course wiki / sync-wiki (push) Successful in 4s
Co-authored-by: claude <claude@jpaul.io> Co-committed-by: claude <claude@jpaul.io>
This commit was merged in pull request #94.
This commit is contained in:
@@ -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."
|
||||
|
||||
Reference in New Issue
Block a user