Plans

A plan is a change you design with the planner, across as many repositories as it needs, until it is published and implemented. You lead it. The planner asks, drafts and writes nothing else.

Start a plan

Choose New plan, give it a title, the repositories it touches, an epic if you want one, and a brief. Then choose Start planning.

You can add a repository while you plan, on the plan's Plan tab, and the planner adds one you ask for or agree to. Only you take one out.

Answer the planner

The planner reads your repositories and never changes them. Before its first question, it reads the ADRs and the domain model of each repository whose Documentation names them, and the ADRs that concern the plan. The code and the documentation answer what they can, and it asks you the rest. When a word of yours conflicts with the domain model, it says so. It never writes to your tracker or your documentation while you plan. Each turn, it asks one to three questions, each with a Recommended answer and up to three others, and you can write your own. You send your answers together.

As the design takes shape, it drafts

• the tickets, T1 to Tn, each in one repository,
• the decisions, as ADRs,
• the terms of your domain.

Publish

Publish writes the plan where your team keeps its work. The tickets go to each repository's tracker, linked by what blocks what, with the label ai-planned, under the epic if there is one. The ADRs and the terms go to the documentation of one repository, the one you choose, which needs the address of its ADR index or of its domain model page.

Publishing again is safe. An ADR or a term cannot be changed once published.

Implement

Implement puts the plan's tickets in the Builder, and starts a resolver on each ticket once the tickets it waits for are merged.