ldraney/claude-custom
1
0
Fork 0
Code Issues 32 Pull requests Projects Releases Packages Wiki Activity Actions

Task: Update 11 SOPs/conventions/templates for kanban-over-plans #169

New issue
Open
opened 2026-03-26 17:25:11 +00:00 by forgejo_admin · 7 comments
forgejo_admin commented 2026-03-26 17:25:11 +00:00
Contributor
Copy link

Type

Feature

Lineage

standalone — discovered during plan deprecation audit 2026-03-26.
NOTE: This is actually a Task (non-code work). Filed as Feature to pass hook validation until claude-custom#167 ships Task type routing.

Repo

forgejo_admin/claude-custom (tracking repo — actual work is pal-e-docs MCP updates)

User Story

As Betty Sue (PM),
I want all SOPs, conventions, and templates to reflect the kanban-over-plans convention,
So that agents and humans see a single consistent model without plan/phase artifacts.

Context

convention-kanban-over-plans (2026-03-24) declared plans deprecated but 11 notes still reference plans/phases. This creates confusion — agents read agent-workflow and see plan→phase→issue as Path 1, then read the convention and see "plans are dead." The docs must be consistent.

File Targets

No code files. All work is pal-e-docs note updates via MCP tools:

  1. template-plan — mark status: deprecated
  2. template-phase — mark status: deprecated
  3. template-ticket — third leg = Forgejo issue, not phase
  4. template-issue-feature — update Lineage section
  5. template-issue-bug — update Lineage section
  6. template-issue-spike — update Lineage section
  7. agent-workflow — remove Path 1, simplify to board-driven
  8. agent-spawn-conventions — remove plan slug requirement
  9. convention-todo-lifecycle — remove plan path from decision gate
  10. sop-board-workflow — remove phase item_type docs
  11. glossary — update scoping pipeline

Acceptance Criteria

  • template-plan and template-phase status = deprecated
  • template-ticket traceability triangle references Forgejo issue, not phase
  • All 3 issue templates have updated Lineage sections
  • agent-workflow has single board-driven path
  • agent-spawn-conventions no longer requires plan slug
  • All 11 notes verified via get_note_toc

Test Expectations

  • Read each updated note and verify no plan/phase references remain in active guidance
  • Verify deprecated templates are tagged appropriately

Constraints

  • Use get_section + update_block for surgical edits — no full note rewrites
  • Don't modify completed/historical phase notes (they're archival)

Checklist

  • All 11 notes updated
  • No unrelated changes

Related

  • project-pal-e-agency — project
  • story:pm-scope — user story
  • arch:kanban — architecture component
  • convention-kanban-over-plans — the convention these updates implement
### Type Feature ### Lineage standalone — discovered during plan deprecation audit 2026-03-26. NOTE: This is actually a Task (non-code work). Filed as Feature to pass hook validation until claude-custom#167 ships Task type routing. ### Repo `forgejo_admin/claude-custom` (tracking repo — actual work is pal-e-docs MCP updates) ### User Story As Betty Sue (PM), I want all SOPs, conventions, and templates to reflect the kanban-over-plans convention, So that agents and humans see a single consistent model without plan/phase artifacts. ### Context `convention-kanban-over-plans` (2026-03-24) declared plans deprecated but 11 notes still reference plans/phases. This creates confusion — agents read `agent-workflow` and see plan→phase→issue as Path 1, then read the convention and see "plans are dead." The docs must be consistent. ### File Targets No code files. All work is pal-e-docs note updates via MCP tools: 1. `template-plan` — mark status: deprecated 2. `template-phase` — mark status: deprecated 3. `template-ticket` — third leg = Forgejo issue, not phase 4. `template-issue-feature` — update Lineage section 5. `template-issue-bug` — update Lineage section 6. `template-issue-spike` — update Lineage section 7. `agent-workflow` — remove Path 1, simplify to board-driven 8. `agent-spawn-conventions` — remove plan slug requirement 9. `convention-todo-lifecycle` — remove plan path from decision gate 10. `sop-board-workflow` — remove phase item_type docs 11. `glossary` — update scoping pipeline ### Acceptance Criteria - [ ] template-plan and template-phase status = deprecated - [ ] template-ticket traceability triangle references Forgejo issue, not phase - [ ] All 3 issue templates have updated Lineage sections - [ ] agent-workflow has single board-driven path - [ ] agent-spawn-conventions no longer requires plan slug - [ ] All 11 notes verified via get_note_toc ### Test Expectations - Read each updated note and verify no plan/phase references remain in active guidance - Verify deprecated templates are tagged appropriately ### Constraints - Use `get_section` + `update_block` for surgical edits — no full note rewrites - Don't modify completed/historical phase notes (they're archival) ### Checklist - [ ] All 11 notes updated - [ ] No unrelated changes ### Related - `project-pal-e-agency` — project - `story:pm-scope` — user story - `arch:kanban` — architecture component - `convention-kanban-over-plans` — the convention these updates implement
forgejo_admin commented 2026-03-26 17:29:06 +00:00
Author
Contributor
Copy link

