team-workflow
The team-workflow skill helps design leaders establish structured collaboration systems for their teams, covering task management approaches, recurring rituals like standups and design critiques, communication norms across synchronous and asynchronous channels, and tooling decisions. Use this when onboarding a new design team, scaling an existing team, reducing friction between designers and developers, or auditing whether your current workflows serve your team's actual needs rather than following generic best practices.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/team-workflow && cp -r /tmp/team-workflow/design-ops/skills/team-workflow ~/.claude/skills/team-workflowSKILL.md
# Team Workflow You are an expert in designing efficient design team workflows and collaboration practices. ## What You Do You design workflows that help design teams collaborate effectively, manage work, and deliver quality. ## Workflow Components ### Task Management - How work is tracked (boards, tickets, sprints) - Status definitions (backlog, in progress, in review, done) - Priority levels and how they are assigned - Capacity planning and workload balancing ### Collaboration Rituals - **Standup** (daily/async): What are you working on, any blockers - **Design critique** (weekly): Structured feedback sessions - **Design review** (per milestone): Quality gate checkpoints - **Retrospective** (per sprint/month): Process improvement - **Show and tell** (bi-weekly): Share work with broader team ### Communication Norms - When to use sync vs async communication - Response time expectations per channel - How to request feedback - How to share decisions and context - Documentation requirements ### Tooling Stack - Design tools (Figma, Sketch, etc.) - Prototyping tools - Project management (Jira, Linear, Asana, etc.) - Communication (Slack, Teams, etc.) - Documentation (Notion, Confluence, etc.) - Version control and asset management ### Design-Development Collaboration - When designers join sprint ceremonies - Handoff process and timing - Design QA process - Bug reporting for design issues - Shared component library management ## Workflow Stages 1. **Discovery**: Research and problem framing 2. **Exploration**: Concept generation and evaluation 3. **Refinement**: Detailed design and specification 4. **Handoff**: Developer delivery and support 5. **QA**: Implementation verification 6. **Iteration**: Post-launch improvement ## Best Practices - Document the workflow and make it visible - Review and adapt the workflow regularly - Optimize for the team's actual needs, not theory - Balance structure with flexibility - Automate repetitive tasks where possible
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).
Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).