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

After you have created an implementation plan, you can review the details of that plan. The **Plan** tab includes several sections covering the full details of the generated plan, including a plan summary, extensive implementation details, and the implementation steps that Appfire QueueZero maps out. See below for additional information on each section. 

The **Plan** tab includes a few functions at the top right of the tab content: 

- **Copy context** - Export a Markdown file that includes the full context that is sent to your model by QueueZero. This can be used to run comparison planning using alternate models.
- **Refresh (Jira only)** - Refresh the tab contents; during planning, this will reload the tab to display the most current version of the plan.
- **Walkthrough** - QueueZero will provide a “guided tour” of the implementation plan.
- **Execute plan** - Once a plan has been approved, start the execution process.

![Resolver full plan details for a work item](media://0a9677ff-922f-4907-bbb0-025025d51137)

## Resolution plan

### Work item overview

The top **Overview** section (Figure 1, point 1, right) provides a simple dashboard detailing the following:

- The number of files QueueZero has identified to create or modify
- The number of steps in the implementation plan
- The number of tests planned
- The Rollback plan
- The Current Status of the plan, detailing the plan’s approval and execution status
- The total usage across all plans and executions
- If the plan has been executed, a link to the PR generated

### Plan overview/Plan summary (Jira)

The **Plan summary** (Figure 1, point 2, right) is a brief summary of QueueZero’s goal, the impact of it’s proposed changes, and any risks it has identified. In Jira, click **Show full summary** to see an expanded explanation of QueueZero’s logic and plan. 

### Assumptions

Any assumptions made by your selected model will be listed here (Figure 1, point 3, right). These can be reviewed and modified to generate a new execution plan if the model made an incorrect choice. See [Refine and rerun](https://appfire.atlassian.net/wiki/spaces/RS/pages/3424387078) for more information on assumptions and plan regeneration.  

### Steps/Implementation details (Jira)

The **Steps **section (Figure 1, point 4, right) includes the files that QueueZero accessed in creating its plan, and specific details on each of the files that will be created or modified when executing the plan. Some details for new or updated files may be hidden for readability; in Jira, click **Show more** to expand the details and under each file, click **Show full rationale** to see additional details on QueueZero’s logic. 

### Implementation steps (Jira only)

The **Implementation steps** subsection includes the specific steps QueueZero will take, in order, when implementing its plan. Click **Show all steps** at the bottom of the list to see additional steps that may not be listed initially.

### Plan context (standalone only)

The **Plan context** section (Figure 1, point 5, right) contains a summary of the files QueueZero used as context for generating its plan; this includes files that will be affected during code generation, and files that were read but will not be affected. Additionally, it displays metadata about the plan, including the complexity of the plan, which correlates to the workflow QueueZero will use. 

### Testing and verification

The **Testing and verification** section (Figure 1, point 6, right) lists the specific tests and steps that QueueZero will take to verify that its changes are accurate and functional. If available, click **Show all checks** to see any additional tests that may be planned. 

## Next steps (Jira only)

Any additional steps that QueueZero has identified will be listed in this section.

## Plan information (Jira only)

The **Plan information** section includes basic details about the plan, including its ID, version, and the workflow type (Easy, Medium, or Complex) that QueueZero chose to implement. This information can be used in the standalone app to review more detailed data about the plan.