Guide 2 of 3
Start new project
There is no code to inspect yet. In this guide you and your agent agree on the project's direction, its constitution, one topic at a time. At the end you have confirmed decisions, a list of open ones, and a first plan.
"Constitution" is an editorial name on this site. It is not a CLI command and not a required file. Each domain decides where project context lives.
Before you start
- You finished Set up your project and doctor passes.
- You have a new agent session open at the project root.
1. Cover the constitution topics
- Purpose: the problem the project solves.
- Intended users: who uses it and what they need.
- Initial scope: what the first version must do.
- Exclusions: what it will not do for now.
- Constraints: time, budget, platform, legal, or team limits.
- Chosen stack: only if you already decided it.
- Engineering principles: how the team wants to build.
- Success criteria: how you will know the first version works.
2. Run the interview
Cumaru's universal bootstrap rules apply here too: one topic at a time, only confirmed answers, and empty topics stay empty. Give your agent this prompt:
Help me set the direction for this new project. Run `cumaru bootstrap` first and follow its rules.
Ask me about one topic at a time, in this order:
purpose, intended users, initial scope, exclusions, constraints, chosen stack, engineering principles, and success criteria.
Write only the answers I confirm. Mark every unanswered topic as open. Do not suggest answers as facts.
Do not declare components or write specs for code that does not exist yet.
Store the confirmed direction where my domain says project context belongs, and use cumaru tag and cumaru fs for the changes.
Finish with `cumaru doctor` and a summary of confirmed and open decisions. Keep confirmed and open decisions apart. An open decision is useful information; a guessed answer is not.
3. Store the direction
Example: sdlc-light
This example applies only to the sdlc-light domain. Record the confirmed direction,
briefly, in the root tag of .cumaru/domain.md. Do not edit the
framework prose outside the tag.
cumaru tag set domain.md root Declare components and target keys only after you confirm them. Planned behavior does not go
into specs/; specs describe what is true now.
Other domains may keep project context in a dedicated file. For example, ai-ccn uses
an adopter-owned constitution.md. Follow your domain's contract.
4. Check the result
cumaru doctor Then review your agent's summary. Every topic should be confirmed or marked open.
5. Open the first plan
The intended implementation and its acceptance criteria belong in a plan. In sdlc-light, use the cumaru-plan skill:
Use the cumaru-plan skill to open the first plan for this project.
Base it only on the confirmed project direction. Put the intended implementation and its acceptance criteria in the plan.
Keep open decisions listed as open in the plan. Sources: Universal bootstrap rules, sdlc-light domain, Available domains. The constitution topics and prompts are guidance from this site, not CLI behavior.