PlanningPokerPage
v1.0.33Updated 20 Oct 2026Composed example planning-poker estimation page: story-queue rail, current-story panel with acceptance criteria, a players table of hidden/empty/revealed vote cards, and a selectable estimate deck with computed consensus/spread reveal outcomes.
Preview
Live · 8 stories▸Why this is recommendedpageagileestimationplanning-poker+5
The default, out-of-the-box PlanningPokerPage.
- ✓Sprint estimation sessions
- ✓Scrum/agile team tooling
- ✓Reference for realtime voting screens
- i18n: a labels prop overrides every built-in string; English defaults, brand-free copy
- Story queue rail with current/upcoming/estimated states and locked points
- Current story panel with description + acceptance criteria
- Players table: face-down card backs, empty thinking slots, revealed numbers
- Selectable 0-21 / ? / coffee estimate deck with Reveal action
- Computed reveal outcome: success consensus banner or warning spread callout naming the outliers
- ✕Direct embedding
- ✕Board/pipeline views (use KanbanPage)
- ✕Backlog grooming lists (use BacklogPage)
Install
Ask your agent, or call the MCP tool directly. The resolved bundle is written into your project.
Usage
Tick variants in the left menu — each adds a tab with that variant’s real story source, the same code the preview above renders.
Props
labelsOverride every built-in string and aria-label (i18n). Merged over DEFAULT_PLANNING_POKER_PAGE_LABELS (85 English keys); every template in the file accepts it. The rendered DEFAULTS are English — page templates used to hardcode their copy, which no consumer could translate or ship. MCP feedback fb_ba2ec12f.
—playersThe players at the table and the cards they picked, from which the reveal outcome (consensus or spread, outliers, the suggested estimate) is computed; defaults to the demo session.
—estimatedStoriesStories already estimated this session, shown last in the queue rail; defaults to the demo session's estimated stories.
—