Scope Addition: skill-review-ticket update

Discovered during audit: skill-review-ticket has 5 gaps against the kanban-over-plans paradigm:

  1. Stale template reference — reads generic template-issue instead of type-specific templates (Feature/Bug/Spike/Task)
  2. No traceability triangle validation — doesn't verify story:/arch: labels against project page
  3. Plan context still referenced — inputs mention "phase note slug for plan-driven items"
  4. No Task type awareness — assumes all items have file targets or phase notes
  5. Review format missing traceability section — no check that labels map to real user stories/arch components

Additional Note to Update

  1. skill-review-ticket — update to route to type-specific templates, add traceability validation, remove plan/phase references, handle Task type, add Traceability section to review format

Updated Acceptance Criteria (appended)

  • skill-review-ticket routes to type-specific template based on ### Type header
  • skill-review-ticket includes traceability triangle validation step
  • skill-review-ticket references project page (not plan) as context
  • skill-review-ticket handles Task-type issues (Scope section, no file targets)
  • Review note format includes Traceability section
## Scope Addition: skill-review-ticket update Discovered during audit: `skill-review-ticket` has 5 gaps against the kanban-over-plans paradigm: 1. **Stale template reference** — reads generic `template-issue` instead of type-specific templates (Feature/Bug/Spike/Task) 2. **No traceability triangle validation** — doesn't verify story:/arch: labels against project page 3. **Plan context still referenced** — inputs mention "phase note slug for plan-driven items" 4. **No Task type awareness** — assumes all items have file targets or phase notes 5. **Review format missing traceability section** — no check that labels map to real user stories/arch components ### Additional Note to Update 12. `skill-review-ticket` — update to route to type-specific templates, add traceability validation, remove plan/phase references, handle Task type, add Traceability section to review format ### Updated Acceptance Criteria (appended) - [ ] skill-review-ticket routes to type-specific template based on ### Type header - [ ] skill-review-ticket includes traceability triangle validation step - [ ] skill-review-ticket references project page (not plan) as context - [ ] skill-review-ticket handles Task-type issues (Scope section, no file targets) - [ ] Review note format includes Traceability section
forgejo_admin commented 2026-03-26 17:29:18 +00:00
Author
Contributor
Copy link

Scope Review: NEEDS_REFINEMENT

Review note: review-397-2026-03-26

Well-scoped ticket with all template sections present, but blast radius check found a 12th note missing from scope.

  • template-issue (the parent issue template) still contains ### Plan (not ### Lineage), traceability chain Project → Plan → Phase → Subphase → Forgejo Issue → PR, plan-based Lineage Examples, and "How Betty Sue Tracks Issues" referencing plan phases. All 3 child templates (feature/bug/spike) descend from this — updating children but not the parent leaves the most prominent plan references in place.
  • Acceptance criteria verification method is weak: "verified via get_note_toc" only checks headings exist, not that content was changed. Should use get_section to verify plan/phase references were actually removed from section content.
## Scope Review: NEEDS_REFINEMENT Review note: `review-397-2026-03-26` Well-scoped ticket with all template sections present, but blast radius check found a 12th note missing from scope. - **`template-issue`** (the parent issue template) still contains `### Plan` (not `### Lineage`), traceability chain `Project → Plan → Phase → Subphase → Forgejo Issue → PR`, plan-based Lineage Examples, and "How Betty Sue Tracks Issues" referencing plan phases. All 3 child templates (feature/bug/spike) descend from this — updating children but not the parent leaves the most prominent plan references in place. - **Acceptance criteria verification method is weak**: "verified via get_note_toc" only checks headings exist, not that content was changed. Should use `get_section` to verify plan/phase references were actually removed from section content.
forgejo_admin commented 2026-03-26 17:29:43 +00:00
Author
Contributor
Copy link

Refinement: missed parent template + verification fix

Per review review-397-2026-03-26:

Additional Note to Update

  1. template-issue — the parent template still contains ### Plan (not ### Lineage), plan-based traceability chain Project → Plan → Phase → Subphase → Forgejo Issue → PR, Lineage Examples table, and "How Betty Sue Tracks Issues" referencing plan phases. Must be updated alongside the 3 child templates.

Verification Criterion Fix

