Claude Code Plan Mode: Did AI Build a Feature in 17 Hours?
By Matt Cullerton, founder of Mavric and Apso
A TikTok claims AI built a whole feature in 17 hours by writing a 930-line plan first, then shipping it in five reviewed pull requests. The timeline on screen adds up to exactly 17 hours, and the workflow matches what Claude Code's docs recommend. But no public repository backs the 15,870 lines or the pull requests, so the results are self-reported.
The video, from @austinbuildswithai, is a short animation with the closing line "Don't ask AI for a feature. Ask it for a plan." Its description tags #claudecode, though no tool is named on screen or in the audio.
What does the video show?
It starts with a file labeled "PLAN.md" that grows to 930 lines, with 19 lines highlighted as "19 decisions" and the caption "First, no code. Just a plan." Then it lists five phases, each as its own pull request:
| Phase | Pull request | Merged |
|---|---|---|
| 0 Fix what's there | #434 | 12:56 AM |
| 1 Purchase orders | #436 | 5:40 AM |
| 2 Receiving + bills | #437 | 8:24 AM |
| 3 Received, not billed | #438 | 3:07 PM |
| 4 Parts + van restock | #439 | 4:55 PM |
A status line counts added lines, from "+0 lines" at "Wed 11:55 PM" to "+15,870 lines" at "Thu 4:55 PM." The captions say each phase was "checked by AI reviewers."
Does the 17-hour timeline add up?
It does. Wednesday 11:55 PM to Thursday 4:55 PM is 17 hours to the minute. The time between merges also adds up:
- Phase 0: 1 hour 1 minute
- Phase 1: 4 hours 44 minutes
- Phase 2: 2 hours 44 minutes
- Phase 3: 6 hours 43 minutes
- Phase 4: 1 hour 48 minutes
Those total 1,020 minutes, or 17 hours. The 15,870 lines over 17 hours works out to about 933 added lines per hour, including any review and merge time.
The counter has gaps. It shows additions only, with no deletions or net change. It does not break down how much is application code versus tests, migrations or generated files. The pull request numbers also skip #435, which the video does not explain.
Can the 15,870 lines be verified?
They cannot. If the repository were public, each pull request page would show its own line counts, merge time and review comments. No public repository, profile or post tied to the handle could be found. The plan size, the 19 decisions, the pull requests and the line count all come from the uploader.
The app is not named. The phase titles describe purchasing and stock for a business that runs vans, which suggests a field-service product. "Received, not billed" is a standard accounting concept for goods received before the vendor's bill arrives, used in tools like NetSuite, ERPNext and QuickBooks.
How does Claude Code plan mode work?
The workflow in the video matches Claude Code's documented plan mode, though the video never confirms which tool was used. The permission modes page says: "Plan mode tells Claude to research and propose changes without making them. Claude reads files, runs shell commands to explore, and writes a plan, but does not edit your source."
Edits "stay blocked until you approve the plan." Approving the plan switches the session to an editing mode so Claude can start work. Ways to use it:
- Press
Shift+Tabto switch into plan mode - Start a prompt with
/plan - Run
claude --permission-mode plan - Press
Ctrl+Gto open the proposed plan in your editor before approving
The best practices page recommends the same sequence the video shows, under the heading "Explore first, then plan, then code": Explore, Plan, Implement, Commit, with the last step being "commit with a descriptive message and open a PR." It also suggests having Claude interview you and "write a complete spec to SPEC.md," then "start a fresh session to execute it." One example prompt reads "Use a subagent to review the rate limiter diff against PLAN.md."
When should you skip the plan?
The video's closing line leaves out a limit the docs spell out. The best practices page says: "Plan mode is useful, but also adds overhead. For tasks where the scope is clear and the fix is small (like fixing a typo, adding a log line, or renaming a variable) ask Claude to do it directly." It adds: "If you could describe the diff in one sentence, skip the plan."
A five-phase purchasing feature spans many files and has an uncertain approach, so it fits the case for planning. A one-line fix does not.
Can AI reviewers merge pull requests?
Claude's review tools cannot. The video says each pull request was "checked by AI reviewers" but does not say which. Claude Code's options:
- Code Review (Team and Enterprise plans). "Several agents examine the diff and the surrounding code in parallel," a verification step "filters out false positives," and findings are ranked and posted as inline comments. The docs say "A review never approves or blocks the pull request, so the decision to merge stays with your team."
- GitHub Actions. A workflow runs the
code-reviewplugin on pull request events with an API key or subscription token. - The
/code-reviewskill, which runs locally on any plan. - A Writer/Reviewer setup with two sessions, since "Claude won't be biased toward code it just wrote."
The Code Review docs add: "A review with no findings doesn't mean your code is error-free or secure." The video shows no findings and no fix cycle, so it is unclear whether the reviews changed anything.
Since these tools do not merge, something else merged the five pull requests through the night and the next day. The video does not say whether that was a person, an automation or another reviewer.
Bottom line
The timeline in the video is internally consistent: 17 hours from start to last merge. The plan-first workflow matches Claude Code's documented plan mode and its explore, plan, implement, commit sequence. The line counts and pull requests cannot be checked, and Claude's AI reviewers never merge code on their own. For small, one-sentence changes, the docs say to skip the plan.
Sources
- Claude Code docs: Choose a permission mode - plan mode and how to enter it
- Claude Code docs: Best practices - explore, plan, implement, commit and when to skip planning
- Claude Code docs: Common workflows - the plan-before-editing recipe
- Claude Code docs: Code Review - multi-agent review and the no-merge rule
- Claude Code docs: GitHub Actions - the code-review workflow
Published October 17, 2026. Based on a TikTok by @austinbuildswithai. Full video notes (markdown)