Documentation

Guide 3 of 3

Bootstrap existing

Your code already exists. In this guide your agent records what you confirm about the project, then maps the code into knowledge it can navigate. At the end you have a verified first version of that knowledge and a list of open gaps.

Before you start

  • You finished Set up your project and doctor passes.
  • You have a new agent session open at the project root.

1. Understand what bootstrap does

cumaru bootstrap prints instructions and changes nothing. It prints universal rules for every domain, then the installed domain's own steps when the domain has them. Your agent follows these instructions; the command does not.

Do not confuse it with templates/bootstrap.md, which some domains use as a discovery log for one area.

2. Run the project interview

The universal rules say: ask one topic at a time, write only confirmed answers, and keep unanswered topics empty. Give your agent this prompt:

Run `cumaru bootstrap` and follow the steps it prints.
Ask me one topic at a time. Write only what I confirm.
Leave unanswered topics empty, and do not infer answers from the repository.
Use cumaru tree, map, tag, and fs for every change in .cumaru/.
Finish with `cumaru doctor` and list the topics I answered and the ones still empty.

3. Map the code from evidence

The interview records what you say. Mapping records what the code shows. This second step uses the domain's skills, so it differs between domains.

Example: sdlc-light

This example applies only to the sdlc-light domain. sdlc-light has no domain bootstrap document today, so cumaru bootstrap prints only the universal rules. Its adoption skill adds these steps:

  1. Inspect the README, manifests, code, contracts, and tests.
  2. Propose components, such as a web app or an API, with the evidence for each.
  3. Confirm the components with you before writing them.
  4. Write the components tag in domain.md and the matching target keys in config.yaml.
  5. Use cumaru-specs to create spec areas for the behavior that exists today.
Use the cumaru-install skill to map this project's components.
Read the README, the package manifests, the top-level layout, the contracts, and the tests.
Propose the component list with the files you inspected for each one. Wait for my confirmation.
Write the confirmed list with `cumaru tag set domain.md components`, and add the same keys to meta.targets.values in .cumaru/config.yaml.
Then use the cumaru-specs skill to bootstrap spec areas. Confirm every area with me before you create it.
Finish with `cumaru doctor`, the sources you inspected, and the gaps that remain.

Other domains may keep their durable knowledge somewhere other than specs/. Follow your domain's skills.

4. Check the result

cumaru doctor

Then review your agent's report. It should list:

  • the topics you confirmed and the topics still empty;
  • the source files it inspected for each component or area;
  • the gaps that still need a decision or more evidence.

Sources: Bootstrap command, Universal bootstrap rules, sdlc-light adoption, Spec authoring. The prompts are guidance from this site, not CLI output.

Other paths