쉐도잉 연습: /wayfinder: Nothing is too big to plan anymore - 영상으로 영어 말하기 배우기
연습 모드 선택
각 모드는 전체 화면 연습실로 열립니다.
212 문장
문장이 너무 짧거나 길면 Edit를 눌러 조정하세요.
1
I think I've figured out a way to plan any size of work with an agent.
2
The existing planning tools that I was using and playing around with, even ones that I've created, felt too constrained, too tied to a single session.
3
I felt like I wasn't able to be ambitious enough.
4
And because of that, I was kind of constraining the stuff I was building to fit AI, which doesn't feel right.
5
This new approach doesn't have that limit.
6
You can plan enormous chunks of work, and it will orchestrate the planning over multiple types of sessions.
7
It knows that you can't make your way cleanly to the destination.
8
You have to clear the fog of war.
9
It understands dependent decisions and it even allows you to plan in parallel.
10
And the best thing about this is this is based on software fundamentals.
11
This is based on the fundamentals of planning work that I learned when I was a real developer before AI.
12
And I've packaged this all up into a skill that's available right now on my skills repo called Wayfinder.
13
So the way that I was planning work before was really tied into a single session.
14
It's to do with the grill me or the grill with doc skill that's in my skills repo.
15
That's still a super important primitive, but it's really just tied into a single session.
16
Some work is bigger than what you can fit into the context window
17
and especially the smart zone of the context window of the agent.
18
And you know that going in.
19
So you'll often take time ahead of these AI agent sessions to break it down into smaller chunks say, oh, I'll just bite off this little bit.
20
I'll just bite off this little bit.
21
But then what you'll find is, okay, I'm working towards planning and this bit of grilling, and then you reach a question that you can't answer, or you just find yourself lost in fog,
22
and all the time you're managing the smart zone, you're trying not to spend too many tokens.
23
This has been out there for a while, and people are freaking loving this thing.
24
One-shotted a prototype, it kept starting again and again for months.
25
I really hate the phrase one-shotting, but I think what he means is it really helped him out.
26
John here even built his own freaking harness because he liked the Wayfinder approach so much.
27
It's got this gorgeous little star map on it that kind of lets you take tasks as you go.
28
So it's been out there for a little while and I'm finally making the video that people want me to make.
29
What is Wayfinder?
30
How do you best use it?
31
Well, let's start by looking at how big work typically gets planned.
32
You have a start point, a point where you need to start from, a sort of vague idea, not really how to get there,
33
and you're trying to get to some kind of destination.
34
You know vaguely where you want to end up, but the steps between are super foggy.
35
You've no idea how to get.
36
This is true, by the way, in engineering, but it's also true in many walks of life where you're planning something ambitious.
37
And so the first thing you should probably do is have a grilling session about it.
38
Get the AI to interview you and figure out the sort of basic premise of where you're going.
39
Now, for some work, that's sufficient and you'll be able to get straight to your destination.
40
But for a lot of work, that will still leave you in a lot of fog.
41
What you might find is based on that initial grilling session, you need to do more sessions.
42
So you might have a prototyping session or you might have another grilling session, or it might need to go off and do some research as well.
43
Conceptually, what we're looking at here is a map.
44
We are creating a map of how we're getting to our destination.
45
This is why it's called Wayfinder.
46
We are finding our way to the destination.
47
And each of these things on the map, they are tickets.
48
Each ticket requires its own individual session with the agent.
49
So you might have a prototyping session, a grilling session, and a research session.
50
And all of those things are created and managed by Wayfinder.
51
And just a note here, yeah, this is just a single skill doing all this, and it works with any coding agent.
52
On its map, Wayfinder gives you a frontier of tickets here.
53
In other words, the decisions that it knows about so far.
54
And it also keeps track of everything that's in fog.
55
So things that are not quite able to be decided upon yet
56
because we haven't done the research or we don't have a prototype to look at
57
or we haven't done enough conversation, enough grilling.
58
At some point, all of the fog will be resolved
59
and then you'll have finally made enough decisions to finally get to your destination.
60
Wayfinder can not only manage the research, but it can also do tasks here too.
61
So if you need to set up some configuration
62
or you need to go out and talk to someone and actually go and run an errand, then Wayfinder can figure that out for you as well.
63
In other words, all of the complicated stuff that you might need to do while you're planning something big, Wayfinder orchestrates it all for you.
64
It keeps track of everything that's been done and it measures the fog of war for you, keeps track of all the frontier of things you can decide right now.
65
How does it keep track of it?
66
Well, it does it in your issue tracker.
67
In my public course video manager repo, here are all of the Wayfinder maps that I've done recently.
68
And you notice that if we look at this one, this is the big old map here.
69
And underneath it are 12 subtasks or sub-issues.
70
And these are the decision tickets.
71
So we can zoom down here and we can understand all of the decisions that have been made.
72
As decisions get made, then obviously they get resolved inside the ticket.
73
So in this one, this is a sub-issue, close the clips during publish race, and we resolved it with a discussion a couple of weeks ago.
74
That resolution also gets written back up to the parent map.
75
So if we look back up here, we can see that a small version of that also gets written in the map.
76
And so Wayfinder is keeping track of all the decisions that have been made, all the prototypes that have been created, all the tasks that have been done.
77
And by the way, even though I'm using GitHub for this, my skills are issue tracker agnostic.
78
so you can use it with any issue tracker you like.
79
You just need to do a little bit of configuration via setup matpocot skills.
80
Use it with linear, use it with JIRA, use it with literally whatever you like.
81
The very first thing you'll need to decide when you kick off a new Wayfinder session is the destination.
82
For instance, in this one, I was adding a command palette with a bunch of new actions into my application
83
and what I ended up wanting was a buildable spec.
84
So I wanted a specification for this command K command palette in the CVM diagram window.
85
So I started it off like this.
86
I invoked the Wayfinder skill and then I gave it a description of what I wanted.
87
I would like the ability in the CVM to add an icon picker.
88
Not only that, I want the ability to search other diagrams.
89
I want the ability to copy things from the diagram and save them as, you know, big old chunk of work.
90
It went through and explored the repo and it invoked the grilling skill and it grilled me about what I wanted.
91
It first asked me what done looks like, whether I wanted a spec and it recommended a spec.
92
That's good.
93
And then it asked me a few initial questions before then going and creating some tickets and the first map.
94
And it created the other tickets as sub issues.
95
So we kicked off with seven tickets immediately.
96
However, only three of those tickets were takeable right now.
97
So figure out where icon names come from, component storage schema and palette information, architecture and grid keyboard.
98
I don't remember that one.
99
And so what I did was I then worked through each of those tickets in a new session.
100
The way I did that was I just called Wayfinder on that ticket name.
101
I did it in a slightly fancier way where I actually have a handoff skill
102
that automatically wrote me a prompt and spawned a clawed subagent.
103
But what it was essentially doing is just calling the Wayfinder skill on this map
104
and on the specific ticket wherever it was.
105
Yeah, here it is.
106
Here's your ticket.
107
Transpar Lucid SVG Geometry to Path Builder and it just mentions the full ticket name.
108
So this is how you work through a Wayfinder map.
109
You do an initial Wayfinder prompt just to chart the map and figure out the next ticket.
110
And then for each ticket, you say Wayfinder with the ticket URL.
111
So you use Wayfinder for both, both for charting the map initially and then walking through each ticket.
112
As you can probably see from this diagram, tickets can have different types.
113
And there are four types.
114
And these ticket types are actually brought into the issue tracker themselves.
115
So we actually have Wayfinder Research, which is a ticket type.
116
Research tickets are where the agent needs to go off and find some information and bring it back.
117
it usually kicks it off immediately.
118
So you don't actually need to watch it.
119
It does it in a sub agent and then reports back.
120
Prototype tickets, which are the next type here,
121
create a prototype, which is so unbelievably invaluable for really seeing things come to life as you're planning.
122
I've done a whole extra video on this, on how important prototypes are, and it reuses the prototype skill from that video.
123
Some folks look at Wayfinder and they think, God, that's a lot of planning.
124
Doesn't that look like waterfall?
125
And the prototypes are the way that you prevent it from becoming waterfall.
126
Huge amounts of low fidelity upfront planning.
127
A prototype is a high fidelity way to get feedback on what you're actually building.
128
And the fact that Wayfinder encourages you to build so many prototypes means that the output is unbelievably good.
129
So, so far we've got research, prototype, obviously there are grilling ones as well.
130
So, grilling sessions.
131
And this is just where you need a discussion over maybe an implementation detail, over a particular aspect of the plan.
132
And the final type of ticket are tasks.
133
These are things that need to be done in the real world, stuff that the agent can't quite do itself, or possibly sometimes the stuff agent can do itself,
134
but is scheduled behind other work.
135
One really cool thing about Wayfinder is the way that it establishes blocking relationships between tickets, because some decisions can only be made once other decisions are made.
136
And so what you end up with is here, we've got 14 out of 17 done on this map.
137
So a lot of work done, but we've still not built the skill that this whole map is built around.
138
And once we built the skill, then we actually need to revisit some other stuff based on how the skill works and how it actually improves things.
139
And so what you're doing a lot of the time when you're working through a Wayfinder map is going, OK, I've resolved that ticket.
140
Let's see how this opens up new tickets.
141
What has the frontier moved to?
142
So then once the map is complete, what do you then go and do with it?
143
Well, this one, because its detonation was a spec, the Wayfinder map is probably a little bit too dense to create a spec.
144
So what I like to do is create a spec from the map.
145
This was the spec that I created from it.
146
And you can see it's basically the same setup as I've had before.
147
I literally just called to spec on the Wayfinder map and it pulled in this enormous document
148
with basically all of the decisions that have been pulled from the Wayfinder map into this GitHub issue.
149
The initial draft was actually too large for GitHub's character limit.
150
So that kind of tells you how big it was.
151
And from there, I turned it into tickets using my usual approach, which is to spec and then to tickets.
152
In other words, Wayfinder fits in just in exactly the same place that grill with docs does in my usual approach.
153
So instead of doing grill with docs and then doing to spec and to tickets, You're spending a lot more time in Wayfinder, creating this enormous map, and then taking that map,
154
turning it to spec, turning it to tickets, and then implementing each ticket, and then running code review at the end.
155
The really cool thing about the Wayfinder setup is that the specs that it creates are so dense, and they all link back to the original decision tickets.
156
So you can actually go and the agent can go and view the primary source if it's confused about anything.
157
That was always a kind of weakness with Grill with Docs, which is that you were really relying on the spec to be the source of truth,
158
but the spec is always just a summary of what was actually said in the meeting.
159
Whereas now with Wayfinder you've actually got access to that primary source, which is amazing.
160
So that is Wayfinder.
161
It's a way of mapping huge chunks of work by planning things out really in detail ahead of time.
162
It can handle prototyping, can handle research, can handle arbitrary tasks, can handle discussions too.
163
Let's jump into an FAQ now of frequently asked questions that I get when people ask me about Wayfinder.
164
One is, this is way too much process.
165
This way too heavy for the kind of work that I do.
166
When should I actually use it?
167
Well, the answer to this is if you think the work
168
that you're doing can be completable and planable in a single session, then plan it in a single session.
169
If you kind of already know the way to your destination, then there's no need to use Wayfinder
170
because you can just path your way there in a single session and just figure it out.
171
Wayfinder is for the cases where you have the fog of war.
172
You have no idea quite where to go, and you just need to start and then see where you get to.
173
By the way, I've actually been using Wavefinder for non-coding tasks, so I've been meaning to put up a garden office in my garden, and I've been using Wavefinder for that.
174
So it's commissioning a site survey, figuring out all that stuff, figuring out who to contact, doing all the research, finding the different firms that could build it.
175
It's awesome.
176
Another response people have to Wavefinder is, this is SDD, this is spec-driven development, and I don't want to do spec-driven development.
177
I don't want to spend all this time putting together a spec.
178
This seems bananas.
179
Well, the way I think of specs is really just a destination for a multi-session piece of work.
180
In other words, we have a huge task down here, let's say task number four, that we're trying to schedule over multiple agent sessions because it's just too big.
181
And what we want to do is we need a spec so that we can, when we get to the end, figure out where we were going.
182
That's all a spec is in this context.
183
It's just a destination document to handle this multi-session work.
184
And then each session is done in an implementation ticket.
185
Also, this is people get confused when they first use Wavefinder because they go, right, it's creating some tickets.
186
Aren't we supposed to do the tickets later?
187
These are kind of implementation tickets versus decision tickets.
188
So in Wavefinder, you have decision tickets.
189
These are implementation tickets.
190
So the difference between my approach and most other approaches is that people, when they get to the end of this, they will keep that spec around somewhere.
191
For me, I close the issue you continue the spec and the spec is gone.
192
It's gone from my repository.
193
I rarely, if ever, refer to it again.
194
Once the spec is present in the code, then you can just delete the spec.
195
Whereas people who do spec-driven development go back to the spec and edit it and modify it.
196
There are lots of approaches to spec-driven development, so I'm probably annoying someone with that.
197
But what I'm essentially trying to say is that these specs are non-persistent.
198
With that, folks, I recommend you go off and you chart your own awesome, foggy idea.
199
I have found Wayfinder just so liberating in
200
that it just lets me get started and it handles all of that difficult decision for me.
201
I've been using it to plan courses, been using it to do engineering work, been using it to build a garden office.
202
It is just awesome.
203
The cool thing about it is that the destination is totally up to you, whether you want it to create a spec that you then run through an AFK agent, which is what I do,
204
or if you just want it to implement the work for you in tasks, then it totally can.
205
There is no more fun feeling than starting a new Wayfinder session and knowing that you're going to see something awesome, but not quite knowing how you're going to get there.
206
If you're into this stuff and if you want to keep up with my skills, then you should check out this seven lesson free course that I've put out on AI skills for real engineers,
207
which is on my AI hero site.
208
I'll add the link below.
209
This lets you build up a repeatable workflow that you can ship great work and it's all built on solid software fundamentals.
210
Thanks so much for hanging out.
211
It is always fun filming these sessions and I'm so glad that people are enjoying Wayfinder so much.
212
Cheers pals, I will see you in the next one.
앱 다운로드
유창하게 말하는 데 필요한 모든 것
AI 발음 평가문장마다 점수 확인
IPA 발음 연습모든 소리 마스터
단어 학습나만의 단어장 만들기
단어 게임놀면서 외우기
📺 같은 채널
C12
New Skills! v1.2 brings /wait-what, /writing-for-agents, and fixes /grill-me
British AccentDaily ConversationWorking Adults
C14
New Skills! v1.3 brings /pr, /implement-spec, and /retro
Business EnglishWorking Adults
C14
New Skills! v1.1 brings /wayfinder, /research, /implement, /to-spec, /to-tickets
British AccentBusiness EnglishUniversity StudentsWorking Adults
C13
mattpocock/skills: A complete AI Coding workflow, end-to-end
British AccentBusiness EnglishUniversity StudentsWorking Adults
B23
I was an AI skeptic. Then I tried plan mode
British AccentBusiness EnglishUniversity StudentsWorking Adults
C15
The 7 phases of AI-driven development
British AccentBusiness EnglishUniversity StudentsWorking Adults
C12
How to actually force Claude Code to use the right CLI (don't use CLAUDE.md)
British AccentBusiness EnglishUniversity StudentsWorking Adults
C13
Learn anything with the /teach skill
British AccentBusiness EnglishUniversity StudentsWorking Adults
C16
5 Claude Code skills I use every single day
British AccentBusiness EnglishUniversity StudentsWorking Adults
C13
Most devs don't understand what agents are
British AccentDaily ConversationUniversity StudentsWorking Adults
C15
Can Cursor's HARDCORE Review Skill Stop The Slop?
British AccentBusiness EnglishUniversity StudentsWorking Adults
C12
Most devs don't understand how LLM tokens work
British AccentBusiness EnglishUniversity StudentsWorking Adults
C1New Skills! /handoff, /prototype, /review and /writing-* | Skills Changelog
British AccentBusiness EnglishUniversity StudentsWorking Adults
✨ 추천 영상
B21
15 문장
Focus on one thing per quarter to succeed faster - click link in bio for my new app :)
British AccentBusiness EnglishUniversity StudentsWorking Adults
B217 문장
Did someone say... SecondBrain?
American AccentBusiness EnglishUniversity StudentsWorking Adults
B26
139 문장
Is it time to dismantle the puzzle?
Business EnglishDaily ConversationUniversity Students
C15
222 문장
The Multi-Agent Architecture That Actually Ships — Luke Alvoeiro, Factory
Business EnglishUniversity StudentsWorking Adults
B25
214 문장
Launch Pads and Prep at Starbase (and Beyond) - Starship Summary
Business EnglishUniversity StudentsWorking Adults
B23
46 문장
OpenAI’s new browser feels familiar…
American AccentBusiness EnglishUniversity StudentsWorking Adults
B27
73 문장
How to Never Run Out of Things to Say
Business EnglishDaily ConversationUniversity Students
B23
548 문장
Sam Altman x Nikhil Kamath: How to Win When AI Changes Everything | People by WTF | Episode 13
Business EnglishUniversity StudentsWorking Adults
B21
31 문장
Proposing a New Project: The Business Case for Warehouse Automation
British AccentBusiness EnglishWorking Adults
C12
540 문장
Incremental Cooking in UE 5.7: A Dive Into the UE Cook Pipeline | Unreal Fest Chicago 2026
Business EnglishUniversity StudentsWorking Adults
이 레슨의 어휘와 말하기 포인트
이 B2 수준 말하기 레슨은 영상 “/wayfinder: Nothing is too big to plan anymore”을(를) 바탕으로 합니다. 가장 자주 반복되는 단어는 다음과 같습니다: ticket, Wayfinder, spec, session, map. 이 영상에는 섀도잉할 문장 212개와 단어 3154개가 있습니다. 말하는 구간의 길이는 15:08입니다. 화자는 분당 약 208단어로 빠르게 말하므로 연음과 약하게 발음되는 소리가 많습니다. 단어의 84%가 영어에서 가장 많이 쓰이는 3,000단어에 속합니다. 나머지는 연습 전에 미리 확인해 두세요.
이 영상의 핵심 어휘
영상에서 가장 어려운 단어 15개를 발음, 뜻과 함께 정리했습니다.
| 단어 | 발음 | 뜻 |
|---|---|---|
| grill 명사 | /ɡɹɪl/ | 그릴 |
| chunk 명사 | /t͡ʃʌŋk/ | 조각 |
| diagram 명사 | /ˈdaɪ.ə.ɡɹæm/ | 다이어그램, 도표 |
| resolve 동사 | /ɹɪˈzɑlv/ | 해결하다 |
| spectacles 명사 | /ˈspɛktəkl̩z/ | 안경 |
| palette 명사 | /ˈpælɪt/ | 팔레트 |
| frontier 명사 | /ˈfɹʌntɪə/ | 경계, 국경 |
| constrain 동사 | /kənˈstɹeɪn/ | 제한, 구속 |
| waterfall 명사 | /ˈwɔːtəfɔːl/ | 폭포 |
| prompt 동사 | /pɹɑmpt/ | 부추기다 |
| ambitious 형용사 | /æmˈbɪʃ.əs/ | 야심적 |
| dense 형용사 | /ˈdɛns/ | 짙다 |
| icon 명사 | /ˈaɪ.kɑn/ | 이콘, 성상 |
| errand 명사 | /ˈɛɹənd/ | 심부름 |
| liberate 동사 | /ˈlɪbəˌɹeɪt/ | 해방(解放)하다 |
영상에 나오는 구동사
| 단어 | 뜻 |
|---|---|
| go out 동사 | 나가다 |
| put together 동사 | 조립하다 |
따라 말해 볼 만한 문장
영상에 나오는 짧고 완결된 문장으로, 일상 대화에서 그대로 쓸 수 있습니다:
- I'll just bite off this little bit.
- How do you best use it?
- You've no idea how to get.
- When should I actually use it?
- Aren't we supposed to do the tickets later?
이 영상의 문법
화자가 가장 많이 쓰는 문형을 영상 속 실제 표현과 함께 정리했습니다.
| 문형 | 영상 속 표현 |
|---|---|
| 현재완료진행 have/has been + -ing — 전에 시작해 지금도 계속되는 동작 | I've actually been using · I've been using |
| 현재완료 have/has + 과거분사 — 과거의 일이 지금도 관련이 있을 때 | I've figured · I've created · I've packaged |
| 수동태 be + 과거분사 — 누가 하는지보다 무슨 일이 일어나는지에 초점 | is based · are created · be decided |
| 관계절 who / which + 절 — 사람이나 사물에 대한 추가 정보 | Research, which is · tickets, which are · prototype, which is |
주의할 발음
화자는 you're, I've, I'm 같은 축약형과 약화된 형태를 64번 사용합니다. 들리는 대로 짧게 발음하세요.
- “sh”와 “zh” 소리: speculation /ˌspɛk.jəˈleɪ.ʃən/, ambitious /æmˈbɪʃ.əs/, configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/, detonation /dɛtəˈneɪʃən/, publish /ˈpʌblɪʃ/
- 긴 단어 — 강세 위치에 주의: speculation /ˌspɛk.jəˈleɪ.ʃən/, configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/, conceptually /kənˈsɛp.tjʊə.li/, detonation /dɛtəˈneɪʃən/, repeatable /ɹɪˈpiːtəbəl/
한국어 화자가 어려워하는 소리:
- /f/ — ㅍ(/p/)으로 바꾸지 말고 윗니를 아랫입술에 대기: frontier /ˈfɹʌntɪə/, foggy /ˈfɒɡi/, fidelity /fᵻˈdɛlədi/, waterfall /ˈwɔːtəfɔːl/, configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/
- /v/ — ㅂ(/b/)과 구별하기: resolve /ɹɪˈzɑlv/, invoke /ɪnˈvoʊk/, revisit /ɹiːˈvɪzɪt/, vaguely /ˈveɪɡli/, invaluable /ɪnˈvælju(ə)bl̩/
- /z/ — ㅈ이 아니라 성대를 울리는 /s/: resolve /ɹɪˈzɑlv/, spectacles /ˈspɛktəkl̩z/, repository /ɹɪˈpɒz.ɪ.t(ə.)ɹɪ/, revisit /ɹiːˈvɪzɪt/, zoom /zuːm/
이 영상으로 연습하는 방법
- 먼저 말하지 않고 영상을 끝까지 듣고 모르는 단어를 적어 둡니다.
- 0.75배속으로 한 문장씩 섀도잉을 시작하고, 익숙해지면 보통 속도로 돌아갑니다.
- 자신의 목소리를 녹음해 원본과 비교하고, grill, chunk, diagram 같은 단어에 특히 주의합니다.
쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법
쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.