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

# Quickstart

> Complete your first Blitzy workflow in minutes

Get from zero to a Blitzy pull request. Choose your path based on whether you're starting fresh or working with an existing codebase.

<Accordion title="First time? Connect your source control">
  1. Go to **Settings > Integrations**
  2. Click **Connect** for your provider (GitHub, GitLab, Azure DevOps)
  3. Complete OAuth authorization
  4. Select repositories to enable

  **Verify:** Connection shows "Connected" in **Settings > Integrations**
</Accordion>

## Create a Project

<Steps>
  <Step title="Go to Workspace" />

  <Step title="Create a new project">
    Click [**Create new project**](https://platform.blitzy.com/workspace/project-name).
  </Step>

  <Step title="Select your path">
    Choose **New Product** or **Existing Product**.
  </Step>
</Steps>

<Note>**Start with an existing codebase when possible.** The Existing Product path gives Blitzy full context of your architecture and patterns, which produces higher-quality output. Use New Product only when you are truly starting from scratch with no existing code to build on.</Note>

<Tabs>
  <Tab title="Existing Product">
    <Steps>
      <Step title="Configure environment">
        Add build instructions and environment variables in project settings.

        **Optional:** Create a `blitzy` branch for high-activity repos.
      </Step>

      <Step title="Write ingestion prompt">
        Describe your architecture, patterns, and domain terminology.

        **Template:** [Codebase Ingestion](/templates/documentation-onboarding/codebase-ingestion)

        <Note>Templates are not required but highly recommended - they're structured to give Blitzy the context it needs for thorough output.</Note>
      </Step>

      <Step title="Review Tech Spec">
        Blitzy generates a specification of your codebase. Refine as needed.
      </Step>

      <Step title="Write generation prompt">
        Describe the feature or changes to add.

        **Templates:** [New Feature](/templates/feature-product-development/new-feature), [Refactor](/templates/code-quality-maintenance/refactor), [Bug Fix](/templates/code-quality-maintenance/bug-fix)

        **Optional:** Add [Rules](/prompt-engineering/rules)

        <Note>Rules are reusable directives that enforce quality standards consistently across generations - code style, test coverage, security, and more. Add once to the project instead of repeating the instruction in every prompt.</Note>
      </Step>

      <Step title="Review Agent Action Plan (AAP)">
        Blitzy generates a structured plan showing the files it will create/modify and its overall approach before any code is written.

        **Actions:** Approve, Discard, or Edit inline.

        <Note>For most changes, **Discard and regenerate** with an updated prompt is the recommended approach. Inline edits are best reserved for small, targeted corrections, as larger edits can produce inconsistencies in the generated output.</Note>
      </Step>

      <Step title="Generate">
        Blitzy creates code and opens a PR to your target branch.
      </Step>

      <Step title="Review Project Guide">
        Documentation of changes and how they integrate with existing code.

        <Note>After merging, return to Step 3 for your next generation.</Note>
      </Step>
    </Steps>
  </Tab>

  <Tab title="New Product">
    <Warning>
      **New product code generation is currently under maintenance.** Temporarily, use the existing product workflow instead:

      1. Create a clean GitHub repo and branch
      2. Onboard the repo (ignore the initial Tech Spec)
      3. Select **Add Feature** from the **Build** button
      4. Add your project requirements
      5. Generate code

      You'll receive a PR against your base branch.
    </Warning>

    <Steps>
      <Step title="Write prompt">
        Describe what to build: objective, tech stack, key features, success criteria.

        **Template:** [New Product](/templates)

        <Note>Templates are not required but highly recommended - they're structured to give Blitzy the context it needs for thorough output.</Note>
      </Step>

      <Step title="Review Agent Action Plan (AAP)">
        Blitzy generates a structured plan showing the files it will create and its overall approach before any code is written.

        **Actions:** Approve, Discard, or Edit inline.

        <Note>For most changes, **Discard and regenerate** with an updated prompt is the recommended approach. Inline edits are best reserved for small, targeted corrections, as larger edits can produce inconsistencies in the generated output.</Note>
      </Step>

      <Step title="Generate">
        Blitzy creates code and opens a PR to your target branch.
      </Step>

      <Step title="Review Project Guide">
        Documentation of what was built and how to extend it.
      </Step>
    </Steps>
  </Tab>
</Tabs>

## Next Steps

<CardGroup cols={3}>
  <Card title="Test" icon="flask-vial" href="/project-lifecycle/code-review">
    Check out the branch and verify functionality
  </Card>

  <Card title="Merge" icon="code-merge" href="/pull-request-review/merge">
    Follow your review process and merge
  </Card>

  <Card title="Refine" icon="arrows-rotate" href="/pull-request-review/refine">
    Iterate with follow-up prompts
  </Card>
</CardGroup>