Nextnow

You have an idea a week. Most of them die in a note; the ones that survive each get a folder, a repo, a half-written README, a port number you forget, and no two of them are built the same way. Nextnow is the workshop that takes the next one, now.

One repertoire holds every project: name, one line, stack, tags, status, a port, private or public. Each project follows a profile — a small side-project that could pay for itself, say — and the profile lays out the stages: idea, features, business, market, PRD, tech, research. Each stage is a markdown file, idea.md, features.md, business.md; the required ones are required, you press Init and a template opens, and the project does not move on until the file exists. An inbox for what has not been sorted yet, a library, templates, and a portfolio side that turns the finished ones outward — with an insiders view for the people who get to see early.

The library is mythological: seventy-eight figures to name projects after, each with its etymology written on the sheet. Euterpe is a music player. Metis is the knowledge base. A project is a name before it is a codebase, and the name has to mean something.

The industrial part is the discipline, not the volume: same stages, same files, same questions asked in the same order, so that a solo founder can start the tenth project the way a factory starts the tenth run — knowing where everything goes.