Get started
Choose the right lane
Choose the smallest path that gives the work enough structure and verification.
Lane comparison
| Path | Best for | How to start | Execution |
|---|---|---|---|
| Plan | Questions, discovery, and shaping work before code | Select the Plan tab | Main agent |
| Full lane | Meaningful features, architecture or contract changes, rollout work, or higher-risk delivery | Select Full lane in Build, or type /full-lane | Coordinated multi-stage workflow |
| Quick lane | Small, low-risk features and fixes with a clear outcome | Select Quick lane in Build, use plain text, or type /mini-spec-lane | Main agent fast path |
| Direct agent | One focused specialist task | Select Direct agent or mention @agent | Single-node run |
Plan
Use Plan to clarify a request, compare approaches, inspect context, or create a plan without starting repository changes. When the plan is ready, move the session to Build and choose the appropriate lane. A session that has committed to Build does not move back to Plan in the current product.
Full lane
Full lane is the Project Lane path. It coordinates Product, Architect, Lead, Implement, Code Review, Verify, Deploy Plan, and Learning work around one durable request. Use it when an early design decision or missed contract could create downstream rework.
Quick lane
Quick lane is for a small, low-risk feature or fix with a clear outcome and limited impact. Use Full lane when the work changes contracts, data models, onboarding, release behavior, or rollout. Prinevo still captures a compact mini-spec before editing.
Direct agent
Direct agent runs one named specialist inside a single-node workflow envelope. Use it for focused work such as asking Verify to validate a pull request or asking Architect to review a design. It does not silently become the full multi-stage workflow.