The picture that is still a map
A MIT Claude Code plugin that draws a plan against the diff, once someone names the product in a map.
- Category
- Developer tools
- Who it is for
- A team already using Claude Code whose reviews are still a file list.
- Possible model
- Open source
- Difficulty
- Medium
- Inspired by
- Readback · Readback
- Original launch
- Watch the launch · Oct 19, 2026
Difficulty is an editorial estimate of technical and operational complexity, not a score.
Startup idea analysis by Startup Ideas. Last reviewed Oct 19, 2026. How we read a launch.
The startup idea
Nikhil posted Readback on October 19. See what Claude Code planned against what it actually changed, as a picture. Open source. The links are github.com/nik190799/readback and xion-labs.com/readback. The site says it is in development. It is a Claude Code plugin. While Claude works, it lays the product out as features and tracks what the plan said, what changed, and who has to check it. The readme says it reads the git diff and .readback/map.json. Init drafts that map from the folders, and you rename the tiles into the team's words. MIT. Python 3.8 or newer, and git. A maybe tile is confirmed once and never raises a flag by itself. Unplanned and not-touched flags need a real plan: plan mode, or a Readback-Plan line in the pull request. Without that line, the board shows what changed and no flags. The log at .readback/log.jsonl stores tile ids and counts, not the code or the plan text, stays on the machine, and is gitignored. The post says every angle: user, product, team. The site's lenses are questions the map can answer. The map starts as folders. This page did not install the plugin.
The opportunity is a review a teammate can read without the diff. A smaller product is one repo, a map a person actually renamed, and a board that stays quiet when there was no plan. A picture of folder names is not the product the post describes.
Do not say it covers every angle on a fresh repo. Init has not been edited yet. Do not say the site is finished. It says in development.
The problem
A diff says which files moved, and not which feature the team thinks moved.
Who would pay for this?
- Primary
- A team already using Claude Code whose reviews are still a file list.
- Secondary
- A person who will rename the tiles and put a plan line on the pull request.
- Early adopter
- One repo, one renamed map, and the in-development line.
How could it make money?
Possible models. Nothing here is a claim about what Readback charges.
- No price. MIT.
- The coding agent is one the team already pays for.
- The post does not name a seat.
What would the MVP look like?
- A board for one branch.
- A map someone renamed.
- Flags only when a plan exists.
- The in-development line from the site.
How to validate the idea
- Ask five reviewers if the tiles match the words they use in a meeting.
- If the tiles are still folder names, the map was not the product.
- Do not count a board with no plan as a plan check.
How to differentiate
- The unit is a feature tile, not a file.
- Maybe does not raise a flag.
- The log keeps counts, not the code.
- Do not become another diff viewer.
Original product launch
This launch is inspiration and evidence that someone shipped, not a partnership. The idea above is our reading of the broader opportunity. Readback did not write it.
- Product
- Readback
- Source
- Readback
- Film
- Readback, the map starts as folders
- Posted
- Oct 19, 2026 · 0:44
Product that inspired this idea
Nikhil's post says Readback shows what Claude Code planned against what it changed, as a picture. Open source. The site says it is in development. It is a Claude Code plugin. It reads the git diff and a map at .readback/map.json. Init drafts that map from folders, and you rename the tiles. The readme says MIT, Python 3.8 or newer, and git. A maybe tile is asked once and does not raise a flag by itself. Unplanned and not-touched flags need a real plan, or a Readback-Plan line on the pull request. The log stores tile ids and counts, not the code, and it is gitignored. The post says every angle: user, product, team. Those angles are the map, and the map starts as folder names. This page did not install the plugin.
Posted by @nikhil_kadalge. Watch the original launch. No separate product site is listed unless the post itself is the source.
- agents
- review
Related startup ideas
- A drive that files the document and cites the page
Upload a pile of files, have them land in a folder a person would recognize, and answer a question with the page it came from.
- A visible team of agents in a world you can walk into
Use a shared world, not a log file, when several agents need a person to come over and decide.
- An Android remote for coding agents
A phone client for checking projects and steering agents when the laptop is closed.
- An inbox so the agents stay quiet
Collapse every coding-agent thread into one list, and only interrupt when one of them is stuck.
- Coding agents in the menu bar
Show which coding session is working, which is stuck, and let a person reply without opening the app.
- Cut the launch film from the app you already have
A skill that rebuilds the screens in a frame, times them to a track, and renders on the machine the coding agent already uses.
Looking for more ideas?
The full list is startup ideas for 2026, each one tied to a launch you can watch.
Browse startup ideas for 2026