Claude Code /goal Just Dropped and it Can Build Literally Anything
This video demonstrates how to use the new /goal feature in both Claude Code and Codeex to autonomously build a complete Next.js social-content app from a PRD and a 62-task product roadmap in a single ~32-minute long-running agent pass.
Build Great Products27 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 Build Great Products; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: Setting up and running a long-running coding agent with /goal so it loops through a defined task roadmap, self-verifies each task, and stops only when a measurable completion condition is met.
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.
5,682 cleaned transcript words reviewed across 1,596 timed caption segments.
Thesis
Claude Code /goal Just Dropped and it Can Build Literally Anything teaches a practical creative automation move: This video demonstrates how to use the new /goal feature in both Claude Code and Codeex to autonomously build a complete Next.js social-content app from a PRD and a 62-task product roadmap in a single ~32-minute long-running agent pass.
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:00
What /goal does
“Claude Co just released a feature that is going to change the way that everyone builds with AI. But the thing is they stole it directly from codecs. And the feature I'm talking about is for/goal. And what...”
/goal sets a completion condition and the agent keeps working turn after turn without per-step prompting; a small fast model checks after each turn whether the condition holds, looping again if not and clearing the goal only when met. It is presented as an evolution of the Ralph loop, paired with auto mode for broader permissions. Open the Claude Code and Codeex /goal docs and write down the four subcommands and the lifecycle states so you understand exactly when the loop terminates.
7:35
Writing a strong goal
“context to be able to work correctly. So, let's start building our app using for/goal include code and codeex. But before we start, I want to show you how I've set up the folders for these projects as...”
A good goal is bigger than one prompt but smaller than an open-ended backlog: it must define one measurable end state, what to change, how to validate progress, and when to stop, so the agent knows what 'done' means before it starts. A verifiable roadmap of checkable tasks (typically 40-80 for a full app) supplies that end state, and explicit constraints lock down what must not change. Draft a single /goal condition under 4000 characters that names a measurable end state plus one 'must not change' constraint, then have the agent critique whether 'done' is unambiguous.
23:01
Setup that makes it work
“you're going to get around any like specific design direction from a a given model. Basically we've got our channel that is connected here. Jordan builds 10 posts ready to review now processing videos processing post generated niche...”
The build succeeds because the folder is pre-loaded with context: a claude.md/agents.md with Karpathy-style rules, a docs folder holding the PRD, the product roadmap.md task list, and a design.md (Google's open format) for visual direction. Entering plan mode first and answering the agent's clarifying questions (build offline with mocks/stubs, design.md wins) gives a verifiable plan before any code is written. Recreate this scaffold for a small app of your own (claude.md rules + PRD + roadmap checklist + design.md), then run /goal in plan mode and note which clarifying questions the agent asks before building.
01
Brief
Start with this video's job: This video demonstrates how to use the new /goal feature in both Claude Code and Codeex to autonomously build a complete Next.js social-content app from a PRD and a 62-task product roadmap in a single ~32-minute long-running agent pass. Treat "Brief" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:00, where the video says: “Claude Co just released a feature that is going to change the way that everyone builds with AI. But the thing is they stole it directly from codecs. And the feature I'm talking about is for/goal. And what...”
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 7:35, where the video says: “context to be able to work correctly. So, let's start building our app using for/goal include code and codeex. But before we start, I want to show you how I've set up the folders for these projects as...”
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: This video demonstrates how to use the new /goal feature in both Claude Code and Codeex to autonomously build a complete Next.js social-content app from a PRD and a 62-task product roadmap in a single ~32-minute long-running agent pass.
02
Explain the practical stakes without hype: New playlist item from Build Great Products; 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: Claude Code /goal Just Dropped and it Can Build Literally Anything
- URL: https://www.youtube.com/watch?v=0lw8KTx8KS8
- Topic: Creative Automation
- My current learning frame: Build your own offline-first Next.js app by authoring a PRD, a checkable product roadmap, and a design.md, then launch a single /goal run in plan mode and inspect how completely the agent flips every roadmap checkbox before declaring the goal done.
- Why this matters: New playlist item from Build Great Products; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:00 / Evidence 1: "Claude Co just released a feature that is going to change the way that everyone builds with AI. But the thing is they stole it directly from codecs. And the feature I'm talking about is for/goal. And what..."
- 2:53 / Evidence 2: "to understand here for non-technical people over at buildgreateproducts.com, which just covers off what is the codec cli, what for/goal actually does, the four subcomands, life cycle states, how to actually write a strong goal, and some of..."
- 7:35 / Evidence 3: "context to be able to work correctly. So, let's start building our app using for/goal include code and codeex. But before we start, I want to show you how I've set up the folders for these projects as..."
- 10:07 / Evidence 4: "context manageable. So it's now reading those files there. Codeex has saying the workspace is essentially fresh. Only agents.md and docs are present. There is no git metadata in this directory. The design file is design. MD. So..."
- 11:57 / Evidence 5: "design source. Let's do design.md wins everywhere. The scope is all 62 tasks as code. Get um in it with no remote. Let's do that. and then submit these answers to Claude Code. Codeex is just off to..."
- 23:01 / Evidence 6: "you're going to get around any like specific design direction from a a given model. Basically we've got our channel that is connected here. Jordan builds 10 posts ready to review now processing videos processing post generated niche..."
- 26:17 / Evidence 7: "really introducing an entirely new way of building with AI agents where instead of just prompting back and forth, we're allowing the AI agent to decide what all of these different tasks are based on a longer running..."
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 "Claude Code /goal Just Dropped and it Can Build Literally Anything", 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.
Mechanically, how does /goal keep the agent working without you prompting each step, and when does it stop?
What makes a good /goal condition, and what is the character limit and typical roadmap size for a full-app build?
What scaffolding did Chris pre-load into the folder so /goal could build the whole app, and what did he do before letting it code?
Source shelf
Use the video as a doorway, then verify with primary sources.
