Turn a feature backlog into shippable code in batches

A solo developer used Claude Code to turn a planned feature list into markdown tasks, then had Claude implement each batch and pause for review.

Done with Claude CodeClaude· Intermediate· Nov 2026

What they did
Working alone in the terminal, they used Wispr Flow to speak detailed requirements and first talked them through with Claude. Claude then organized the work into a Vision, Features, and Tasks markdown flow, along with a Claude.md file. After they outlined a large set of features, they asked Claude to carry out the next group of tasks in order and check the results.
How it went
The writer says Claude does strong implementation work once the requirements are clear, and they spend less time digging into the code themselves. Claude also creates visual review pages for the apps. No numbers were given.
Tips
Keeping the plan in markdown makes the workflow easier to move away from Claude Code later. Having the agent build a visual review page can help you inspect behavior without reading source.

Try it yourself with Claude Code

In [project folder], help me create VISION.md, FEATURES.md, TASKS.md, and Claude.md for [product]. First, ask me the questions you need to define the product vision and feature list. Then help me write [number] features in FEATURES.md and break the first feature into small, testable tasks in TASKS.md. Implement only the first [3-5] tasks, run the relevant tests, then stop and show me a clear summary of what changed for review before starting the next batch. Before doing anything irreversible, such as deleting files, submitting code, or making external calls, pause and ask for my approval.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on news.ycombinator.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.