DDovel Team
CockpitOverview & what needs youChatAsk the Product agentFigma SyncLive diff vs the PRDFeaturesEvery feature & its spec✓FlowsAI-inferred from the designsBacklogWhat's left to buildScreensPages, specs & criteriaRoadmapNew in Figma → proposalsDriftWhat changed in designMeetingsCalls → decisions → PRDTeamPeople + their AI support
Figma Dovel iQ v0.3 MVP (Active) · 2026-10-10
Dovel Team
PProduct agentsupports Design & PM✓BBackend agentsupports EchecomingFFrontend agentsupports the FE buildcomingQQA agentsupports QualitycomingOOrchestrator agentsupports Opscoming
Product / Transaction Capture & Reconciliation / Confirm Spend Status

Confirm Spend Status

SCR-RECON-01 · Transaction Capture & Reconciliation

Confirm Spend Status
ScopedFigma 504:6227design drifted since last sync

Layout

Establish, at the reconciliation step, whether the project has any actual spend yet — so Dovel knows whether to move into expense capture now or simply record a valid "no spend yet" state and follow up later.

States

- **Default**: both options visible, neither pre-selected. - **"No" recorded**: proceeds onward; no error styling, no blocking message.

Acceptance criteria

  • The screen asks "Has spending on this project started?" with exactly two options: "Yes" and "No, not yet".
  • Choosing "Yes" navigates to SCR-RECON-02.
  • Choosing "No" records that no actual spend has started and lets the user continue.
  • The "No, not yet" path renders as a normal, valid completion state — never as an error or warning.
  • After project creation, Dovel can re-surface this screen (or route directly to SCR-RECON-02) to prompt the user to add actual spend when relevant.

Endpoints

None mapped yet — the backend agent will own these.

In flows

Confirm Spend Status & Choose Capture Method
P
Product agent
supports Design & PM
×