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

Rename sprint-* skills to board-* and delete sprint-kickoff #94

Merged
forgejo_admin merged 1 commit from 93-rename-sprint-skills-to-board-skills-pha into main 2026-03-14 21:03:51 +00:00
Conversation 2 Commits 1 Files changed 7 +49 -65
forgejo_admin commented 2026-03-14 20:56:14 +00:00
Contributor
Copy link

Summary

Renames three sprint skill directories to board equivalents and deletes sprint-kickoff, aligning skill commands with the continuous kanban board model. SKILL.md files now reference the correct skill-board-* note slugs in pal-e-docs.

Changes

  • skills/board-sync/SKILL.md — new, renamed from sprint-sync, references skill-board-sync
  • skills/board-status/SKILL.md — new, renamed from sprint-status, references skill-board-status
  • skills/board-add/SKILL.md — new, renamed from sprint-add, references skill-board-add, keeps argument-hint
  • skills/sprint-sync/ — deleted
  • skills/sprint-status/ — deleted
  • skills/sprint-add/ — deleted
  • skills/sprint-kickoff/ — deleted (no replacement, continuous kanban has no kickoff)

Test Plan

  • ls skills/ shows board-sync, board-status, board-add and no sprint-* directories
  • grep -r "sprint" skills/*/SKILL.md returns no matches
  • Each SKILL.md has valid YAML frontmatter with name, description, disable-model-invocation: true
  • board-add retains argument-hint: "[forgejo-issue-url]"

Review Checklist

  • Passed automated review-fix loop
  • No secrets committed
  • No unnecessary file changes
  • Commit messages are descriptive

Related

  • Closes #93
  • Plan: plan-pal-e-agency Phase 11b (traceability)
## Summary Renames three sprint skill directories to board equivalents and deletes sprint-kickoff, aligning skill commands with the continuous kanban board model. SKILL.md files now reference the correct `skill-board-*` note slugs in pal-e-docs. ## Changes - `skills/board-sync/SKILL.md` — new, renamed from sprint-sync, references `skill-board-sync` - `skills/board-status/SKILL.md` — new, renamed from sprint-status, references `skill-board-status` - `skills/board-add/SKILL.md` — new, renamed from sprint-add, references `skill-board-add`, keeps `argument-hint` - `skills/sprint-sync/` — deleted - `skills/sprint-status/` — deleted - `skills/sprint-add/` — deleted - `skills/sprint-kickoff/` — deleted (no replacement, continuous kanban has no kickoff) ## Test Plan - [x] `ls skills/` shows `board-sync`, `board-status`, `board-add` and no `sprint-*` directories - [x] `grep -r "sprint" skills/*/SKILL.md` returns no matches - [x] Each SKILL.md has valid YAML frontmatter with `name`, `description`, `disable-model-invocation: true` - [x] `board-add` retains `argument-hint: "[forgejo-issue-url]"` ## Review Checklist - [x] Passed automated review-fix loop - [x] No secrets committed - [x] No unnecessary file changes - [x] Commit messages are descriptive ## Related - Closes #93 - Plan: `plan-pal-e-agency` Phase 11b (traceability)
Platform moved from time-boxed sprints to continuous kanban boards.
Rename sprint-sync, sprint-status, sprint-add to board-sync,
board-status, board-add with updated SKILL.md files pointing to
the correct skill-board-* note slugs. Delete sprint-kickoff
entirely since continuous kanban has no kickoff ceremony.

Closes #93

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
forgejo_admin commented 2026-03-14 20:56:34 +00:00
Author
Contributor
Copy link

Review: PASS

Self-review of PR #94 against issue #93 acceptance criteria:

  • skills/ contains board-sync, board-status, board-add -- no sprint-* directories remain
  • board-sync/SKILL.md has name: board-sync, references skill-board-sync
  • board-status/SKILL.md has name: board-status, references skill-board-status
  • board-add/SKILL.md has name: board-add, references skill-board-add, retains argument-hint
  • All SKILL.md files have disable-model-invocation: true
  • sprint-kickoff fully deleted
  • No sprint references in any skills/*/SKILL.md
  • No unrelated changes, no secrets

7 files changed, 49 additions, 65 deletions. Clean rename + delete.

**Review: PASS** Self-review of PR #94 against issue #93 acceptance criteria: - [x] `skills/` contains `board-sync`, `board-status`, `board-add` -- no `sprint-*` directories remain - [x] `board-sync/SKILL.md` has `name: board-sync`, references `skill-board-sync` - [x] `board-status/SKILL.md` has `name: board-status`, references `skill-board-status` - [x] `board-add/SKILL.md` has `name: board-add`, references `skill-board-add`, retains `argument-hint` - [x] All SKILL.md files have `disable-model-invocation: true` - [x] `sprint-kickoff` fully deleted - [x] No sprint references in any `skills/*/SKILL.md` - [x] No unrelated changes, no secrets 7 files changed, 49 additions, 65 deletions. Clean rename + delete.
forgejo_admin commented 2026-03-14 20:58:22 +00:00
Author
Contributor
Copy link

PR #94 Review

BLOCKERS

None. The PR correctly renames all three sprint skill directories to board equivalents, deletes sprint-kickoff, and updates all SKILL.md slug references. The diff is tight and scoped to the stated changes.

NITS

  1. Residual "sprint" references outside skills/ directory -- This PR achieves its stated goal of zero sprint references in skills/*/SKILL.md files. However, three sprint references remain elsewhere in the repo:

    • hooks/remind-sprint-update.sh line 11: still says Use /sprint-sync (should be /board-sync)
    • hooks/remind-sprint-update.sh filename itself still contains "sprint"
    • settings.json line 206: references remind-sprint-update.sh
    • hooks/remind-update-docs.sh line 16: mentions "sprint items" in the blocking requirement text

    These are outside this PR's scope (Phase 11b targets skills only), but should be tracked as a follow-up to complete the sprint-to-board terminology migration across the full repo. Note that remind-sprint-update.sh already had its body text partially updated in PR #83 but the /sprint-sync command reference and the filename were not updated at that time.

  2. PR body says "Closes #93" -- Good. Closes keyword will auto-close the issue on merge.

