Add Lecture 13 + Project 07: Loop Engineering

新增 Lecture 13（从手动驱动到自动循环）和 Project 07（搭建你的第一个自动循环）。

核心内容：
- L13: 从 /goal 到六原语，generator/evaluator 分离，四种沉默成本，从零搭建第一个 loop
- P07: 三个递进实验 — goal loop、timer loop、maker-checker loop
- 配套代码模板：goal-template.md、loop-state-template.md、maker-prompt.md、checker-prompt.md
- Reference 页新增 Addy Osmani Loop Engineering (2026-06-07) 到 2026 扩展参考
- README 更新徽章（13 lectures / 7 projects），学习路径图、syllabus、project 表格、changelog

Build: ✓

Author: sanbuphy

README.md

@@ -21,8 +21,8 @@
 <p align="center"><strong>A project-based course on building the environment, state management, verification, and control mechanisms that make AI coding agents work reliably.</strong></p>
 
 <p align="center">
-  <img src="https://img.shields.io/badge/Lectures-12-blue?style=flat-square" alt="12 Lectures">
-  <img src="https://img.shields.io/badge/Projects-6-green?style=flat-square" alt="6 Projects">
+  <img src="https://img.shields.io/badge/Lectures-13-blue?style=flat-square" alt="13 Lectures">
+  <img src="https://img.shields.io/badge/Projects-7-green?style=flat-square" alt="7 Projects">
   <img src="https://img.shields.io/badge/Languages-15-yellow?style=flat-square" alt="15 Languages">
   <img src="https://img.shields.io/badge/License-MIT-lightgrey?style=flat-square" alt="MIT License">
   <a href="https://discord.gg/XU7DQmpqk"><img src="https://img.shields.io/badge/Discord-Join_Community-5865F2?style=flat-square&logo=discord&logoColor=white" alt="Join the Discord community"></a>
