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

# Generate your first blueprint

> Ask the agent for a card, review what comes back, keep what's good.

A **blueprint card** is a structured document the agent drafts for you: a Vision, a Problem statement, a set of Personas, an OKR set. Cards live in Strategy, External research and Development hubs.

<Steps>
  <Step title="Open a hub and press Create card">
    In any card-based hub, press **Create card**. Pick a card type from the list, or start blank.
  </Step>

  <Step title="Let the agent draft it">
    The agent reads everything attached to the strategy — your description, other cards, anything in the Context Bank — and drafts the card section by section. This takes a few seconds.
  </Step>

  <Step title="Review and edit">
    Every section is editable. Rewrite a paragraph, delete a section, ask the assistant to make it sharper. The card is yours the moment it lands.
  </Step>

  <Step title="Link it">
    Cards can reference other cards and roadmap items. Linking is how the agent keeps later drafts consistent with earlier ones.
  </Step>
</Steps>

## Good first cards

* **Problem statement** — forces clarity on what you're solving and for whom.
* **Personas** — who you're building for. Later cards draw on these heavily.
* **Vision** — where this lands if it works.

## When the draft is wrong

It will be, sometimes. Two fixes work better than deleting:

1. **Add context.** Tell the assistant the thing it didn't know, then regenerate the section.
2. **Edit the section directly.** Your edits become context for the next card.

<Note>
  Cards you've edited are never overwritten by a later generation. Regeneration only touches the section you ask about.
</Note>