A new project, set up in one sitting

The situation

Every new project starts with the same half hour: the same board columns, the same rules for agents, the same skills library, the same MCP wiring. It is remembered rather than written down, so it drifts

• and the fourth project is set up slightly differently from the first for no reason anybody chose.

1. Capture what you actually do

Once, on the project you like best, write the setup down as a setup profile: which instruction sets, which asset collections, which versions, and the MCP hints a client needs.

A profile is a manifest, not a script. It declares a working environment; makermap assembles it and your client applies it.

2. Start the product

create_product with a name and the five "why" fields. Those are not ceremony - they are what get_product_context hands an agent later, and an agent that knows why the product exists writes different code from one that does not.

3. Apply the profile

apply_setup_profile returns everything the environment needs, resolved at the versions the profile pins. Nothing is invented here: it owns no library logic and reads through the services that do, so what you get is exactly what those tools would have returned one call at a time.

4. Seed the work

create_tasks takes a batch, so the first sprint is one call rather than fifteen. Give an agent the outline and let it write them:

Read get_product_context for this product. Propose the first two weeks as tasks, grouped by epic, each with what "done" looks like. Do not create anything until I say go.

5. Hand it to the agent

The bootstrap that makes this worth doing: a new machine, one MCP endpoint, and the same environment appears - because the profile is data in the product, not a page in somebody's notes.

What this buys you

The setup stops being a memory exercise. Two projects set up a month apart are set up the same way, and when you improve it you improve the profile rather than the last project you touched.