Review: Update 11 SOPs/conventions for kanban-over-plans

Verdict: NEEDS_REFINEMENT

Template Completeness

• [x] Type
• [x] Lineage
• [x] Repo
• [x] User Story
• [x] Context
• [x] File Targets
• [x] Acceptance Criteria
• [x] Test Expectations
• [x] Constraints
• [x] Checklist
• [x] Related

File Targets

• [x] template-plan — verified exists, has active status needing deprecation
• [x] template-phase — verified exists, has active status needing deprecation
• [x] template-ticket — verified exists, traceability triangle shows "Phase (note_slug)" as third leg
• [x] template-issue-feature — verified exists, Lineage section contains plan-slug-here reference
• [x] template-issue-bug — verified exists, Lineage section contains plan-slug-here reference
• [x] template-issue-spike — verified exists, Lineage section contains plan-slug-here reference
• [x] agent-workflow — verified exists, "Two Work Paths" section has Path 1 (plan-driven) needing removal
• [x] agent-spawn-conventions — verified exists, "Two Work Paths" table and "Pre-Spawn Checklist" reference plan slugs
• [x] convention-todo-lifecycle — verified exists, "Lifecycle" table has "3a. Plan path" row
• [x] sop-board-workflow — verified exists, "Item Lifecycle" table has plan and phase item_type rows
• [x] glossary — verified exists, "Scoping Pipeline" section shows Project → Plan → Phase → Forgejo Issue chain
• [ ] template-issue — MISSING FROM SCOPE: the parent issue template still has ### Plan (not ### Lineage), traceability chain Project → Plan → Phase → Subphase → Forgejo Issue → PR, plan-based Lineage Examples table, and "How Betty Sue Tracks Issues" referencing plan phases. This is a 12th note that needs updating.

Repo Placement

Dependencies

• Board #396 (claude-custom#168 — "Remove plan/phase hooks from enforcement layer") — sibling task from same audit. Code changes to hooks. No blocking dependency; can run in parallel with this doc-only ticket.
• Board #395 (claude-custom#167 — "Upgrade story: label to hard-block + Task type routing") — mentioned in issue body as prerequisite for Task type, but does not block the documentation updates.
• Board #98 (Phase: Context intelligence) — currently in_progress. No dependency.
• No undocumented blockers found.

Acceptance Criteria

• [x] Criteria are specific and enumerable (11 notes, each with a clear change)
• [ ] ISSUE: "All 11 notes verified via get_note_toc" is insufficient. TOC only shows headings, not content. Should specify get_section or get_note to verify content within sections was actually changed. Suggest: "Read updated sections via get_section to verify no plan/phase references remain in active guidance."
• [x] Deprecation criteria are clear (template-plan and template-phase status = deprecated)

Blast Radius

• template-issue (slug: template-issue) is not in scope but contains stale plan references. This is the parent issue template that all 3 typed templates (feature/bug/spike) descend from. It still has:
• No other notes outside the 11 targets were found with active plan/phase guidance.

Recommendation

• Add template-issue as target #12. It is the parent template and contains the most prominent plan references (### Plan section, traceability chain, Lineage Examples). Without this, the child templates will be updated but the parent they reference will still say "plans."
• Strengthen acceptance criterion for verification. Change "verified via get_note_toc" to "verified via get_section — no plan/phase references remain in active guidance sections." TOC cannot verify content changes.