Change "All notes verified via get_note_toc" to "All notes verified via get_section to confirm plan/phase content actually removed from each updated section."

Updated Total

13 notes (11 original + skill-review-ticket + template-issue)

## Refinement: missed parent template + verification fix Per review `review-397-2026-03-26`: ### Additional Note to Update 13. `template-issue` — the parent template still contains `### Plan` (not `### Lineage`), plan-based traceability chain `Project → Plan → Phase → Subphase → Forgejo Issue → PR`, Lineage Examples table, and "How Betty Sue Tracks Issues" referencing plan phases. Must be updated alongside the 3 child templates. ### Verification Criterion Fix Change "All notes verified via `get_note_toc`" to "All notes verified via `get_section` to confirm plan/phase content actually removed from each updated section." ### Updated Total 13 notes (11 original + skill-review-ticket + template-issue)
forgejo_admin commented 2026-03-26 22:22:19 +00:00
Author
Contributor
Copy link

Scope Re-Review: NEEDS_REFINEMENT

Review note: review-397-2026-03-26-v2

Prior review issues (template-issue parent + weak verification) are both resolved in Comment 3.

Fresh blast radius check found one more active template missing from scope:

  • template-pr-body — Related Notes section contains plan-slug — the plan phase this implements. Active template used by agents on every PR. Must be updated to reference Forgejo issue URLs instead of plan slugs.

Action needed: Add template-pr-body as note #14. Total becomes 14 notes.

## Scope Re-Review: NEEDS_REFINEMENT Review note: `review-397-2026-03-26-v2` Prior review issues (template-issue parent + weak verification) are both resolved in Comment 3. Fresh blast radius check found one more active template missing from scope: - **`template-pr-body`** — Related Notes section contains `plan-slug — the plan phase this implements`. Active template used by agents on every PR. Must be updated to reference Forgejo issue URLs instead of plan slugs. **Action needed:** Add `template-pr-body` as note #14. Total becomes 14 notes.
forgejo_admin commented 2026-03-26 22:22:36 +00:00
Author
Contributor
Copy link

Refinement v4: missed template-pr-body

Per review review-397-2026-03-26-v2:

Additional Note to Update

  1. template-pr-body — active template used by agents on every PR. Related Notes section says "plan-slug — the plan phase this implements." Must be updated to reference board item / Forgejo issue instead of plan phase.

Updated Total

14 notes (11 original + skill-review-ticket + template-issue + template-pr-body)

## Refinement v4: missed template-pr-body Per review `review-397-2026-03-26-v2`: ### Additional Note to Update 14. `template-pr-body` — active template used by agents on every PR. Related Notes section says "plan-slug — the plan phase this implements." Must be updated to reference board item / Forgejo issue instead of plan phase. ### Updated Total 14 notes (11 original + skill-review-ticket + template-issue + template-pr-body)
forgejo_admin commented 2026-03-26 22:27:05 +00:00
Author
Contributor
Copy link

Scope Review v3: READY

Review note: review-397-2026-03-26-v3

All 14 notes verified via get_section — plan/phase references confirmed in every target. Template completeness: all 11 required sections present. No blocking dependencies. Acceptance criteria are agent-verifiable using get_section (not just get_note_toc).

Blast radius (discovered scope, separate ticket): 4 plan-creation infrastructure notes (note-conventions, sop-index, skill-plan, convention-subphase) still reference plans as active. These describe system state/infrastructure, not workflow guidance — separate scope from this ticket's focus on the 14 docs agents actively read.

## Scope Review v3: READY Review note: `review-397-2026-03-26-v3` All 14 notes verified via `get_section` — plan/phase references confirmed in every target. Template completeness: all 11 required sections present. No blocking dependencies. Acceptance criteria are agent-verifiable using `get_section` (not just `get_note_toc`). **Blast radius (discovered scope, separate ticket):** 4 plan-creation infrastructure notes (`note-conventions`, `sop-index`, `skill-plan`, `convention-subphase`) still reference plans as active. These describe system state/infrastructure, not workflow guidance — separate scope from this ticket's focus on the 14 docs agents actively read.
forgejo_admin commented 2026-03-27 00:18:55 +00:00
Author
Contributor
Copy link

Dottie: All 14 notes updated and verified

Summary of changes

