pal-e-docs

Phase 19: User Stories on Project Pages

phase-pal-e-agency-19-user-stories Phase

active phase
Project
Goal: Every project page has a User Stories section (template position #2) organized by role hierarchy from glossary. The superuser has a story in every project. Domain roles are project-specific. A stranger can read any project page and understand who uses the system and what they need.
Owner: Betty Sue (docs work, no code)
Repo: n/a (pal-e-docs notes only)
Depends on: Phase 18 (glossary defines Role Hierarchy, User Story format)

Scope

19a: pal-e-agency — internal roles: Superuser (Lucas), PM (Betty Sue), Dev agent, QA agent, Dottie. What each needs from the process system.
19b: pal-e-platform — Superuser infra stories: deploy, observe, recover, scale. What drives observability dashboard priorities.
19c: pal-e-docs — Superuser, Reader, Contributor. What each needs from the knowledge platform.
19d: mcd-tracker — Superuser, User (Lucas). Small app, stories drive what gets built.
19e: Westside Basketball — already has user stories. Verify superuser story is explicit and story:X keys align with board labels. Minor refinement only.

Deliverables

# Project Page Stories Status
19a <code>project-pal-e-agency</code> 6 (Superuser x2, PM, Dev, QA, Dottie) DONE
19b <code>project-pal-e-platform</code> 4 (Superuser: deploy, observe, recover, onboard) DONE
19c <code>project-pal-e-docs</code> 5 (Superuser x2, Agent x2, Reader) DONE
19d <code>project-mcd-tracker</code> 4 (Superuser, User x3) DONE
19e <code>project-westside-basketball</code> 25 (Superadmin x4, Admin x8, Coach x4, Parent x6, Player x3) — fixed positioning, added WS-S1 to WS-S25 keys DONE
  • glossary — Role Hierarchy and User Story definitions
  • template-project-page — User Stories at position #2
  • template-ticket — traceability triangle (story:X labels)
  • phase-pal-e-agency-18-enterprise-definitions — prerequisite
  • plan-pal-e-agency — parent plan