> ## Documentation Index > Fetch the complete documentation index at: https://docs.getvector.me/llms.txt > Use this file to discover all available pages before exploring further. # Delivery preparation > Move delivery cycles through configurable stages, let AI draft a spec, plan and tasks along the way, and approve the work before it reaches your developers. Delivery preparation is where a feature you've decided to build turns into something a development team can pick up. Each [delivery cycle](/delivery/plan-a-delivery-cycle) moves through a pipeline of stages. At each stage AI can draft an artifact — a spec, a plan, a task breakdown — from everything the feature's dossier knows, and the stages you mark as gates wait for your approval before the work goes on. Open it from **Features** → **Delivery preparation** in the left menu. ## See where the work stands The **Kanban** tab shows one column per stage and one card per active cycle; **List** shows the same cycles as a table, in stage order. Each card carries the feature's name, the cycle number and title, the feature's summary, and a row of signals from the feature's dossier: | Chip | What it tells you | | ----- | ---------------------------------------------------------------------------------------------- | | `#12` | The cycle's number across the whole workspace | | ▦ | How many competitors have the feature | | 🗣 | How much customer feedback it has from [meeting analysis](/features/meeting-analysis), by team | | 💬 | How many signals it has from public reviews | | 🔗 | Linked items | A card showing **⏳ awaiting approval** is waiting for you. To move a cycle to another stage, drag its card to that column, or change the stage in its row on **List**. ## Set up your pipeline Each column is a stage, and the stages are yours to shape to how your team works. A new workspace starts with a pipeline such as **Backlog**, **Specify**, **Plan**, **Review**, **Tasks** and **Ready for dev**. Two markers next to a stage name show how it behaves: * **✦** — a skill is linked: AI can draft this stage's artifact. * **🔒** — the stage is an approval gate: a cycle waits here until someone approves it. To change the pipeline, click **⚙ Stages**. For each stage you can: * rename it, recolor it, and move it up or down * link a **skill** — the instructions AI follows to draft that stage's artifact * tick **auto** to run the linked skill as soon as a cycle enters the stage * tick **gate** to make the stage wait for approval * delete it — its cycles move to the neighboring stage Add a stage with **+ Add stage**. You can't delete the last one. ## Let AI draft each stage When a cycle enters a stage with a linked skill and **auto** on, AI starts drafting that stage's artifact in the background. It works from the cycle, the feature's [dossier](/features/feature-dossier), and the artifacts earlier stages produced — so the plan builds on the spec, and the tasks build on the plan. While it runs, the card shows what it's doing and for how long. Stages without a gate hand the cycle on to the next stage automatically, so a cycle can run through several stages on its own and stop at the first gate, or at the last stage. Move a cycle by hand while a skill is running, and the run stops. To run a stage's skill yourself, open the cycle and click **✦ Generate** — or **↻ Re-run** once there's an artifact. Each run uses your [AI key](/getting-started/connect-a-provider). ## Approve work at a gate When a cycle reaches a gate and the stage's work is done, its card shows **⏳ awaiting approval**. Open the card, read the artifact, and choose: * **Approve** — the cycle can move on. * **Override** — let it through without approving. Vector asks for a reason and records it. A cycle can't be dragged out of a gate until it's approved or overridden. Every cycle keeps a record of who approved or overrode which gate, and why. ## Review a cycle's work Click a card to open the cycle. Besides its title, stage and description, you'll find: * **Artifacts** — one per stage, with every version kept, so you can see how a spec changed between runs. * **Feature signals** — coverage by competitor, public reviews and meeting analysis, each linking into the feature's page. **↗ Open feature page** takes you there. * **Linked items** — the feature, and links to other cycles: relates to, blocks, duplicates, clones or causes. A **blocks** link is the same dependency the [roadmap](/delivery/roadmap) draws. * **Run history** — every run, with its stage, model and cost. * **Approvals** — who approved or overrode which gate, and why. At the bottom, **Cancel** or **Archive** takes the cycle off the active board and keeps its artifacts. **Delete cycle** removes it. ## Keep track of work that isn't a feature Bugs, infrastructure, housekeeping — work that isn't a feature — go on the **Chores** tab, so they stay off the delivery board. Type a chore and click **Add**, tick it when it's done, or delete it with **✕**. Chores don't move through stages and don't appear on the roadmap. ## Outline larger initiatives The **Delivery** tab is a simple outline of larger work: **Initiative → Epic → Story → Task**. Add an initiative with **+ Initiative**, then add children level by level with **+ Epic**, **+ Story** and **+ Task**. The outline is separate from delivery cycles and from the stages on the board. ## Where to go next How a feature gets onto the board. Scheduling cycles over time.