Guides
Documentation
Working with agents

Technical Guide agent

Documents the stack, data model, and conventions for the build.

The Technical Guide agent writes the technical shape of the product: stack choices, the data model, conventions, and how things fit together. On an existing codebase Fragua also drafts this guide for you automatically from the code — it arrives ready for you to review, accept, or edit, the same as any other draft.

What you share to start

Describe what you want the guide to cover (up to 1,500 characters) and add any notes. There's no prerequisite; the agent draws on your earlier documents when they exist.

Already have a technical guide? You don't have to generate it — paste what you have and save it, and it goes straight to review. See Greenfield and brownfield.

How the turns work

The agent asks a round or two of questions on the page, then writes the guide. You answer; others follow read-only.

How a turn cycle goes
You describe it Agent asks You answer Draft Review Accept

The ask-and-answer step repeats until the agent has enough to write the draft. After the draft, sending revision notes reopens the same conversation.

Accepting the result

The guide lands in review for the workspace to accept, and stays editable by you or an admin afterward.

Good to know

  • While a run is going, only the person who started it can answer — everyone else in the workspace follows along read-only.

  • If a run stalls or you change your mind, you can cancel it, then restart or resume from where it left off.

  • Fragua lets you know when a draft is ready or a run fails, so you don't have to sit and watch it.

  • An admin can undo an acceptance to send a document back to review.