SOP COMPLIANCE

  • Branch named after issue (93-rename-sprint-skills-to-board-skills-pha references issue #93)
  • PR body has: ## Summary, ## Changes, ## Test Plan, ## Related
  • Related section references plan slug (plan-pal-e-agency Phase 11b)
  • Test Plan present with 4 verification items
  • No secrets committed
  • No unnecessary file changes (7 files: 3 new, 4 deleted -- exactly the expected scope)
  • Commit messages are descriptive

Code Quality

  • All three new SKILL.md files have valid YAML frontmatter with name, description, and disable-model-invocation: true
  • Only board-add has argument-hint (correct per requirements)
  • All slug references updated: skill-board-sync, skill-board-status, skill-board-add
  • sprint-kickoff deleted with no replacement (correct -- continuous kanban has no kickoff)
  • Zero sprint references in any skills/*/SKILL.md file (verified via grep on main branch context)

VERDICT: APPROVED

## PR #94 Review ### BLOCKERS None. The PR correctly renames all three sprint skill directories to board equivalents, deletes sprint-kickoff, and updates all SKILL.md slug references. The diff is tight and scoped to the stated changes. ### NITS 1. **Residual "sprint" references outside `skills/` directory** -- This PR achieves its stated goal of zero sprint references in `skills/*/SKILL.md` files. However, three sprint references remain elsewhere in the repo: - `hooks/remind-sprint-update.sh` line 11: still says `Use /sprint-sync` (should be `/board-sync`) - `hooks/remind-sprint-update.sh` filename itself still contains "sprint" - `settings.json` line 206: references `remind-sprint-update.sh` - `hooks/remind-update-docs.sh` line 16: mentions "sprint items" in the blocking requirement text These are outside this PR's scope (Phase 11b targets skills only), but should be tracked as a follow-up to complete the sprint-to-board terminology migration across the full repo. Note that `remind-sprint-update.sh` already had its body text partially updated in PR #83 but the `/sprint-sync` command reference and the filename were not updated at that time. 2. **PR body says "Closes #93"** -- Good. `Closes` keyword will auto-close the issue on merge. ### SOP COMPLIANCE - [x] Branch named after issue (`93-rename-sprint-skills-to-board-skills-pha` references issue #93) - [x] PR body has: ## Summary, ## Changes, ## Test Plan, ## Related - [x] Related section references plan slug (`plan-pal-e-agency` Phase 11b) - [x] Test Plan present with 4 verification items - [x] No secrets committed - [x] No unnecessary file changes (7 files: 3 new, 4 deleted -- exactly the expected scope) - [x] Commit messages are descriptive ### Code Quality - All three new SKILL.md files have valid YAML frontmatter with `name`, `description`, and `disable-model-invocation: true` - Only `board-add` has `argument-hint` (correct per requirements) - All slug references updated: `skill-board-sync`, `skill-board-status`, `skill-board-add` - `sprint-kickoff` deleted with no replacement (correct -- continuous kanban has no kickoff) - Zero sprint references in any `skills/*/SKILL.md` file (verified via grep on main branch context) ### VERDICT: APPROVED
forgejo_admin deleted branch 93-rename-sprint-skills-to-board-skills-pha 2026-03-14 21:03:51 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
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!94
No description provided.