從原始使用者回饋中，做出對的功能

Paddi 是一個 PM Agent，把雜亂的使用者回饋整理成人與 Coding Agent 都能直接使用的清楚規格。

Problem

Reports has no export path today, so finance and ops teams fall back to screenshots or manual copy-paste. Nine customer interviews and three support calls over the past two months point to the same gap.

Goals

Export the rows and columns currently visible in the Reports table, respecting active filters.
Ship inside this sprint using the existing ReportsTable component.
Give finance teams a CSV they can drop straight into their month-end close workflow.

Non-Goals

Saved filter presets or scheduled recurring exports — tracked separately on the H2 roadmap.
XLSX or PDF output — CSV only for this pass.

Implementation notes

Wire the existing ReportsTable component to the unused csv.ts stub in src/reports/exporters — the stub already matches the rows and columns customers are asking for. The open question is where the export action lives in the toolbar, and whether large exports need to run asynchronously.

Acceptance Criteria

Export button appears in the Reports toolbar and respects active filters.
Exported CSV column order matches the on-screen table.
Exports over 10k rows complete without blocking the UI.

Rollout

Ship behind a feature flag to Northwind Traders first — the customer who asked most recently — then roll out to the rest of the enterprise tier once the export holds up under their month-end close.

Background

DraftFeatureReports

Bulk CSV export for the Reports dashboard

Enterprise customers keep asking for a way to export the Reports dashboard instead of copying rows out by hand.

Analysis

Nine customer interviews and three support calls over the past two months point to the same gap: Reports has no export path, so finance and ops teams fall back to screenshots or manual copy-paste. The existing ReportsTable component already renders the exact rows and columns customers want — csv.ts in the reports exporters folder has an unused stub from an earlier attempt, and EXPORT-142 has sat in the icebox since Q1.

Refine with Paddi...

Paddi 把原始回饋轉成可直接開發的規格，
每個決策都有你的程式碼與文件作為依據

來自各處的訊號，一個都不漏

串接回饋所在的來源，或透過內建輸入方式直接新增。
Paddi 會把相關回饋歸整成結構化的需求。

Slack

文字輸入

Paddi Chat

上傳檔案

轉寄 Email

給 Agent 與開發者

直接進入 Coding Agent 與開發者原本的工作環境

閱讀文件

dev — bash

npx paddi

從 CLI 取用，直接在終端機拉下任何一份規格文件，不必切換情境，也不用等人交接。

把 Paddi 當成 skill 執行，Coding Agent 就能自己取得所需規格，直接開工。

給團隊

直接在規格上問 Paddi 任何問題

ACAlex Chen

Fix checkout button overlap on mobile

Problem / Motivation

On narrow viewports, the primary CTA button overlaps the order summary total once the cart grows past two line items with a discount applied. Reported by 3 users this week, all on iOS Safari between 375–390px widths.

3 reports this week, all iOS Safari between 375–390px — the same viewport band.
Checkout is the highest-traffic screen on mobile; every added click here costs conversions.
The sticky footer hasn't been touched in 8 months and has no regression coverage below 400px.

"The button was literally on top of the price, I couldn't tell what I was paying."
— user feedback

Goals

Button stays clear of the summary total at every width under 400px.
No layout shift when the cart updates or a discount line is added.
Fix ships without touching the desktop layout or the CheckoutSummary component's public API.

Non-Goals

Redesigning the checkout summary — this is a targeted overlap fix, not a layout overhaul.
Extending sticky-footer regression coverage beyond the breakpoints named in this spec.
Changing button copy, sizing, or placement on tablet and desktop.

User Stories

As a mobile shopper with a full cart, I want the CTA button to stay visible above the total, so I can confirm my order before paying.
As an engineer on-call for checkout, I want the fix scoped behind a flag, so a bad rollout can be reverted without a hotfix deploy.

Acceptance Criteria

Summary and CTA never overlap at 375px, 390px, or any width in between.
Layout holds with 1 line item and with 6+ line items, discounts included.
No regression on tablet (768px) or desktop (1280px+) breakpoints.
Automated screenshot test added for the 375–390px band.

Rollout

Ship behind the existing mobile-checkout-fix flag, enabled for 10% of sessions first. Watch checkout completion rate and rage-click events on the CTA for 48 hours before rolling out to everyone.

Chat about this spec

What's the button's position once the cart is empty?

Same fix — the button clears the summary block whether the cart shows 0 or 5 items, so the empty state doesn't need a separate layout.

Any edge case with the sticky footer on iOS?

Only below 400px width — checked against 375 and 390 explicitly, since that's where the prior reports came from.

Type @ to mention...

工程師會問某個決策會對應到哪段程式碼、又有哪些邊界情況要注意。

設計師想知道為什麼這個改動是這樣界定範圍的，又是哪些回饋促成了它。

任何人提問都能直接看到每個決策背後的理由，不必再來敲你。

每一步都內建資安

絕不留存

Paddi 讀取你的程式碼以支撐分析，隨後即釋放。你的原始碼絕不會被儲存。

絕不用於模型訓練

你的任何資料都不會被用來訓練模型。

傳輸與儲存全程加密

所有經過 Paddi 與存放在 Paddi 的資料都經過加密。

正在取得 SOC 2 Type II 與 ISO 27001

我們從第一天就依這些標準打造產品，並會隨著 Paddi 成長取得正式認證。

成為最早用 Paddi 打造產品的團隊

搶先體驗預約導覽

我們正在讓少數團隊搶先加入。早點進來，開始交付真正該做的功能。

從原始使用者回饋中，做出對的功能

Problem

Goals

Non-Goals

Implementation notes

Acceptance Criteria

Rollout

Paddi 把原始回饋轉成可直接開發的規格，
每個決策都有你的程式碼與文件作為依據

來自各處的訊號，一個都不漏

找出每個需求背後真正的問題

把最重要的排在最前面

檢視分析，選定方向

AI 起草規格，由你收斂細節

依照團隊習慣的方式交付

直接進入 Coding Agent 與開發者原本的工作環境

直接在規格上問 Paddi 任何問題

Fix checkout button overlap on mobile

Problem / Motivation

Goals

Non-Goals

User Stories

Acceptance Criteria

Rollout

每一步都內建資安

成為最早用 Paddi 打造產品的團隊

從原始使用者回饋中，做出對的功能

Problem

Goals

Non-Goals

Implementation notes

Acceptance Criteria

Rollout

Paddi 把原始回饋轉成可直接開發的規格， 每個決策都有你的程式碼與文件作為依據

來自各處的訊號，一個都不漏

直接進入 Coding Agent 與開發者原本的工作環境

直接在規格上問 Paddi 任何問題

Fix checkout button overlap on mobile

Problem / Motivation

Goals

Non-Goals

User Stories

Acceptance Criteria

Rollout

每一步都內建資安

成為最早用 Paddi 打造產品的團隊

Paddi 把原始回饋轉成可直接開發的規格，
每個決策都有你的程式碼與文件作為依據