Skip to main content
This is the whole thing in one page: take an idea, find out if people want it, and turn it into everything you need to launch. Each step is one slash command in Claude Code — or one Python call. They all read from the one demand report you produce first, so every recommendation traces back to a real quote you can open. Install the Claude Code plugin, or pip install "metalworks[research]" and set one provider key (see Installation). Then walk the five steps below.

​
1. Is there demand?

Start with one sentence about your idea. metalworks reads real conversations — Reddit, Hacker News, the web, or your own data — and gives you a go/no-go plus the actual needs people voiced.
If the demand is thin, it says so here — and the later steps stay honest about it instead of inventing an opportunity. Everything below runs on this report. → Demand research

​
2. Find your angle and your competitors

Your positioning is built from the unmet needs in the report; each competitor gap is a real complaint someone posted. → Positioning · Competitors

​
3. Turn it into a build plan

metalworks writes the spec, not the product. From the demand it picks the surface to build on (web? mobile? CLI? — with a one-line reason), maps the demand to a feature list, sketches the screens you need, and scaffolds a project your own coding agent (Claude Code, Cursor, etc.) builds.
The scaffold includes a frozen list of the real quotes behind every feature, so whatever your agent builds stays true to what people actually asked for. → Build spec

​
4. Distribution

Distribution copy is drafting-only — metalworks never posts anything. Each claim in a draft is backed by a quote; the GEO stream lists the real threads to cite so people and AI search engines find you. → Distribution · GEO / LLM-citability

​
That’s the loop

One idea → one grounded report → positioning, design, a build plan, distribution. Because it all reads from the same report, every recommendation links back to a real quote you can open and read for yourself. That’s the difference between this and a tool that just makes things up — see why you can trust the output. Run metalworks init first and metalworks remembers all of this — each run is saved under .metalworks/ and later steps chain off its report_id instead of re-running research. See Projects & memory. New to the plugin? See the Claude Code plugin for installing it and what each command does. Driving it from your own app or agent? The same flow runs through the CLI and MCP tools.