# Quickstart

From a business requirement to a plan in your issue tracker, in about five minutes.



<Callout>
  You do not need an issue tracker connected to finish this. You can export the plan instead and
  connect Linear, Jira or Radial later.
</Callout>

<Steps>
  <Step>
    ### Create a project [#create-a-project]

    From your dashboard, create a project and give it the name your team already uses for this product.
    A project holds plans, and later it holds the connection to your issue tracker.
  </Step>

  <Step>
    ### Write the business requirement [#write-the-business-requirement]

    Open a new plan and describe what the business needs, in plain English. No format, no template. A
    paragraph is enough:

    ```text
    Customers keep emailing us to ask for last month's numbers as a PDF.
    We want them to save a report once and have it arrive on a schedule.
    ```

    Write what the business wants, not the implementation. Deciding how is the agent's job, and yours
    to correct.
  </Step>

  <Step>
    ### Answer the agent's questions [#answer-the-agents-questions]

    The agent researches your Context first, then asks you what it still needs. Expect two or three
    questions, and expect them to be the awkward ones: what "monthly" means in someone else's time
    zone, who keeps receiving a report when the person who set it up leaves, what a schedule does when
    the report behind it changes.

    This step is what makes the Specs specific. Skipping it produces a plan that reads well and cannot
    be built.
  </Step>

  <Step>
    ### Review the Specs [#review-the-specs]

    You now have a plan: a tree of Specs, each with acceptance criteria, an effort and a readiness of
    Rough, Shaping or Ready.

    Read the acceptance criteria first, not the titles. That is where a plan is right or wrong. Ask for
    changes in the same conversation ("SPEC-3 should cover weekly as well as monthly") and the agent
    rewrites it in place.
  </Step>

  <Step>
    ### Push to your issue tracker [#push-to-your-issue-tracker]

    Connect Linear, Jira or Radial, then push. The plan lands as issues and sub-issues with its
    hierarchy and its "needs first" dependencies intact, and every Spec keeps its acceptance criteria
    in the issue body.
  </Step>
</Steps>

## What you end up with [#what-you-end-up-with]

A plan of record in your issue tracker, and a conversation in Plansmith you can come back to when
the plan needs to change. Re-pushing updates what Plansmith created.

<Cards>
  <Card title="Core concepts" href="/docs/core-concepts">
    Team, Project, Plan and Spec: the four words the rest of the docs use.
  </Card>

  <Card title="Push to your issue tracker" href="/docs/push-to-your-issue-tracker">
    Linear, Jira and Radial, and what re-pushing does to edits.
  </Card>
</Cards>