Board: Scope Review Pipeline (Jidoka)
Board: Scope Review Pipeline (Jidoka)
Decomposition of claude-custom#161 — too large for single agent pass (6+ file targets across 2 systems, 7 AC, 3 distinct concerns).
Parent
Board item #364 on board-pal-e-agency. Forgejo issue:
forgejo_admin/claude-custom#161. Original ticket covers enforcement hook + skill enhancement + documentation — three independent concerns that can be parallelized.User Stories
| Role | Key | Story | Success Metric |
|---|---|---|---|
| Betty Sue (PM) | scope-review | I want tickets to be automatically reviewed before advancing from todo to next_up | No ticket advances without a READY verdict from /review-ticket |
Architecture
Components from
project-pal-e-agency architecture:arch:hooks— PreToolUse hook onupdate_board_itemthat gates todo→next_up transitionsarch:board-api— board item column changes that trigger the hookarch:enforcement— the broader enforcement layer this hook joins
Acceptance Criteria
The parent ticket (#161) is done when:
- Moving a board item from todo→next_up triggers a review check
- The /review-ticket skill and skill-review-ticket note include the decomposition check
- Conventions and SOPs document the review gate
Kanban
Three sub-tickets, all independent and parallel-dispatchable:
- Hook: check-board-advance.sh — PreToolUse hook on
update_board_item. Fires only on todo→next_up. Checks for review note. Must NOT fire during sync_board. Target:claude-customrepo. ~3 min agent work. - Skill: update /review-ticket router — Update SKILL.md router to handle the new decomposition path. Target:
claude-customrepo. ~2 min agent work. - Docs: convention + SOP updates — Update
sop-board-workflowto document the review gate. Route to Dottie. ~2 min agent work.
Dependency: Board item #365 (
claude-custom#162, Forgejo MCP update_issue tool) blocks sub-ticket #1's ability to programmatically update issue bodies. Sub-tickets #2 and #3 are unblocked.