---
name: new-society-modules
description: Design and outline New Society classroom modules. Use when David asks to work on NS course outlines, module layouts, classroom structure, or Section 2/3 design.
user-invocable: true
---

# New Society Module Design Process

## Context Files (read all before starting)
1. `work/new-society/sprint.md` — sprint plan, master checklist, customer insights
2. `work/new-society/classroom.md` — full classroom structure, all outlines, open questions
3. `work/youtube/audience-research.md` — polls, customer DMs, positioning data

## Process
1. Read all 3 context files above
2. Identify which course/section David wants to work on
3. Ask David targeted questions to extract his thinking — provide 3-5 suggestions per question
4. After EVERY message from David, update `work/new-society/classroom.md` with all new context (decisions, variables, thinking, risks, bottlenecks)
5. Build module-by-module outlines based on David's answers
6. Repeat until the outline is complete

## Rules
- **David knows better.** Extract HIS taste, judgment, and knowledge. Do NOT force opinions or tell him what the outline should look like.
- **Ask questions, don't prescribe.** Seek to understand how David thinks. He knows the customers better than you.
- **3-5 suggestions per question.** Always give ideas/options for what YOU think is a great answer — but defer to David's judgment.
- **Be concise.** Short questions, short suggestions. No fluff.
- **Update classroom.md after EVERY message.** No exceptions. All context — decisions, open questions, variables, thinking, risks — lives in that one file.
- **Progressive depth.** Module length increases through the program:
  - Section 1 (Week 1-3): 1-5 min → 3-7 min → 5-10 min
  - Section 2 (Month 2-4): 5-10 min avg
  - Section 3 (Month 5-7): 5-10 min avg
- **15-25 modules per course** in Section 2 and 3.
- **RR = Retention Reminder** — place every 5-7 modules. Purpose: inspire, show the future is coming, learning this is not optional.
- **This is NOT a coding course.** It's agentic development. Never teach coding concepts directly. Keep it simple for non-technical people.
- **Each course needs a BIG WIN** — a single-sentence transformation students achieve by the end.
- **VPS constraint** — if there is a sponsor or platform requirement, include a few modules on VPS deployment (e.g. setting up OpenClaw on a VPS).