A maintainer walks through the Obsidian Task Manager 1.1.0 release, demoing concrete UX upgrades — week numbers across views, a configurable first day of the week, a lighter sidebar widget, a status picker, smoother mobile list updates, shift-click bulk selection, and a fully rebuilt Kanban board now controllable via an MCP server.
Antone Heyward11 minTranscript found
Quick learning frame
Read this before watching.
Creative automation uses agents to accelerate production while keeping human taste in story, pacing, selection, and critique.
New playlist item from Antone Heyward; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to evaluate a task-management plugin's release notes against your own workflow — spotting which mobile, calendar, and Kanban changes matter to you and how to drive the board through an MCP/AI integration.
Watch for the shift from claim to mechanism. The learning value is the point where the transcript reveals a repeatable action, tool boundary, context move, review habit, or artifact.
Concept diagram
Where this video fits.
01Brief
02Source
03Generation
04Selection
05Edit
06Taste Review
Deep lesson
Turn this video into working knowledge.
1,754 cleaned transcript words reviewed across 460 timed caption segments.
Thesis
NEW - Obsidian Task Manager Release 1.1.0 teaches a practical creative automation move: A maintainer walks through the Obsidian Task Manager 1.1.0 release, demoing concrete UX upgrades — week numbers across views, a configurable first day of the week, a lighter sidebar widget, a status picker, smoother mobile list updates, shift-click bulk selection, and a fully rebuilt Kanban board now controllable via an MCP server.
The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.
0:35
Calendar config tweaks
“also in the month view is shown along the side here. There was also a request to have the first day of the month be configurable that has been added. So if we come in here into the...”
1.1.0 adds week numbers shown across the 3-day, week, day, agenda, list, and month views, plus a configurable first day of the week (toggle Sunday vs Monday in Task Manager settings) — but the calendar only reflects a first-day change after you switch the view to force a refresh. Open the plugin settings, switch the first day of the week between Sunday and Monday, then change the view to see the week-number column update and confirm the refresh behavior for yourself.
4:57
Mobile and list UX
“this popup in the beginning that has all of the different configuration and everything in it. I tried to put everything right here on the board that you need to change. So, if we want to come in...”
The list view gains a status picker (better than the checkbox, which only toggles open/complete, especially on mobile and when many statuses exist) and now updates only the changed element when you complete a task, so the list no longer jumps back to the top; the table view also adds shift-click range selection for bulk actions. In the list view, create a long list of tasks, mark several complete to feel the non-jumpy update, then use the status picker to move a task through multiple statuses.
7:17
Rebuilt Kanban + MCP
“have any tasks, let me actually create some dummy tasks here. I can create some tasks and let's take these and we can just drag them into the board directly and those update just like that. And once...”
The Kanban experience was redone: no upfront config popup, settings live on the board itself, new boards only ask for a name, the Done column is permanent (renameable but not removable) and defines completion, columns get colors/counts and a side pane for dragging in tasks — and you can now add, delete, edit, and list Kanban boards via the MCP server so AI can manage them. Create a new Kanban board, customize and color a couple of columns, drag tasks in from the side pane, then try driving a board operation (create or list) through the MCP server.
01
Brief
Start with this video's job: A maintainer walks through the Obsidian Task Manager 1.1.0 release, demoing concrete UX upgrades — week numbers across views, a configurable first day of the week, a lighter sidebar widget, a status picker, smoother mobile list updates, shift-click bulk selection, and a fully rebuilt Kanban board now controllable via an MCP server. Treat "Brief" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:35, where the video says: “also in the month view is shown along the side here. There was also a request to have the first day of the month be configurable that has been added. So if we come in here into the...”
02
Source
Use "Source" to locate the part of the creative automation workflow the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 4:57, where the video says: “this popup in the beginning that has all of the different configuration and everything in it. I tried to put everything right here on the board that you need to change. So, if we want to come in...”
03
Generation
Turn "Generation" into the reusable artifact for this lesson: A creative workflow board with critique criteria and review checkpoints. This is where watching becomes something you can inspect and reuse.
04
Selection
Use "Selection" as the application surface. Decide whether the idea touches a browser flow, a local file, a model choice, a source document, a UI, or a review step.
05
Edit
Use "Edit" to prove the lesson. The evidence should connect back to the video title, transcript anchors, and a concrete output, not a generic best-practice claim.
06
Taste Review
Use "Taste Review" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.
Example
Source-backed work packet
Convert the video into a scoped task that includes the transcript claim, target workflow, acceptance criteria, and proof. The output should be a creative workflow board with critique criteria and review checkpoints..
Example
Claim vs. demo brief
Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the workflow.
Example
Teach-back module
Transform the lesson into a definition, a mechanism diagram, one misconception, one practice exercise, and a check-for-understanding question.
Do not learn it wrong
Treating the title as the lesson without checking what the transcript actually says.
Letting the prompt drift into generic advice that could apply to any video in the playlist.
Copying the tool setup without identifying the operating principle that transfers to your own stack.
Skipping the artifact, which means the learning never becomes operational or inspectable.
Do not count this as learned until these are true.
01
State the transcript-backed claim in your own words: A maintainer walks through the Obsidian Task Manager 1.1.0 release, demoing concrete UX upgrades — week numbers across views, a configurable first day of the week, a lighter sidebar widget, a status picker, smoother mobile list updates, shift-click bulk selection, and a fully rebuilt Kanban board now controllable via an MCP server.
02
Explain the practical stakes without hype: New playlist item from Antone Heyward; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Brief -> Source -> Generation -> Selection -> Edit -> Taste Review sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A creative workflow board with critique criteria and review checkpoints.
Put it into practice
Give this grounded prompt to Codex or Claude after watching.
You are helping me turn one specific YouTube video into real, durable learning.
Source video:
- Title: NEW - Obsidian Task Manager Release 1.1.0
- URL: https://www.youtube.com/watch?v=AvuuLq10IhQ
- Topic: Creative Automation
- My current learning frame: Install or update to Task Manager 1.1.0, set your preferred first day of the week, build a Kanban board with custom colored columns and the permanent Done column, then create or list that board through the MCP server to see the AI-driven workflow end to end.
- Why this matters: New playlist item from Antone Heyward; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:35 / Evidence 1: "also in the month view is shown along the side here. There was also a request to have the first day of the month be configurable that has been added. So if we come in here into the..."
- 2:56 / Evidence 2: "and it works very well on mobile. So, that's one of the other benefits. Also, I've added the time that the task will either start if there's a start time and if there's no start time, it will..."
- 4:57 / Evidence 3: "this popup in the beginning that has all of the different configuration and everything in it. I tried to put everything right here on the board that you need to change. So, if we want to come in..."
- 7:17 / Evidence 4: "have any tasks, let me actually create some dummy tasks here. I can create some tasks and let's take these and we can just drag them into the board directly and those update just like that. And once..."
- 9:16 / Evidence 5: "these. I have a couple other requests for the next version. One of the top of the list is to automate archiving of completed tasks. So, that's something of importance, let me know down in the comments. And..."
- 10:48 / Evidence 6: "buy me a coffee link that is available. So if you like this plugin, love this plugin, give back and show it in the way of contribution. And with that out of the way, until the next time,..."
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 creative workflow board with critique criteria and review checkpoints.
5. Include:
- a plain-English definition of the core idea
- a diagram or structured model using this sequence: Brief -> Source -> Generation -> Selection -> Edit -> Taste Review
- 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 "NEW - Obsidian Task Manager Release 1.1.0", not a generic Creative Automation 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.
Misconceptions
What to stop believing.
Creative AI removes the need for taste.
It increases the need for taste because output volume explodes.
The best prompt is enough.
References, critique, iteration, and post-production matter just as much.
Practice studio
Learning only counts when you make something.
01
Transcript evidence map
Separate what the video actually says from what you already believe about the topic.
3 source-backed takeaways with timestamps, confidence, and a transfer note.02
One useful artifact
Apply the video to a real workflow and produce a creative workflow board with critique criteria and review checkpoints..
A reusable artifact with a done signal and one verification step.03
Teach-back card
Explain the lesson to someone who has not watched the video yet.
A 90-second explanation, one diagram, one example, and one misconception to avoid.
Recall check
Answer first, then reveal — without rewatching.
After changing the first day of the week between Sunday and Monday in Task Manager settings, why does the calendar still show the old first day, and what do you have to do to make it update?
In the list view, how does the new status picker differ from the checkbox, and in what situations is it most useful?
In the rebuilt Kanban experience, which column is permanent and what is its role, and what specifically can you do with Kanban boards through the MCP server?
Source shelf
Use the video as a doorway, then verify with primary sources.
