Hands-On Labs
You will complete three labs in this chapter, each scoped to be done in a sandbox or test tenant:
**Lab 1** — Load the smart-industry-architecture skill and complete a real working task from start to finish. Submit the artifact URL.
**Lab 2** — Run a follow-up sweep across GitHub. Produce the list of open items with owners and next dates.
**Lab 3** — Execute a handoff into another track. Either Full-Stack Engineer → engineering, or Full-Stack Engineer → PM, or Full-Stack Engineer → sales. The handoff is complete when the receiving side has everything they need to act without coming back to you.
How Eric talks about this
“show me the artifact”
Lab pass criterion. Every lab produces an artifact — a URL, a file, a record. The lab isn't done until the artifact is in the submission.
“done means shipped, not described”
Eric corrected me here. I said 'I would do X' instead of doing X. He pushed back: describing the work isn't doing the work. The lab fails if all you have is a plan.
“load smart-industry-architecture for this lab”
Each lab specifies which skill to load. Load it explicitly, then drive the work. Don't try to do it without the skill — you'll miss structural pieces.
Try these exact phrasings
Try it yourself
Complete all three labs in this chapter. For each lab: name the skill you loaded, paste the artifact URL, and write one sentence on what was harder than expected.
- all three labs submitted
- each lab has an artifact URL
- each lab names the skill loaded
Quick check
1. What proves a lab is done?
- a. A description of what you would do
- b. An artifact URL or file path
- c. A meeting recap
- d. A Slack message
Reveal answer
Labs require artifacts. Description ≠ doing. The artifact is the pass condition.
2. For each lab in this chapter, which skill must you load first?
- a. Whatever feels right
- b. The skill named in the lab spec
- c. All 19 skills
- d. None — just improvise
Reveal answer
Each lab specifies the skill to load. Load it explicitly. The lab is designed to exercise that skill's workflow.
3. What's the right move when a lab fails midway?
- a. Hide it and try again silently
- b. Document the failure, note what changed, retry with the corrected approach
- c. Ask Eric to do it for you
- d. Skip the lab
Reveal answer
Failures are part of the work. Document, learn, retry. Hidden failures cost more later.
Built 2026-07-31 · 3 teaching moments · 3 prompts