If you're tired of your design team constantly asking "what's the process for this?" you need a documented workflow. This gives you a framework for the full cycle: task management with boards and priorities, collaboration rituals like critiques and standups, communication norms so people know when to ping Slack versus write a doc, and the tooling stack to tie it together. The design-to-dev handoff section alone is worth it, covering when designers join sprints and how to QA implementation. It's structured around six stages from discovery through iteration. Best part is it emphasizes adapting to your actual team rather than copying some ideal process from a blog post.
npx skills add https://github.com/owl-listener/designer-skills --skill team-workflow