> ## Documentation Index
> Fetch the complete documentation index at: https://docs.augmentcode.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Requirements → Ticket

> Turn feature requirements into a reviewed design and actionable tickets.

## How it works

[Project Builder](/cosmos/experts-project-builder) is an [Expert](/cosmos/experts), a specialized agent. Give it a feature brief, mockup, existing ticket, or rough design. It researches the relevant code and drafts a design for your review. On request, it breaks the reviewed design into ordered tickets with dependencies.

The diagram shows the **ticketed path**:

```mermaid theme={null}
flowchart TD
    brief["👤 Human: provide a feature brief"] --> design["🤖 Project Builder: research and draft a design"]
    design --> review["👤 Human: review scope and architecture"]
    review -->|Revise| design
    review -->|Approve design and request tickets| tickets["🤖 Project Builder: create ordered tickets"]
    tickets --> authorize["👤 Human: authorize implementation"]
    authorize --> next["Ticket → PR"]
    classDef human fill:#fff7ed,stroke:#c2410c,color:#7c2d12;
    class brief,review,authorize human;
```

Ticket creation is optional. When you request implementation, Project Builder delegates the work to PR Author workers and coordinates delivery.

## Where you participate

* **Define the outcome.** Provide the problem, success criteria, constraints, and what is out of scope.
* **Review the design.** You decide scope and architecture; the Expert researches options and explains tradeoffs. Resolve open questions before handing work off.
* **Choose the next step.** Ask for tickets, implementation, or both. A design request alone is not permission to change code.

## Template Experts

* [Project Builder](/cosmos/experts-project-builder) researches, drafts designs, and breaks work into tickets; it can also coordinate delivery when requested.
* [PR Author](/cosmos/experts-pr-author) implements and tests work you hand off after planning.

## Set it up

1. **Connect your tools.** Connect your code host and, for ticket creation, your tracker. Provide access to the relevant repositories and product context.
2. **Ask [Cosmos Advisor](/cosmos/advisor/overview) to configure Project Builder.** Tell it which code host and ticket tracker you use.
3. **Start Project Builder with a feature brief.** Review its design and open questions, then decide whether to request tickets or implementation.

Example Advisor prompt:

> Set up Project Builder for \[code host] and \[ticket tracker] to turn feature requirements into designs and tickets.

## Next step

Use [Ticket → PR](/cosmos/software-factory/ticket-to-pr) to turn approved work into a draft change for review. Already have a clear ticket? Start there directly.

## Further reading

* [Accelerating large engineering projects with Cosmos](https://www.augmentcode.com/blog/accelerating-large-engineering-projects-with-cosmos)
* [How we built Augment's software factory](https://www.augmentcode.com/blog/beyond-ai-coding-agents-how-we-built-augments-software-factory)
* [Software Factories in September 2026](https://igoro.com/archive/software-factories/)