Scrum4Me/docs/glossary.md

title	status	audience	language	last_updated	when_to_read
Scrum4Me — Glossary	active	ai-agent contributor	en	2026-05-03	When you encounter a domain term and need its canonical definition and the doc where it is specified.

Scrum4Me — Glossary

Domain terms used across Scrum4Me docs, code, and MCP tooling.

agent worker

A Claude Code session that has registered itself as a ClaudeWorker record and polls the job queue via mcp__scrum4me__wait_for_job. The NavBar counts active workers by last_seen_at < now() - 15s. See MCP integration runbook.

claude-question

A pending question posted by an agent (via mcp__scrum4me__ask_user_question) to a human user, stored in the claude_questions table. The user answers in the UI; a PostgreSQL LISTEN/NOTIFY trigger pushes the answer back to the waiting agent. See architecture: claude-question-channel and ADR-0007.

demo-token

An API token whose owning user has isDemo = true. All write operations are blocked at three layers: the proxy.ts middleware, individual server actions, and disabled UI buttons. See architecture: auth and sessions and ADR-0006.

demo-user

A preconfigured read-only account used for public showcase. Shares product data with the main account but cannot create, update, or delete anything. See architecture: auth and sessions.

MCP-job

A Task record that has been queued for autonomous agent execution. An agent claims a job atomically via mcp__scrum4me__wait_for_job and reports completion via mcp__scrum4me__update_job_status. See MCP integration runbook.

PBI (Product Backlog Item)

The second level of the work hierarchy: Product → PBI → Story → Task. A PBI groups related stories under a single theme or capability. Do not use "Epic", "Feature", or "Issue" as synonyms. See backlog index.

Solo Panel

The single-user planning screen that shows all PBIs and stories for one product in a split-pane drag-and-drop layout. Contrast with the Sprint board (team-facing). See functional spec — Solo Panel.

Sprint

A time-boxed iteration with a sprint_goal. Stories move from OPEN to IN_SPRINT when added to the active sprint. Only one sprint per product can be ACTIVE at a time. See backlog index.

Story

The third level of the work hierarchy: Product → PBI → Story → Task. A Story has acceptance criteria and a status (OPEN | IN_SPRINT | DONE). See functional spec.

Task

The leaf level of the work hierarchy: Product → PBI → Story → Task. A Task has an implementation_plan, a status (TO_DO | IN_PROGRESS | REVIEW | DONE), and an optional sort_order. API exposes status as lowercase (todo | in_progress | review | done). See architecture: data model and ADR-0004.

Todo

A lightweight freeform note scoped to a product (or unscoped). Not part of the sprint hierarchy — used for quick capture. Created via mcp__scrum4me__create_todo. See MCP integration runbook.