Alejandro AO tests pairing the cheap open-source coder Kimi K2.7 with expensive frontier models (Opus 4.8, GPT 5.5) by splitting a coding workflow into a planning phase and an implementation phase, then benchmarking every planner/implementer combination on a fresh CPython GitHub issue to find the best cost-to-quality ratio.
Alejandro AO18 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 Alejandro AO; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to split an agentic coding workflow into planner and implementer roles and empirically choose which model fills each role to cut cost without sacrificing output quality.
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.
3,053 cleaned transcript words reviewed across 884 timed caption segments.
Thesis
Kimi K2.7 + Opus 4.8 = BEST Coding Duo?? teaches a practical creative automation move: Alejandro AO tests pairing the cheap open-source coder Kimi K2.7 with expensive frontier models (Opus 4.8, GPT 5.5) by splitting a coding workflow into a planning phase and an implementation phase, then benchmarking every planner/implementer combination on a fresh CPython GitHub issue to find the best cost-to-quality ratio.
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:46
Split the workflow
“it. All right, so let me tell you a little bit about this experiment and what I mean when I say using multiple models during your works your workflow. So, what happens is that when you have your...”
A coding task moves through understanding the issue, exploring the codebase, planning, implementing, and review — and you don't need one expensive model for all of it: assign exploration-plus-planning to one model and implementation to another, using an open-source model like Kimi K2.7 (roughly $0.95/M input, $4/M output vs $25–30/M output for Opus 4.8 and GPT 5.5) to save premium tokens. Write out the five phases of your own coding workflow and mark which phases currently burn your most expensive model's tokens unnecessarily.
6:55
Benchmark on fresh issues
“agent who's going to be the implementer and this agent is going to be in charge of exploring the code base, figuring out what the issue really is, creating an implementation plan and handing out that implementation plan,...”
The experiment used a two-week-old CPython bug (class-scope comprehension with lambda raising SystemError) so no model had seen it in training, ran every model as both planner and implementer, and had GPT 5.5 and Opus 4.8 jointly judge solutions with averaged scores to mitigate self-preference bias — while tracking the dollar cost of each combination. Pick a recent issue from a repo you use (newer than the models' training data) and run two planner/implementer combinations on it, recording both a quality judgment and the token cost.
13:34
Frontier plans, Kimi implements
“the different combinations ended up being not that great. In this particular case, we see there is a little bit of noise, so Kimi K12.6 and Kimi K12.7 performed relatively similarly because this is a relatively simple issue.”
Every combination produced a mergeable PR with only ~1 point of quality variance on a 10-point scale, so cost became the differentiator: Kimi-inclusive combos were about seven times cheaper, Opus 4.8 proved a strong planner but an expensive implementer, and the recommended split is GPT 5.5 or Opus 4.8 for planning with Kimi K2.7 implementing. Install the Dual Bench skill (npx skills add) and run its planner/implementer benchmark with plots on one of your own GitHub issues using Pi and tmux.
01
Brief
Start with this video's job: Alejandro AO tests pairing the cheap open-source coder Kimi K2.7 with expensive frontier models (Opus 4.8, GPT 5.5) by splitting a coding workflow into a planning phase and an implementation phase, then benchmarking every planner/implementer combination on a fresh CPython GitHub issue to find the best cost-to-quality ratio. Treat "Brief" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:46, where the video says: “it. All right, so let me tell you a little bit about this experiment and what I mean when I say using multiple models during your works your workflow. So, what happens is that when you have your...”
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 6:55, where the video says: “agent who's going to be the implementer and this agent is going to be in charge of exploring the code base, figuring out what the issue really is, creating an implementation plan and handing out that implementation plan,...”
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: Alejandro AO tests pairing the cheap open-source coder Kimi K2.7 with expensive frontier models (Opus 4.8, GPT 5.5) by splitting a coding workflow into a planning phase and an implementation phase, then benchmarking every planner/implementer combination on a fresh CPython GitHub issue to find the best cost-to-quality ratio.
02
Explain the practical stakes without hype: New playlist item from Alejandro AO; 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: Kimi K2.7 + Opus 4.8 = BEST Coding Duo??
- URL: https://www.youtube.com/watch?v=2H78l10fkMQ
- Topic: Creative Automation
- My current learning frame: Take one real issue from your backlog, have a frontier model produce the implementation plan, hand that plan to Kimi K2.7 to implement, then compare the resulting PR's quality and total token cost against your usual single-model workflow.
- Why this matters: New playlist item from Alejandro AO; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:46 / Evidence 1: "it. All right, so let me tell you a little bit about this experiment and what I mean when I say using multiple models during your works your workflow. So, what happens is that when you have your..."
- 2:20 / Evidence 2: "coding task. And then we're going to have another model do the implementation itself. And the code review is really independent because you always do it anyways. So, we're just going to split this part right here. And..."
- 3:58 / Evidence 3: "on their agentic benchmarks as well. So, on Chemico, which is the benchmark that measures how good this model is at claw-like agents such as Open Claw or Hermes, on MCP Atlas and MCP Mark Verified, it's also..."
- 6:55 / Evidence 4: "agent who's going to be the implementer and this agent is going to be in charge of exploring the code base, figuring out what the issue really is, creating an implementation plan and handing out that implementation plan,..."
- 8:36 / Evidence 5: "training material, okay? So, since this one is from just about 2 weeks ago, it is perfect to test how good these models are at this. So, I take this GitHub issue and I gave it to all..."
- 13:34 / Evidence 6: "the different combinations ended up being not that great. In this particular case, we see there is a little bit of noise, so Kimi K12.6 and Kimi K12.7 performed relatively similarly because this is a relatively simple issue."
- 17:03 / Evidence 7: "in the description. It is called Dual Bench right here, and as you can see, it is a skill that you just install with NPX skills add, and you just ask your model benchmark Opus and Kimi on..."
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 "Kimi K2.7 + Opus 4.8 = BEST Coding Duo??", 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.
How does the video propose splitting a coding workflow across two models, and why does that save money?
Why did the experiment use a CPython issue that was only about two weeks old, and how were solutions judged?
What was the final model-pairing recommendation, and what evidence supported it?
Source shelf
Use the video as a doorway, then verify with primary sources.
