Document deferred UI screens for chains and buckets

Fleshes out the "not built" notes in both specs into actionable
follow-up scope: what data/API layer already exists, what the screen
needs to do, and precedent to follow.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EZ7ikw2ukGJFTHE3bJS7zL

1 files changed, 9 insertions, 0 deletions

diff --git a/docs/superpowers/specs/2026-07-15-recurring-maintenance-buckets-design.md b/docs/superpowers/specs/2026-07-15-recurring-maintenance-buckets-design.md
index 2bfb5ba..69ce370 100644
--- a/docs/superpowers/specs/2026-07-15-recurring-maintenance-buckets-design.md
+++ b/docs/superpowers/specs/2026-07-15-recurring-maintenance-buckets-design.md
@@ -68,3 +68,12 @@ Store-layer tests for the selection algorithm (given a pool with known staleness
 - UI design.
 - Multi-bucket item membership (exactly one bucket per item, per the interview).
 - Any interaction with the linear-task-chains feature ([[doot-future-task-scheduling-ideas]] item 4) — buckets and chains are independent concepts, not designed to compose.
+
+## Deferred: bucket-management UI
+
+Not built as of 2026-07-17. What exists: the full CRUD API and store layer (`CreateBucket`, `GetBuckets`, `AddBucketItem`, `RemoveBucketItem`, all with store+handler tests), reachable at `GET/POST /api/widget/buckets`, `POST /api/widget/buckets/{id}/items`, `POST /api/widget/buckets/{id}/items/remove`. The Defer action itself (the part end users actually interact with day-to-day) IS live on both web timeline rows and the Android widget row. What's missing is the create/configure/manage surface — there is currently no way to create a bucket or assign a task to one except direct API calls.
+
+Rough shape for whoever picks this up, per the spec's own minimum bar ("create bucket, add/remove pool items, see cycle settings"):
+- **Web**: closest existing precedent is the Projects list under Settings (`HandleWidgetProjectsGet`/`Create` + whatever template renders it) — a Buckets management page would follow the same shape: a list of buckets (name, cycle_days, pick_n, pool size), a create form, and per-bucket pool membership (search/pick an existing task, or type a new title, to add; remove from the same list).
+- **Android**: per the spec's explicit scoping, this is web-only — the widget only needs Complete/Defer on items it already displays, which is done.
+- No scoring-formula tuning UI needed — that's explicitly out of scope in the spec above, not just deferred.