claude
fbec36cb67
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
1.7 KiB
1.7 KiB
Title: <specific, scannable — someone reading 40 titles should know what this is>
Context / problem
<What is wrong or missing, and WHY it matters.
- For a bug: the exact command you ran, what happened, and what you expected.
- For a feature: the motivation — what the user can't do today.>
Acceptance criteria
<The checklist that defines DONE. Concrete and verifiable. This is the most important section — it is the definition of done for a human AND the spec for an agent.>
- <verifiable statement, e.g. "
done 99prints a clear error and exits non-zero"> - <...>
- <...>
Out of scope
<What this issue does NOT cover, so the work doesn't sprawl into a refactor.>
Proposed approach (optional)
<A suggestion, not a spec. The person or agent doing the work may know a better one. Leave blank if you don't have one.>
- Type: bug | feature | chore
- Priority: high | med | low
- Ready: yes/no (acceptance criteria solid enough to start?)
- Route to: human | agent — and one sentence on WHY (in terms of the issue's clarity/scope)