personal-projects/leo-claude-mktplace
Template
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(projman): add new command verification step to sprint-close #279

Merged
lmiranda merged 1 commits from fix/sprint-close-new-command-verification into development 2026-01-28 20:37:24 +00:00
Conversation 0 Commits 1 Files Changed 1 +19 -10
lmiranda commented 2026-01-28 20:36:30 +00:00
Owner
Copy Link

Summary

Addresses issue #278 - sprint-diagram command not discoverable after Sprint 4.

Problem

Claude Code discovers skills at session start. Commands added during a session are NOT discoverable until restart. Sprint 4 added /sprint-diagram but it wasn't testable in the same session.

Solution

Added step 7 "New Command Verification" to sprint-close workflow:

  • Checks if sprint added new commands
  • Reminds user that new commands require session restart to test
  • Creates follow-up verification task

Changes

  • plugins/projman/commands/sprint-close.md: Added verification step, renumbered subsequent steps

Lesson Learned

Created: lessons/patterns/sprint-4---new-commands-not-discoverable-until-session-restart

Test Plan

  • Review sprint-close.md changes
  • Verify step numbering is correct (1-11)
  • Confirm lesson learned is accessible in wiki

Closes #278

Generated with Claude Code

## Summary Addresses issue #278 - sprint-diagram command not discoverable after Sprint 4. ## Problem Claude Code discovers skills at session start. Commands added during a session are NOT discoverable until restart. Sprint 4 added `/sprint-diagram` but it wasn't testable in the same session. ## Solution Added step 7 "New Command Verification" to sprint-close workflow: - Checks if sprint added new commands - Reminds user that new commands require session restart to test - Creates follow-up verification task ## Changes - `plugins/projman/commands/sprint-close.md`: Added verification step, renumbered subsequent steps ## Lesson Learned Created: `lessons/patterns/sprint-4---new-commands-not-discoverable-until-session-restart` ## Test Plan - [ ] Review sprint-close.md changes - [ ] Verify step numbering is correct (1-11) - [ ] Confirm lesson learned is accessible in wiki Closes #278 --- Generated with [Claude Code](https://claude.ai/code)
lmiranda added the Type/BugPriority/Medium labels 2026-01-28 20:36:30 +00:00
lmiranda added 1 commit 2026-01-28 20:36:31 +00:00
fix(projman): add new command verification step to sprint-close 611b50b150 
Addresses issue #278 - sprint-diagram command not discoverable after Sprint 4.

Root cause: Claude Code discovers skills at session start. Commands added
during a session are NOT discoverable until restart.

Prevention: Added step 7 "New Command Verification" to sprint-close workflow:
- Reminds about session restart requirement
- Creates follow-up verification task
- Explains why this happens

Lesson learned created: lessons/patterns/sprint-4---new-commands-not-discoverable-until-session-restart

Closes #278

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
lmiranda merged commit 5638891d01 into development 2026-01-28 20:37:24 +00:00
lmiranda deleted branch fix/sprint-close-new-command-verification 2026-01-28 20:37:24 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Component/API
API endpoints, contracts, and integration
 Component/Auth
Authentication and authorization
 Component/Backend
Backend service code and business logic
 Component/Database
Database schemas, migrations, queries
 Component/Deploy
Deployment, infrastructure, DevOps
 Component/Docs
Documentation and guides
 Component/Frontend
User interface and client-side code
 Component/Infra
Infrastructure and system configuration
 Component/Testing
Test infrastructure and frameworks
 Tech/Docker
Docker containers and compose
 Tech/FastAPI
FastAPI backend framework
 Tech/JavaScript
JavaScript/Node.js code
 Tech/PostgreSQL
PostgreSQL database
 Tech/Python
Python language and libraries
 Tech/Redis
Redis cache and pub/sub
 Tech/Vue
Vue.js frontend framework
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label Priority/Medium Type/Bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/leo-claude-mktplace#279
Delete Branch "fix/sprint-close-new-command-verification"

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?