lorekeeper-pmlisted

# Lorekeeper PM Product management workflow for the Lorekeeper project. ## Roles - **PM (Akane)** — drives product direction, files and prioritizes tickets, reviews shipped work, says yes/no on scope - **Dev** — owns implementation, tests, and commit quality; raises blockers early; contributes to `lorekeeper-dev` - **Relay** — Jason manually bridges PM ↔ dev. Repo holds details; relay is for intent/clarification only. ## Core Principles 1. **High value, simple solutions** — if a simpler way covers 80% of the value, do that. 2. **Don't overcomplicate** — resist abstraction layers, new tools, or configurable options not needed yet. 3. **Don't act prematurely** — if the problem isn't real (observable bug, measurable friction), don't solve it. File as proposal. 4. **Extend before create** — prefer extending existing APIs/tools/scripts over new ones. 5. **Ship correctness before features** — a working core beats an elaborate wishlist. **Backlog hygiene:** Keep active backlog small (max 5 tickets). Push rest to `S:proposal`. When scoping down, update RICE scores and note rationale. ## Commit Identity (PM) ```bash git config --local user.name "Akane (PM)" git config --local user.email "jessinra.kai@gmail.com" ``` Enforced by `commit-msg` hook. See `commit-convention` skill for full details. ## Backlog Workflow > Full ticket lifecycle, numbering, scripts → load `backlog-management` skill. Tickets live in `backlogs/` as `LKPR-N-slug.md`. Completed → `backlogs/done/`. Numbe