add readme and finished docs

Author: kentcdodds

exercises/FINISHED.mdx

@@ -1,3 +1,47 @@
 # Engineering Judgement Workshop
 
 Hooray! You're all done! 👏👏
+
+## What you've practiced
+
+### 1. Building an MVP
+
+You practiced turning ambiguity into a concrete plan. That included defining
+the real problem, clarifying success criteria, surfacing constraints, choosing
+reasonable scope, and evaluating whether the implementation actually delivered
+the MVP you intended to build.
+
+### 2. Product Restraint
+
+You practiced resisting feature momentum. Instead of assuming every plausible
+request deserved implementation, you slowed down to qualify the request, look
+for missing evidence, consider narrower alternatives, and recommend the smallest
+response worth shipping.
+
+### 3. Protect the User Experience
+
+You practiced evolving a product without casually degrading it. You identified
+the user flows that mattered most, defined the UX invariants that had to stay
+intact, and used those guardrails to judge whether a change improved continuity
+or quietly added friction.
+
+## The big takeaway
+
+Implementation matters, but judgment shapes implementation before the first line
+of code and after the last line ships.
+
+The durable skill is being able to explain:
+
+- what problem you are actually solving
+- what constraints shaped the decision
+- what tradeoffs you made on purpose
+- what risks you accepted or mitigated
+- how you know the outcome helped or harmed the product
+
+<callout-info>
+	The point of this workshop was never perfect prediction. It was to make your
+	reasoning explicit enough that you can learn from the gap between intent and
+	outcome.
+</callout-info>
+
+Nice work.

exercises/README.mdx

@@ -1 +1,63 @@
-# Engineering Judgement Workshop
+# Engineering Judgement Workshop 🧑‍⚖️
+
+👨‍💼 Hello, my name is Peter the Product Manager. I'm here to help get you
+oriented and to give you your assignments for the workshop.
+
+This workshop is about a skill that becomes more valuable as implementation gets
+easier: engineering judgment.
+
+You'll work on a lightweight scheduling product and practice the part of the
+job that happens before, around, and after code is written:
+
+- clarifying ambiguous goals
+- surfacing constraints and assumptions
+- defining success before implementation starts
+- deciding whether a request is worth shipping at all
+- protecting core user experience as the product evolves
+- evaluating whether the implementation actually matched the intent
+
+This is not a workshop about prompt tricks, framework trivia, or shipping the
+most code the fastest. The point is to build durable judgment that still
+matters even when AI can generate most of the implementation.
+
+## What you'll work through
+
+### 1. Building an MVP
+
+You'll start with an ambiguous product request and turn it into a focused,
+shippable MVP. The work is to define what "good enough" means, ask better
+questions, choose a reasonable starter architecture, and judge the final result
+against the plan you created.
+
+### 2. Product Restraint
+
+Next, you'll confront a plausible feature request and slow the team down on
+purpose. Instead of rushing into implementation, you'll qualify the request,
+separate evidence from momentum, and decide whether the right move is to ship,
+narrow, defer, or reject.
+
+### 3. Protect the User Experience
+
+Finally, you'll evolve the product without losing the experience that made it
+valuable in the first place. Before implementation, you'll define the user
+flows and UX invariants that must not degrade, then use those guardrails to
+evaluate whether the change was actually an improvement.
+
+## How to approach the workshop
+
+In each exercise, focus on making your reasoning visible:
+
+1. Ask clarifying questions.
+2. Write down assumptions, constraints, and success criteria.
+3. Make scope and tradeoffs explicit.
+4. Treat implementation as evidence to inspect, not the only output that
+   matters.
+5. Compare the final system against your original intent and critique the gaps.
+
+<callout-info>
+	A strong result in this workshop is not "I added the most features." It is "I
+	made the right tradeoffs for the information available, and I can explain
+	why."
+</callout-info>
+
+When you're ready, mark this page complete and start with the first exercise.

package.json

@@ -2,7 +2,7 @@
   "name": "engineering-judgement",
   "private": true,
   "epicshop": {
-    "title": "Engineering Judgement Workshop",
+    "title": "Engineering Judgement Workshop 🧑‍⚖️",
     "subtitle": "Practice making better technical decisions under ambiguity",
     "githubRepo": "https://github.com/epicweb-dev/engineering-judgement",
     "subdomain": "engineering-judgement",