Add kanban-guru skill — virtual Kanban expert #17
No reviewers
Labels
No labels
community-feedback
enhancement
skill-upgrade
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
magnus/agent-skills!17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/kanban-guru-skill"
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?
A new skill providing virtual Kanban expertise for engineering teams. Includes diagnostic QuickScan, design/transition modes, and 7 reference files covering full Kanban knowledge stack.
Code Review: kanban-guru skill (PR #17)
Reviewer: Jasper (automated review)
Overall Assessment
This is a well-crafted, comprehensive skill. The structure is professional, the reference file system is well-organized, and the content demonstrates genuine Kanban expertise. The QuickScan, anti-patterns, and consulting approach sections add practical value beyond basic reference documentation.
Findings
1. Missing glossary entry for Scrumban
references/transition-guide.mdhas a full 'Scrumban Bridge' section with month-by-month sequencing, butreferences/glossary.mddoesn't include 'Scrumban' as a term. Since Scrumban is a distinct methodology referenced across multiple files, it merits its own glossary entry for cross-reference consistency.2. QuickScan interactive vs self-service ambiguity
SKILL.md line 77 says 'Say "I don't know where to start" and I'll run a quick diagnostic.' followed immediately by the written QuickScan questions. This creates ambiguity: is the diagnostic interactive or self-service? Consider clarifying: 'If you'd prefer I walk through these questions interactively, say "I don't know where to start."'
3. No 'When NOT to use' guidance
The skill describes when to load it (flow pain signals, ambient anxiety) but doesn't explicitly describe when NOT to. Common exclusions: teams with no pain points, or users looking for tool-specific configuration advice.
4. No Kanban-in-name-only in glossary
This failure mode is described in transition-guide.md but absent from the glossary.
Positives
Verdict: Approved with suggestions
No blocking issues. The content quality is high and the skill provides genuine practical value. Addressing the glossary gap and QuickScan clarity would be minor polish items for a follow-up.