Skip to content

🚀 Plain AI Curriculum — Moonshot Kickoff Prompt

Use this prompt to start a fresh session for the Plain AI curriculum P0 moonshot. Copy the prompt below into a new Copilot CLI session. Reference docs are listed for the agent to read before planning.

The prompt (copy this — keep it short, sharp, intentional)

[[PLAN]]

Time to start the Plain AI Curriculum moonshot — P0 in cosmos-todo.

Read these first, in order:
1. learning-docs/docs/reference/plainai-roadmap.md  (full UX history + curriculum-era IA reshape sections E-J)
2. ~/.copilot/cosmos-todo.md  (P0 statement + cosmos-wide priorities)
3. ~/.copilot/plain-ai-voice-guardrail.md  (mandatory voice rules — every word must pass)
4. ~/.copilot/halt-plan.md  (how Halt was scoped + shipped — same approach for curriculum)
5. C:\ssClawy\plainai\content\paths.json  (the 4 reading paths — closest existing analog to lessons)
6. C:\ssClawy\plainai\build.mjs  (renderTopic, renderTrail — see how content types are templated)

Goal of this session: produce a complete plan for Plain AI Curriculum v1
in plan.md. Don't write code yet — plan only. Plan must include:

  • Audience scoping — pick ONE audience for v1 (e.g. parents, ESL learners,
    mid-career non-tech). Justify the choice. Future audiences are out of scope.
  • Lesson schema — what fields does a lesson have? How does it differ
    from a topic? (Likely: ordered, has-prerequisite, has-exercise/check-question,
    has-takeaway, audience-tagged.)
  • Course schema — how do lessons link into a sequence? (Probably similar
    to existing reading paths but with explicit lesson order and progress.)
  • Information architecture — new /learn/ tab in primary-nav, new
    /learn/<audience>/ landing, new /learn/<audience>/<lesson>/ pages.
    Doesn't break existing topics or /changes/.
  • Build pipeline — does build.mjs grow, or do we add build-curriculum.mjs
    (mirroring build-changes.mjs pattern)? Keep separation if possible.
  • Editorial workload — how many lessons for v1? (Suggest 5-7 to start.)
    Voice guardrail must apply to every lesson. Microsoft-recusal rule still applies.
  • The audience-triage homepage flip — when curriculum has its first
    lessons, the homepage flips from topics-first to "what brings you
    here?" 4-quadrant grid (item E in roadmap). Plan that as part of v1.
  • SEO + sitemap implications — new URL structure adds ~10-30 pages.

Output: plan.md with all of the above + numbered todos in SQL.

Voice guardrail enforcement: mum/dinner-table/12-year-old/honesty tests
on every piece of editorial copy. No "frontier", "ecosystem", "agentic",
"multimodal", "mass-market". Sush's voice = warm, friendly, plain English.

Honest take welcomed throughout. If something is the wrong shape, say so.

What this prompt buys

  • Plan-mode kickoff so the new session starts in design mode, not coding mode (avoids premature implementation).
  • Reference reading list ensures the new session has full context without re-explaining 6 hours of UX work.
  • Six concrete questions force the plan to address real ambiguities (audience, schema, IA, build pipeline, workload, IA flip).
  • Voice guardrail explicit in the prompt — non-negotiable from minute one.
  • Output target is plan.md in the new session, not code — leaves implementation for after Sush reviews and refines the plan.

When to start the new session

  • After a break (curriculum work needs fresh attention).
  • When you have ~2 hours minimum to plan + critique + iterate.
  • Before launching the new session, double-check the reference docs are committed and pushed to GitHub (so they're accessible from any working directory).

What "v1 done" looks like (success criteria)

When v1 lands you'll have: - One audience picked + justified - 5-7 lessons written and live at /learn/<audience>/<lesson>/ - A /learn/ landing page + /learn/<audience>/ start page - Primary-nav has a Learn link - Homepage shows the 4-quadrant audience-triage block - Voice guardrail honoured on every word - A clear "what's next" pointer for v2

The moonshot is real. P0 stands. Build the first audience well — the rest scales.

Created 6 May 2026 · 11:29 NZST · Session 9b67c31d-fca5-47fa-8b5a-b9515de99336