# Working a solution through

> You start a research — and get a verified document on your code and the team’s documents, exportable to PDF.

Use case

# Working a solution through

The solution is not obvious — you need a worked-out analysis with reasoning that you can confidently attach to a task, not a quick answer.

[Connect a repository](https://buff.systems/app) [All use cases](https://buff.systems/en/use-cases)

Situation

## You need a document, not a chat answer

What gets in the way

- The solution is not obvious — you need a verified analysis, not a quick answer.
- You need a document with reasoning — to attach to a task or show the team.
- You need to compare options and choose with arguments.

Solution 01

## Start a research — get a verified document

You pose the question, and two agents — an analyst and a reviewer — work it through using your code and connected sources — tracker tickets, Confluence and Notion pages, documents on Drive — in several steps, checking each other’s conclusions. Solution options are examined and compared, and the choice comes with arguments. The result is a structured document (question, options, a reasoned recommendation), not scattered chat answers, exportable to PDF.

[About research](https://buff.systems/en/docs/research)

**Start a research — get a verified document**

← scroll the frame →

Research: the logic worked through, with options and a recommendation.

Solution 02

## Research documents — straight into the task

You attach finished research to a task. Here, for example, a task about an incremental search index has three analyses attached at once — cache invalidation, the choice of index variant and the inverted index design. Development starts from verified facts rather than guesses — the research sits next to the specification.

[About attachments](https://buff.systems/en/docs/tasks/attachments)

**Research documents — straight into the task**

← scroll the frame →

A task with deep research files attached.

Solution 03

## A well-prepared task — into a large work plan

A well-prepared task breaks down into a plan with confidence: the system splits it into subtasks and builds them in order of dependencies. Here one search index unfolded into 17 subtasks across 7 stages — you see what is done, what is in progress and what is ahead.

[About autonomous development](https://buff.systems/en/docs/pipeline)

**A well-prepared task — into a large work plan**

← scroll the frame →

Development map: 17 subtasks by stage and dependency.

Outcome

You have a verified document with reasoning attached to the task, and the task itself unfolds into a clear work plan.

The first step changes nothing in the code

## Start with a question about your project

Connect a repository and ask the system how your code is built: it reads the source code and answers in minutes, changing nothing. A starting balance is provided to try it out.

[Connect a repository](https://buff.systems/app) [Write to us](mailto:info@buff.systems)

Companies and sole traders can pay by bank transfer and receive closing documents