Team Workflow
- 948 installs
- 1.9k repo stars
- Updated June 14, 2026
- owl-listener/designer-skills
Team Workflow is a design-operations skill that generates collaboration systems covering task management, rituals, and tooling for developers and design leads who need scalable cross-functional workflow documentation.
About
Team Workflow is an installable skill from owl-listener/designer-skills that designs efficient design-team workflows and collaboration practices. It documents task management with boards, tickets, sprints, status definitions (backlog, in progress, in review, done), priority levels, and capacity planning. Collaboration rituals include daily or async standups, design critiques, and structured review handoffs. Developers and design leads reach for Team Workflow when formalizing how a design group tracks work, runs critiques, and balances workload across contributors. The skill scales guidance from solo contributors to small cross-functional groups.
- Designs full task management systems including boards, status definitions, priority rules and capacity planning
- Defines 5 core collaboration rituals: daily standup, weekly design critique, milestone design review, retrospective, and
- Establishes communication norms for sync vs async, response times, feedback requests and documentation standards
- Recommends integrated tooling stack across design, project management, communication and version control
- Specifies designer-developer handoff process, timing and quality gates
Team Workflow by the numbers
- 948 all-time installs (skills.sh)
- +41 installs in the week ending Jul 29, 2026 (Skillselion tracking)
- Ranked #498 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/designer-skills --skill team-workflowAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 948 |
|---|---|
| repo stars | ★ 1.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | June 14, 2026 |
| Repository | owl-listener/designer-skills ↗ |
How do you structure a design team workflow?
Generate complete team collaboration systems that scale from one person to small cross-functional groups.
Who is it for?
Developers or design leads formalizing how a design function tracks tickets, runs critiques, and coordinates delivery across contributors.
Skip if: Teams seeking automated CI/CD pipeline design or code-review policies instead of design-ops collaboration rituals.
When should I use this skill?
A developer asks to design design-team task management, standups, critiques, or collaboration tooling practices.
What you get
Workflow document covering task boards, status definitions, priority rules, capacity planning, and collaboration ritual schedules.
- team workflow specification
- ritual and status-definition guide
Files
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
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kHow it compares
Choose Team Workflow for design-ops ritual and board design; pick engineering PM skills when the primary artifact is sprint planning for code delivery.
FAQ
What workflow components does Team Workflow cover?
Team Workflow covers task management (boards, tickets, sprints, statuses), collaboration rituals such as standups and design critiques, and capacity planning with priority rules for design teams.
Does Team Workflow support small teams?
Team Workflow scales from one-person design contributors to small cross-functional groups, defining status lanes like backlog, in progress, in review, and done.
Is Team Workflow safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.