Plan: pal-e-sprints Backend

plan-2026-03-01-pal-e-sprints Plan

plan completed

Project

Vision

Five-board sprint system in pal-e-docs. Plans, phases, issues, repos, and projects each get their own board with seven columns (Backlog, TODO, Next Up, In Progress, QA, Needs Approval, Done). Betty Sue manages sprints via MCP. Built on pal-e-docs' existing note decomposition — plans contain phases, phases generate issues.

The Five Boards

Board	Tracks	Source
Projects	Which projects are active this sprint	pal-e-docs notes (note_type=project-page)
Plans	Which plans are committed to this sprint	pal-e-docs notes (note_type=plan)
Phases	Which phases are moving this sprint	pal-e-docs notes (note_type=phase, children of committed plans)
Items (Issues)	Which Forgejo issues are committed	Forgejo issue URLs across repos
Repos	Which repos have active work	Repo references

Same table, same columns, filtered by item_type. The sprint board is the commitment layer — it says "these items are in this sprint, in this column."

Projects & Repos Touched

Project/Repo	Platform	Role
<code>forgejo_admin/pal-e-docs</code>	Forgejo	Sprint tables, API endpoints
<code>forgejo_admin/pal-e-docs-mcp</code>	Forgejo	MCP tools for sprint management

Phases

See child phase notes: list_notes(parent_slug="plan-2026-03-01-pal-e-sprints")

Summary:

Phase 1: Tables, API, MCP Tools — COMPLETED. PR #65 merged (pal-e-docs), PR #9 merged + deployed (pal-e-docs-mcp). 25 MCP tools live.
Schema Expansion — COMPLETED. PR #67 (repo/project + needs_approval), PR #69 (points field), PR #32 (MCP tools update) all merged. QA nits tracked as pal-e-docs-mcp #33 and #34.
Phase 2: Auto-Population and Sync — NOT STARTED. API-side auto-sync of sprint items.
Phase 3: Token Metrics — NOT STARTED. Per-sprint token tracking.

Decisions Made

Decision	Rationale
Five boards (projects, plans, phases, items, repos)	Expanded from three after Sprint 1 creation showed the need for project and repo tracking.
Seven columns (added needs_approval)	Gate between QA approval and Lucas's merge approval. Maps to status:approved label.
Single SprintItem table, polymorphic item_type	Same columns, same API, filtered by type. Simple.
note_slug for plans/phases, forgejo_issue_url for issues	Plans and phases already live in pal-e-docs. Issues live in Forgejo.
Backend-first, no frontend	Betty Sue manages via MCP. Frontend deferred.
Sprint data lives in pal-e-docs DB	Zero sync overhead. Isolated tables.