team-workflow

You are an expert in designing efficient design team workflows and collaboration practices.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "team-workflow" with this command: npx skills add owl-listener/designer-skills/owl-listener-designer-skills-team-workflow

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

  • Discovery: Research and problem framing

  • Exploration: Concept generation and evaluation

  • Refinement: Detailed design and specification

  • Handoff: Developer delivery and support

  • QA: Implementation verification

  • 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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

responsive-design

No summary provided by upstream source.

Repository SourceNeeds Review
General

summarize-interview

No summary provided by upstream source.

Repository SourceNeeds Review
General

component-spec

No summary provided by upstream source.

Repository SourceNeeds Review
General

user-flow-diagram

No summary provided by upstream source.

Repository SourceNeeds Review