Pi Coding Agent - Visual Plan Mode Extension

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: Pi Coding Agent - Visual Plan Mode Extension
- URL: https://www.youtube.com/watch?v=XqFun9XCXPw
- Topic: Codex + Claude Workflows
- My current learning frame: Use this codex + claude workflows video to extract the core workflow, identify the useful mechanism, and turn the demo into a reusable operating artifact.
- Why this matters: New playlist item from Michael; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:00 / Evidence 1: "planetator which creates a planning a plan mode like extension for pi and the plan mode works very similarly to cloud code except you benefit from the ability to annotate plans in the UI which will show you..."
- 0:32 / Evidence 2: "repo, try to search and explore. It'll ask you questions and then it will write the plan to a file. Um, similar to clock code, there's a there's a question um answer period, but I'll just tell it..."
- 1:48 / Evidence 3: "know, current implementations of the UI as well. Um, what we can now do is send that feedback. It'll auto close and the agent will correct the plan based on my feedback. It's a very simple UX. Once..."

Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A routing matrix for when to use Codex, Claude, browser checks, or manual review.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Inspect -> Plan -> Edit -> Verify -> Review -> Route
   - 3 concrete examples that apply the video idea to real agentic work
   - 2 failure modes the video helps prevent
   - a checklist I can use the next time I run Codex or Claude
   - one practical exercise with a clear done signal
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.

Quality bar:
- Make this specific to "Pi Coding Agent - Visual Plan Mode Extension", not a generic Codex + Claude Workflows essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.