Drop points enforcement from board items — lean kanban alignment #202
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ldraney/pal-e-api#202
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
Bug
Lineage
Standalone — board-pal-e-agency kanban philosophy
Repo
~/claude-custom(hooks hardlinked to~/.claude/hooks/)What Broke
check-board-item.shrequires Fibonacci points (1, 2, 3, 5, 8) on every board item. This is Scrum estimation theater — it doesn't align with Lean Kanban. Lead time (next_up → done timestamps) is the real metric. Points add ceremony without value.Repro Steps
Expected Behavior
Points should be optional metadata, not enforced. The hook should allow items with or without points. Lead time tracking via timestamps replaces velocity tracking via points.
Environment
~/.claude/hooks/check-board-item.sh— enforces points as required + Fibonacci~/.claude/schemas/agent-spawn-requirements.json— already being updated on branch200-agent-spawn-drop-plan-gateAcceptance Criteria
Related
project-pal-e-agency— kanban philosophy alignment