Project handoff

Give a developer or coding agent the requirements, architecture diagrams, and decisions they need to work on your project.

Choose File → Export → Advanced → Markdown handoff to put your architecture, linked SVG diagrams, requirements, and architecture decision records (ADRs) into a project repository. An agent can start at docs/architecture.md, follow a link to a diagram or acceptance criteria, and read why a design decision was made.

An architecture decision record explains what the team decided, why it chose that option, and what trade-offs follow.

Example handoff inside a repository called my-app
my-app/
└── docs/
    ├── architecture.md
    ├── requirements.md
    ├── diagrams/
    │   └── diagram-id-registration-journey.svg
    └── adr/
        ├── README.md
        └── 0001.md

A whole-project handoff includes every ADR automatically. For a feature addition, use a named Document View with just the relevant diagrams and requirements. Add an Architecture decisions block to that view to include the decisions the developer needs.

The workshop registration example includes an ADR about what happens when two people try to book the last place.

Try this with Workshop Registration