Scored on three axes: Atomicity (1-5), Clarity (1-5), Readiness (1-5). Ready-for-dev requires all three ≥ 4.
Ordered by priority (unblock value + effort).
| # | Card | Reason |
|---|---|---|
| #110 | WebAuthn registration endpoint (Raptor) | 5/5/4 — design branch exists, scope crystal-clear, no deps. First card in the auth sequence; unblocks #111–#115. |
| #138 | Dep bump: Flask/Werkzeug/flask-cors/requests/gunicorn | 4/5/5 — table of packages, risk flags, AC, test plan all present. Pick up immediately; pip-audit is warn-only in CI until this lands. |
| #95 | Automate semver tagging and changelog | 4/4/4 — tooling choice deferred to impl (suggest release-please), clean scope. Unblocks #97, #99. |
| #97 | GitHub Actions deploy workflow to Heroku | 4/4/4 — smoke script exists, scaffolding from PR #135 landed tonight. Write the YAML. |
| #91 | Migrate Antlers CRA → Vite | 4/5/4 — all 9 migration steps explicit, no external deps. Removes 6 HIGH npm audit vulns. Decide Jest vs. Vitest before starting. |
| #103 | Integrate Sentry error tracking | 4/4/4 — vendor chosen (user comment: "let's go with Sentry"). Flask + React SDK integration, one PR. |
| #82 | Bug: compareStrategies hits unregistered endpoint | 4/4/4 — run a grep; if zero callers, delete (5-min fix). Quick win. |
| #98 | Author and drill a production rollback runbook | 4/4/4 — runbook writing is unblocked now; staging drill waits on #96. Start the doc. |
Cards blocked on something only you can answer.
| # | Card | Question |
|---|---|---|
| #121 | Raxx brand system (logo, palette, type, tokens) | Who is doing the design work? In-house, contracted designer, or AI-assisted? This is the critical-path dependency for 8 other cards in Epic #120. |
| #122 | Raxx brand voice and messaging guide | PR #118 landed strategy docs — does docs/marketing/messaging.md exist? If yes, review it and leave an approval comment to unblock #123–#126. |
| #112 | Email verification service | Pick the email provider: SendGrid, SES, or Postmark. Heroku add-on for SendGrid is lowest friction. Unblocks #112 and the waitlist flow. |
| #107 | Build waitlist signup with email verification | Email provider (same as above) + confirm sending domain + confirm storage (Heroku Postgres add-on?). |
| #125 | getraxx.com about + contact pages | Confirm contact email (hello@getraxx.com?) and team attribution (names or "built by a small team"). |
| #124 | getraxx.com pricing page | Confirm three-tier structure (Free/Pro/Pro+), $29/$79 price points, and that docs/marketing/pricing.md is ready. Blocks this card entirely. |
| #42 | Graphs not rendering in real user workflow | Is this bug still reproducible on the current main branch? If charts render correctly now, close this card. |
| #35 | CLI data retrieval with table output and CSV export | Sprint 3 Wave 2 said "execution complete." Is this card actually done? If python cli.py historical-data --symbol SPY works, close it. |
| #43 | EPIC: v2.0.0 contract-first rewrite | Is this epic still the plan, or has it been superseded by #94 + Epics #78–#81? Recommend rename to "v1.0 Technical Foundation" and reframe rather than close — the sub-cards have real value. |
| #96 | Provision Heroku staging and production apps | PR #135 landed Heroku scaffolding tonight. What remains from this card's AC? If apps are provisioned and config vars are set, close or scope to the remaining documentation items. |
| #142 | Connect GitHub + Slack to claude.ai | GitHub and Slack connector setup are UI actions (< 10 min). Sentry option (a/b/c) needs your call. |
Cards that need a design decision before dev can start.
| # | Card | Question |
|---|---|---|
| #114 | GDPR DSR endpoints | Background job runner: in-process APScheduler vs. Heroku Scheduler add-on vs. background worker dyno. APScheduler doesn't survive Heroku dyno restarts cleanly — architect needs to decide before implementation. |
| #56 | DB technology decision | Can SQLite (WAL mode) handle the target scale (5 years of intraday OHLCV, 500 symbols, p95 < 200ms)? If yes, close this card and proceed. If no, pick from Heroku Postgres (simplest for Heroku) vs. DuckDB+S3. |
| #104 | Launch public docs site foundation | Framework decision for "fur-docs": Starlight (Astro-based, excellent theming) is recommended for the custom-themed approach. One-line decision unblocks #131, #132 and all docs site work. |
| #132 | raxx.io themed API reference | Viewer choice: Redoc vs. Scalar vs. Elements. Scalar is recommended for its theming flexibility. Unblocks after #104 framework and #121 tokens exist. |
| Newer card | Superseded by | Recommendation |
|---|---|---|
| #108 (pricing placeholder + about + contact) | #124 (pricing) and #125 (about + contact) | Close #108 in favor of the better-spec'd split cards. |
| #106 (TradeMaster marketing landing) | #123 (getraxx.com landing, Raxx-branded) | Close #106. Brand decision is resolved ("Raxx"). #123 is the correct card. |
| #54 (Sprint 4: SemVer for v2.0.0) | #95 (Automate semver tagging and changelog) | Close #54. #95 has proper spec and is ready for dev. |
All filed 2026-03-04 (49 days ago). Sprint 3 and 4 planning/process cards that are no longer the working model.
| # | Card | Reason |
|---|---|---|
| #32 | Backlog Grooming: Sprint 3 candidate prioritization | Sprint 3 closed. Planning artifact. |
| #33 | Sprint 3 Planning: Commit sprint scope and owners | Sprint 3 closed. Planning artifact. |
| #38 | Sprint 3 QA Card: E2E verification matrix | Sprint 3 closed. QA lane marked complete in Wave 2. |
| #39 | Sprint 3 Bug Lane: Rapid response | Sprint 3 closed. Not an issue — a workstream. |
| #55 | Sprint 4: Rewrite architecture and migration plan | Superseded by #131 (raxx.io concepts) + #98 (rollback) + #100 (first prod cut). |
| #62 | Sprint 4: Sprint planning and agent lane orchestration | Current model is Epic 1-4 + labeled issues. Not needed. |
| #64 | Sprint 4: Chart generation coverage across all core functions | One sentence, no AC, no scope. File specific chart-gap cards instead. |
Candidates to keep but flag for attention (still have value if scoped):
| # | Card | Note |
|---|---|---|
| #37 | Sprint 3: Implement APM instrumentation | Wave 2 "complete" — verify what shipped; close if done. |
| #40 | Sprint 3: APM + synthetics architecture spike | cli.py synthetic-checks exists; verify if Sentry resolves remaining gaps. |
| #67 | Feature: Database tools | Needs user input on which DB problems exist before any work is possible. 49 days old. |
| # | Card | Suggested split |
|---|---|---|
| #90 | In-window trade simulator + auto-schedule follow-on orders | Split into: (1) In-window backtest simulation panel (Phase 1), (2) Follow-on order scheduling (Phase 2), (3) Auto-execution with kill-switch (Phase 3). Keep #90 as the tracking epic. |
| #85 | Options chain viewer + iron condor builder | Split into: #85a options chain viewer (Phase 1, ready once Alpaca options route is wired), #85b iron condor builder (Phase 2, depends on #85a). Close #85 after filing sub-issues. |
Already labeled type:epic and correctly structured: #78, #79, #80, #81, #94, #120.
Cards confirmed as groomed and skipped: #83, #84, #86.
For the user reading this in the morning: