docs: prioritized feature backlog (docs/features) - #647
Draft
palmithor wants to merge 1 commit into
Draft
Conversation
🚀 Preview Environment DeployedPreview URL: https://scorebrawl-pr-647.coding-cowboys.workers.dev Test Account:
This preview environment will be automatically cleaned up when the PR is closed. |
🎭 E2E Test Results✅ 20 passed | ❌ 0 failed | ⏱️ 67.7s
📊 View HTML Report Last updated: 2026-08-10T11:04:02.801Z |
Feature docs from a full app walkthrough + backend triage. Each file is a brief, actionable starting point for a feature. Priority-ordered 01-18 via filename prefix; README.md indexes the backlog and rationale.
palmithor
force-pushed
the
docs/feature-backlog
branch
from
August 10, 2026 11:02
3514e9f to
0509153
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Feature backlog from a full app walkthrough + backend triage. 18 candidate features documented as brief, work-startable briefs in
docs/features/, priority-ordered via filename prefix (01 = highest).What's here
README.mdindexes the backlog with the priority rationaleTop of the backlog
season_winnerachievementPurpose
Discussion artifact — no code changes. Let's use the PR to align on priorities, merge/trim/split stories, and pick what to take forward.
Suggested sequencing
01 → 02 → 03 form a coherent engagement slice (same event/achievement plumbing). 05, 06 are independent and cheap. 15 (PWA/push) depends on 01.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.