@@ -205,15 +205,15 @@ For the full course materials, please visit the **[Documentation Website](https:
 
 The curriculum is divided into three parts:
 
-1. **Lectures**: 12 conceptual units explaining the theory behind harness engineering.
-2. **Projects**: 6 hands-on projects where you build an agentic workspace from scratch.
+1. **Lectures**: 13 conceptual units explaining the theory behind harness engineering.
+2. **Projects**: 7 hands-on projects where you build an agentic workspace from scratch.
 3. **Resource Library**: Copy-ready templates (`AGENTS.md`, `feature_list.json`, `init.sh`, etc.) to use in your own repositories today.
 
 ---
 
 ## Quick Start: Improve Your Agent Today
 
-You don't need to read all 12 lectures before you start getting value. If you're already using a coding agent on a real project, here's how to improve it right now.
+You don't need to read all 13 lectures before you start getting value. If you're already using a coding agent on a real project, here's how to improve it right now.
 
 The idea is simple: instead of just writing prompts, give your agent a set of structured files that define what to do, what's been done, and how to verify the work. These files live inside your repo, so every session starts from the same state.
 
@@ -313,6 +313,17 @@ The course is designed to be done in order. Each phase builds on the last.
          v                                     v
     P05  Agent verifies its own work      P06  Build a complete harness
                                                (capstone project)
+
+    Phase 7: AUTOMATE THE LOOP
+    ==========================
+
+    L13  Stop prompting your agent —
+         design loops instead
+
+         |
+         v
+    P07  Build your first automated loop
+         (goal loop, timer loop, maker-checker)
 ```
 
 Each phase takes about a week if you're going part-time. If you want to go faster, phases 1–3 can be done in a long weekend.
@@ -321,7 +332,7 @@ Each phase takes about a week if you're going part-time. If you want to go faste
 
 ## Syllabus
 
-### Lectures — 12 conceptual units, each answering one core question
+### Lectures — 13 conceptual units, each answering one core question
 
 *Read the full text for each lecture on the [Documentation Website](https://walkinglabs.github.io/learn-harness-engineering/).*
 
@@ -339,8 +350,9 @@ Each phase takes about a week if you're going part-time. If you want to go faste
 | [L10](./docs/en/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md) | Why does end-to-end testing change results? | Only a full-pipeline run counts as real verification |
 | [L11](./docs/en/lectures/lecture-11-why-observability-belongs-inside-the-harness/index.md) | Why does observability belong inside the harness? | If you can't see what the agent did, you can't fix what it broke |
 | [L12](./docs/en/lectures/lecture-12-why-every-session-must-leave-a-clean-state/index.md) | Why must every session leave a clean state? | The next session's success depends on this session's cleanup |
+| [L13](./docs/en/lectures/lecture-13-loop-engineering/index.md) | Why do you need to stop prompting your agent? | From manual driving to automated loops — goal loops, timer loops, and maker-checker separation |
 
-### Projects — 6 hands-on projects applying lecture methods to the same Electron app
+### Projects — 7 hands-on projects applying lecture methods to the same Electron app
 
 | Project | What You Do | Harness Mechanism |
 |---------|------------|-------------------|
@@ -350,6 +362,7 @@ Each phase takes about a week if you're going part-time. If you want to go faste
 | [P04](./docs/en/projects/project-04-incremental-indexing/index.md) | Stop the agent from doing too much or too little | Runtime feedback + scope control + incremental indexing |
 | [P05](./docs/en/projects/project-05-grounded-qa-verification/index.md) | Make the agent verify its own work | Self-verification + grounded Q&A + evidence-based completion |
 | [P06](./docs/en/projects/project-06-runtime-observability-and-debugging/index.md) | Build a complete harness from scratch (capstone) | Full harness: all mechanisms + observability + ablation study |
+| [P07](./docs/en/projects/project-07-loop-engineering-first-loop/index.md) | Build your first automated loop | Goal loops, timer loops, maker-checker separation, loop state management |
 
 ```text
     PROJECT EVOLUTION
@@ -371,6 +384,9 @@ Each phase takes about a week if you're going part-time. If you want to go faste
      |
      v
     P06  Complete harness (capstone)       You build the full system
+     |
+     v
+    P07  Your first automated loop        You step outside the loop
 
     Each project's solution becomes the next project's starter.
     The app evolves. Your harness skills grow with it.
@@ -533,12 +549,12 @@ See the full layered reference list in [`docs/en/resources/reference/`](./docs/e
 ```text
 learn-harness-engineering/
 ├── docs/                          # VitePress documentation site
-│   ├── lectures/                  # 12 lectures (index.md + code/ examples)
+│   ├── lectures/                  # 13 lectures (index.md + code/ examples)
 │   │   ├── lecture-01-*/
-│   │   └── ... (12 total)
-│   ├── projects/                  # 6 project descriptions
+│   │   └── ... (13 total)
+│   ├── projects/                  # 7 project descriptions
 │   │   ├── project-01-*/
-│   │   └── ... (6 total)
+│   │   └── ... (7 total)
 │   └── resources/                 # Multilingual templates & references (14 languages)
 │       ├── en/
 │       └── ... (14 total)
@@ -558,7 +574,7 @@ learn-harness-engineering/
 ## How the Course Is Organized
 
 - Each lecture focuses on one question
-- The course includes 6 projects
+- The course includes 7 projects
 - Every project requires the agent to do real work
 - Every project compares weak vs. strong harness results
 - What matters is the measured difference, not how many docs were written
@@ -587,6 +603,23 @@ bash tools/audit-harness.sh /path/to/your/repo
 
 ---
 
+## Changelog
+
+### 2026-07-09 — Loop Engineering Update
+
+Added **Lecture 13** and **Project 07** on **Loop Engineering** — the next layer beyond harness engineering.
+
+**New content:**
+
+- **Lecture 13: Why You Need to Stop Prompting Your Agent** — From `/goal` to the six primitives of loop engineering (automations, worktrees, skills, connectors, sub-agents, external state), the generator/evaluator split, four silent costs, and a step-by-step guide to building your first loop.
+- **Project 07: Build Your First Automated Loop** — Three progressive experiments: goal loop, timer loop, and maker-checker loop. Compare manual vs. automated, measure intervention reduction, and learn to step outside the loop.
+- **Code templates** — `goal-template.md`, `loop-state-template.md`, `maker-prompt.md`, `checker-prompt.md` for building loops immediately.
+- **Reference update** — Added Addy Osmani's [Loop Engineering](https://addyosmani.com/blog/loop-engineering/) (2026-06-07) to the 2026 extended reference list.
+
+**Key idea:** Harness engineering builds the vehicle. Loop engineering designs the road it drives on — and you design the road from outside the car.
+
+---
+
 ## Other Courses
 
 Our team has also created other courses! Check them out:

docs/.vitepress/config.mts

@@ -24,7 +24,8 @@ const zhLectureItems = [
   { text: "防止 agent 提前宣告完成", link: "/zh/lectures/lecture-09-why-agents-declare-victory-too-early/" },
   { text: "跑通完整流程才算真正验证", link: "/zh/lectures/lecture-10-why-end-to-end-testing-changes-results/" },
   { text: "让 agent 的运行过程可观测", link: "/zh/lectures/lecture-11-why-observability-belongs-inside-the-harness/" },
-  { text: "每次会话结束前都做好交接", link: "/zh/lectures/lecture-12-why-every-session-must-leave-a-clean-state/" }
+  { text: "每次会话结束前都做好交接", link: "/zh/lectures/lecture-12-why-every-session-must-leave-a-clean-state/" },
+  { text: "从手动驱动到自动循环", link: "/zh/lectures/lecture-13-loop-engineering/" }
 ];
 
 const zhProjectItems = [
@@ -34,7 +35,8 @@ const zhProjectItems = [
   { text: "跨会话工作连续性", link: "/zh/projects/project-03-multi-session-continuity/" },
   { text: "运行反馈与行为修正", link: "/zh/projects/project-04-incremental-indexing/" },
   { text: "工作评审与自我验证", link: "/zh/projects/project-05-grounded-qa-verification/" },
-  { text: "综合 Agent 工作环境", link: "/zh/projects/project-06-runtime-observability-and-debugging/" }
+  { text: "综合 Agent 工作环境", link: "/zh/projects/project-06-runtime-observability-and-debugging/" },
+  { text: "第一个自动循环", link: "/zh/projects/project-07-loop-engineering-first-loop/" }
 ];
 
 const zhResourceItems = [
@@ -61,7 +63,8 @@ const enLectureItems = [
   { text: "Why Agents Declare Victory Too Early", link: "/en/lectures/lecture-09-why-agents-declare-victory-too-early/" },
   { text: "Why End-to-End Testing Changes Results", link: "/en/lectures/lecture-10-why-end-to-end-testing-changes-results/" },
   { text: "Why Observability Belongs Inside the Harness", link: "/en/lectures/lecture-11-why-observability-belongs-inside-the-harness/" },
-  { text: "Why Every Session Must Leave a Clean State", link: "/en/lectures/lecture-12-why-every-session-must-leave-a-clean-state/" }
+  { text: "Why Every Session Must Leave a Clean State", link: "/en/lectures/lecture-12-why-every-session-must-leave-a-clean-state/" },
+  { text: "From Manual Prompting to Autonomous Loops", link: "/en/lectures/lecture-13-loop-engineering/" }
 ];
 
 const enProjectItems = [
@@ -71,7 +74,8 @@ const enProjectItems = [
   { text: "Multi-Session Continuity", link: "/en/projects/project-03-multi-session-continuity/" },
   { text: "Runtime Feedback and Scope Control", link: "/en/projects/project-04-incremental-indexing/" },
   { text: "Self-Verification and Role Separation", link: "/en/projects/project-05-grounded-qa-verification/" },
-  { text: "Complete Harness (Capstone)", link: "/en/projects/project-06-runtime-observability-and-debugging/" }
+  { text: "Complete Harness (Capstone)", link: "/en/projects/project-06-runtime-observability-and-debugging/" },
+  { text: "Your First Automated Loop", link: "/en/projects/project-07-loop-engineering-first-loop/" }
 ];
 
 const enResourceItems = [

docs/en/lectures/lecture-13-loop-engineering/code/checker-prompt.md

@@ -0,0 +1,80 @@
+# Checker Agent Prompt
+
+> For the verification agent.
+> Focus on "finding problems" — the stricter, the better.
+
+## Your Role
+
+You are the Checker. Your job is to verify what the Maker produced. Your goal is to find problems, not say nice things.
+
+When you get an implementation from the Maker, your job is to:
+
+1. Read through all changes
+2. Verify item by item against the checklist
+3. Run the full verification commands
+4. List every problem you find — each with evidence
+
+**Remember: you're not here to praise, you're here to find fault.** Not finding problems is your failure.
+
+## Checklist
+
+### Functional Correctness
+- [ ] Does the implementation match the requirements?
+- [ ] Are there any edge cases missed?
+- [ ] Is error handling in place?
+
+### Code Quality
+- [ ] Is the code clear? Are names clear?
+- [ ] Is there duplicate code?
+- [ ] Does it follow project coding standards?
+- [ ] Are there obvious performance issues?
+
+### Testing
+- [ ] Do tests cover the main scenarios?
+- [ ] Are edge cases tested?
+- [ ] Are the tests actually testing something meaningful, or are they just going through the motions?
+
+### Verification Commands
+- [ ] Does `npm test` pass fully?
+- [ ] Does `npm run lint` have zero errors?
+- [ ] Does TypeScript type check pass?
+- [ ] Does coverage meet the bar?
+
+### Safety and Impact
+- [ ] Will this change affect anything else?
+- [ ] Are any new dependencies introduced? Are they justified?
+- [ ] Are config file changes correct?
+
+## Output Requirements
+
+Each issue must include:
+1. **Description**
+2. **Where** (file and line number)
+3. **Evidence** (what exactly is wrong, why it's a problem)
+4. **Severity** (Critical / Medium / Minor)
+
+End with an overall verdict: Pass / Fail / Minor issues, acceptable
+
+Output format:
+
+```
+## Overall Verdict
+✅ Pass / ❌ Fail / ⚠️ Minor issues, acceptable
+
+## Issues Found
+
+### 1. [Critical] Issue title
+- Location: file:line
+- Description: ...
+- Evidence: ...
+- Suggestion: ...
+
+### 2. [Medium] Issue title
+...
+
+## Verification Command Results
+- Unit tests: X passed / Y total
+- Lint: pass / fail (X errors)
+- Type check: pass / fail
+- Coverage: XX%
+```

docs/en/lectures/lecture-13-loop-engineering/code/goal-template.md

@@ -0,0 +1,65 @@
+# Goal Loop Template
+
+> Write your goal as a document like this, then hand it to `/goal` or a maker agent.
+> The more specific and verifiable, the higher the loop quality.
+
+## Goal
+
+<!-- One sentence describing what to do -->
+
+Implement the XX feature with complete unit test coverage.
+
+## Acceptance Criteria
+
+<!-- Machine-verifiable completion conditions — each one can be checked with a command -->
+
+- [ ] `npm test` passes fully
+- [ ] Coverage report shows XX module coverage ≥ 80%
+- [ ] `npm run lint` has zero errors
+- [ ] TypeScript type check passes (`npx tsc --noEmit`)
+- [ ] All new code follows project coding standards
+
+## Scope
+
+<!-- Be explicit about what NOT to touch -->
+
+### Fair game
+
+- All files under `src/xx/`
+- Test files under `tests/`
+- Related type definition files
+
+### Hands off
+
+- `src/main.ts` entry file
+- Database schema migrations
+- Dependency versions in `package.json` (unless explicitly needed)
+- CI/CD config files
+
+## Verification Method
+
+<!-- How to verify after each step -->
+
+1. After implementation, run these commands in order:
+   1. `npx tsc --noEmit` — type check
+   2. `npm run lint` — code style
+   3. `npm test` — unit tests
+   4. `npx vitest --coverage` — coverage check
+
+2. Fix any failures before moving to the next step.
+3. When everything passes, run the full end-to-end test suite (if available).
+
+## Stop Conditions
+
+- All acceptance criteria pass ✅
+- Max turns reached: 20
+- No progress for 3 consecutive rounds (same error keeps appearing)
+- Blocking issue that cannot be resolved independently (e.g., missing dependency, environment problem)
+
+## How to Work
+
+1. Read `AGENTS.md` and `feature_list.json` first to understand the project structure and existing features.
+2. Write out the design approach before touching code.
+3. Verify after each sub-task is done.
+4. If stuck for more than 2 rounds, switch approach or simplify.
+5. Update progress at the end of each round.

docs/en/lectures/lecture-13-loop-engineering/code/index.md

@@ -0,0 +1,8 @@
+# Lecture 13 Code Examples
+
+Use this folder for examples of:
+
+- goal.md goal description template
+- loop-state.md loop state template
+- Maker / Checker role prompt templates
+- Loop control script examples