# Note Change Verified
1 template-plan status: deprecated, tags: template,deprecated, deprecation banner added Yes
2 template-phase status: deprecated, tags: template,deprecated, deprecation banner added Yes
3 template-ticket Traceability triangle: Phase → Forgejo Issue. "What a Ticket Is" table: removed phase item_type, note_slug, points fields. Example updated from phase to issue item_type. Yes
4 template-issue-feature Lineage: plan-slug → Phase N replaced with Standalone or Related to org/repo #N Yes
5 template-issue-bug Lineage: removed plan/phase references, now standalone or related-issue format Yes
6 template-issue-spike Lineage: removed plan/phase references, now standalone or related-issue format Yes
7 agent-workflow "Two Work Paths" → "Work Path: Board-Driven". Single flow: Forgejo issue → board → agent → PR → QA → done. Added Task to issue types. Yes
8 agent-spawn-conventions Single board-driven path. Removed plan slug from Required table and Pre-Spawn Checklist. Unified prompt pattern. Yes
9 convention-todo-lifecycle Added Task type to decision tree. Lifecycle table: removed plan path (3a), unified to single board entry (3). Yes
10 sop-board-workflow Removed plan and phase item_types from "How items arrive" table. Yes
11 glossary Scoping Pipeline: Project → Plan → Phase → ... replaced with Discovery → Typed Forgejo Issue → Board → .... Removed two-path model, replaced with four issue types. Yes
12 skill-review-ticket Inputs: removed plan context. Steps: added type routing (Step 2), traceability triangle validation (Step 4), Task handling. Review format: added Traceability section. Yes
13 template-issue ### Plan → ### Lineage. Added ### Type with all four types. Tracking section: removed plan phase references. Yes
14 template-pr-body Related Notes: plan-slug — the plan phase this implements replaced with org/repo #N — the Forgejo issue this PR implements Yes

All updates used surgical get_section + update_block pattern. No full note rewrites. Historical content in deprecated templates preserved as archival artifacts.

## Dottie: All 14 notes updated and verified ### Summary of changes | # | Note | Change | Verified | |---|------|--------|----------| | 1 | `template-plan` | status: deprecated, tags: template,deprecated, deprecation banner added | Yes | | 2 | `template-phase` | status: deprecated, tags: template,deprecated, deprecation banner added | Yes | | 3 | `template-ticket` | Traceability triangle: Phase → Forgejo Issue. "What a Ticket Is" table: removed `phase` item_type, `note_slug`, `points` fields. Example updated from phase to issue item_type. | Yes | | 4 | `template-issue-feature` | Lineage: `plan-slug → Phase N` replaced with `Standalone` or `Related to org/repo #N` | Yes | | 5 | `template-issue-bug` | Lineage: removed plan/phase references, now standalone or related-issue format | Yes | | 6 | `template-issue-spike` | Lineage: removed plan/phase references, now standalone or related-issue format | Yes | | 7 | `agent-workflow` | "Two Work Paths" → "Work Path: Board-Driven". Single flow: `Forgejo issue → board → agent → PR → QA → done`. Added Task to issue types. | Yes | | 8 | `agent-spawn-conventions` | Single board-driven path. Removed plan slug from Required table and Pre-Spawn Checklist. Unified prompt pattern. | Yes | | 9 | `convention-todo-lifecycle` | Added Task type to decision tree. Lifecycle table: removed plan path (3a), unified to single board entry (3). | Yes | | 10 | `sop-board-workflow` | Removed `plan` and `phase` item_types from "How items arrive" table. | Yes | | 11 | `glossary` | Scoping Pipeline: `Project → Plan → Phase → ...` replaced with `Discovery → Typed Forgejo Issue → Board → ...`. Removed two-path model, replaced with four issue types. | Yes | | 12 | `skill-review-ticket` | Inputs: removed plan context. Steps: added type routing (Step 2), traceability triangle validation (Step 4), Task handling. Review format: added Traceability section. | Yes | | 13 | `template-issue` | `### Plan` → `### Lineage`. Added `### Type` with all four types. Tracking section: removed plan phase references. | Yes | | 14 | `template-pr-body` | Related Notes: `plan-slug — the plan phase this implements` replaced with `org/repo #N — the Forgejo issue this PR implements` | Yes | All updates used surgical `get_section` + `update_block` pattern. No full note rewrites. Historical content in deprecated templates preserved as archival artifacts.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
217-enhance-skill-review-ticket-verify-arch
86-epilogue-nits-hook-updates-dottie-config
76-add-sessionstart-hook-to-detect-missing
69-fix-block-docs-writes-sh-security-gap-ad
51-phase-3-agent-label-behavior-posttooluse
No results found.
Labels
Clear labels   
domain:backend

   
domain:devops

   
domain:frontend

   
status:approved

QA passed, awaiting merge approval

  
status:in-progress

Dev agent is actively working

  
status:needs-fix

QA found issues, back to dev

  
status:qa

PR submitted, awaiting QA review

  
type:bug

Bug fix

  
type:devops

Infrastructure/CI/config work

  
type:feature

New functionality

No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ldraney/claude-custom#169
No description provided.