---
title: "Generate the implementation plan"
canonical: "https://support.appfire.com/space/RS/3158507969/Generate%20the%20implementation%20plan"
format: markdown
---
> Macro (aura-html)

As a developer, Appfire QueueZero can accelerate your process by leveraging AI models to create and implement a plan to fulfill the requirements of your Jira work items. This process is initiated from within a work item:

- In the standalone app, go to the Space for your work items and open each item from the list
- In Jira, open the detail view for your work item and verify that the QueueZero panel is visible by going to **View app actions > QueueZero**.

## Create a plan

1. Open the work item and click **Resolve**.
2. QueueZero reviews the work item and uses available repository and knowledge-source context to prepare the resolution. It chooses the relevant context and repository for the changes. If these are correct, click **Start now**; if you are using Single-shot mode, QueueZero will plan and implement the changes.   
If you want to make changes to the chosen configuration, click **Adjust settings** and follow the steps below.

> Macro (excerpt)
> 
> //To be added to the end of Point 2, above, once the target page is live: 
> 
> You can proceed to [Extend the code locally](https://appfire.atlassian.net/wiki/spaces/RS/pages/3164831770).

> ℹ️ ### If QueueZero recommends refining the work item
> ℹ️ 
> ℹ️ If the work item does not contain enough information, QueueZero may start the **Refine Ticket **process before the resolution starts.
> ℹ️ 
> ℹ️ You can refine the work item to add more context, or select **Skip ticket refinement** to continue without refining it.
> ℹ️ 
> ℹ️ Skipping refinement applies only to the current attempt. QueueZero may recommend refinement again the next time you resolve the work item. A work item that has already been refined is not prompted again.
> ℹ️ 
> ℹ️ For more information, see [Refine a work item](https://appfire.atlassian.net/wiki/spaces/RS/pages/3483271197).

3. Select whether **Single-shot** mode is enabled. **Single-shot mode** is enabled by default.
  When it is enabled, QueueZero generates the implementation plan and automatically continues to execution and pull request creation.
  Turn off **Single-shot mode** if you want QueueZero to pause after generating the plan so you can review and approve it before code is written.

6. Review and update **Advanced settings** if needed. See below for more information.
7. Click **Start resolution **to use the recommended settings and begin the resolution.

## Advanced settings

You do not need to change these settings for every resolution. Use **Advanced settings** when you want more control over how QueueZero handles the work item.

### Workflow Type

Under **Advanced**, use **Workflow type** to control how QueueZero approaches the work item:

- **Auto** — QueueZero determines the appropriate workflow.
- **Easy** — Uses a direct fix with minimal planning.
- **Medium** — Generates a standard implementation plan before execution.
- **Complex** — Gathers additional requirements and creates a specification before implementation.
- **Re-assess with AI** - *Only available for work items that have an existing pull request*. Select if you want QueueZero to evaluate the work item again instead of reusing the previous assessment.

QueueZero selects the workflow automatically by default, but you can override its selection. Your selection takes precedence over the AI assessment and is reused for future runs.

For a **Complex** work item, QueueZero gathers additional requirements, generates a plan specification for you to review, and waits for your approval before creating the implementation plan.

#### Security classification

After QueueZero assesses a work item, you may also be able to classify it as **General** or **Security**.

Security-classified work items receive additional verification.

### Other advanced settings

Additional settings include:

- **Auto-resolve CI/CD failures** — Lets QueueZero automatically attempt to fix CI/CD failures in the pull request. This option is enabled by default.
- **Close previous PR** *(standalone app only)* — When rerunning a work item, close the previous pull request and create a new one.
- **Re-index before planning** — Rebuild QueueZero's repository analysis using the latest code before planning.

When you're ready, click **Start resolution**.

## After you start

QueueZero generates the implementation plan and displays its progress.

What happens next depends on **Single-shot mode**:

- If **Single-shot mode is enabled**, QueueZero continues automatically from planning to execution and creates a pull request.
- If **Single-shot mode is disabled**, QueueZero pauses after generating the plan so you can review it before execution.

See [Review and refine](https://appfire.atlassian.net/wiki/spaces/RS/pages/3158213589) for information about reviewing an implementation plan before execution.

![user-PlanTab.png](media://950948af-0d3f-4b6c-a468-abd5df50b600)

## Dependency and security fixes

Some dependency and security upgrades use a specialized workflow instead of the standard planning process.

When this happens, you may see **Dependency / security fix — deterministic fast path** in the resolution settings or work item details.

This means QueueZero has identified the work item as an upgrade that can be applied and verified directly rather than following the standard implementation-planning workflow.