👥
AutomationMarkdown

Team Workflow

by Owl-Listener

Team Workflow is an Automation skill for Claude Code, published by Owl-Listener in designer-skills.

2.1K stars335 forkson Owl-Listener/designer-skillsAdded 2026/08/18+2% in starsRepository updated 2026/08/08
agenticagentic-aiaiai-toolsclaude-codedesign-systemdesign-systemsprompt-engineeringskillsux-design
Install in seconds
Install Team Workflow
Copy Team Workflow into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/team-workflow ~/.claude/skills/team-workflow

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/Owl-Listener/designer-skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
design-ops/skills/team-workflow/SKILL.md in Owl-Listener/designer-skills
Installs to
~/.claude/skills/team-workflow
Collection
One of 25 skills cataloged from this repository
Category
Automation — 2226 skills

What Team Workflow does

Team Workflow designs a design team's operating rhythm covering task management, collaboration rituals, and tooling. Use it when a team's day-to-day cadence needs structure.

Team Workflow is cataloged under Automation on DirSkills. Team Workflow comes from a repository tagged agentic, agentic-ai, ai, ai-tools and claude-code.

Documentation

README

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

Frequently asked about Team Workflow

  • What else does Owl-Listener publish alongside Team Workflow?

    Team Workflow is one of 25 skills that DirSkills catalogs from Owl-Listener/designer-skills, the repository it ships in. Its siblings there include Accessibility Audit, Affinity Diagram and Card Sort Analysis. Each one is a separate skill with its own page in this directory, installs the same way Team Workflow does, and is maintained by Owl-Listener in that same repository. The rest of the collection is listed on the Owl-Listener/designer-skills page.

  • How does Team Workflow compare to other Automation skills?

    Team Workflow ranks #515 by stars among the 2226 Automation skills in this catalog. The most-starred ones next to it are Autonomous Loops, Autonomous Agent Harness and Automation Audit Ops. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Team Workflow against them. Open each page to compare what they document and how they install.

More from Owl-Listener/designer-skills

Team Workflow is one of 25 skills cataloged on DirSkills from Owl-Listener/designer-skills.

See all 25 skills →
♿
2026/08/18

Accessibility Audit

Accessibility Audit examines an existing interface against WCAG criteria, identifies barriers, and provides severity-rated findings with remediation steps. Use it when you have a design or build to assess now, not for planning future assistive-technology testing sessions.
Quality
2.1K335
🗂️
2026/08/18

Affinity Diagram

Affinity Diagram clusters qualitative data points into themes and insight statements. Use it when synthesising across multiple sessions or sources to create a structured hierarchy with supporting evidence.
Data
2.1K335
🗂️
2026/08/18

Card Sort Analysis

Card Sort Analysis analyzes open or closed card sort results into a proposed grouping and label set. Use it after running a sort study to inform navigation and content organization.
Frontend
2.1K335
🧩
2026/08/18

Component Spec

Component Spec specifies one component's props, states, variants, accessibility, and usage rules. Use when defining a library component.
Frontend
2.1K335
💬
2026/08/18

Design Critique

Design Critique facilitates structured team critique sessions, guiding framing, feedback rules, and actionable outcomes. Use it when running a session with people in the room to keep feedback constructive and aligned.
Frontend
2.1K335
🔍
2026/08/18

Design Debt Audit

Design Debt Audit inventories and prioritizes accumulated design inconsistencies across a product so teams can plan remediation. Use it before redesigns or when UI drift, accessibility gaps, and structural debt have built up.
Frontend
2.1K335