360 Secure SkillHub
360 安全技能中心

team-workflow

提供团队工作流设计框架,覆盖任务管理、协作仪式、沟通规范、工具选型及设计到开发协作,并列出工作流阶段与最佳实践;以文本指导为主,不含具体模板或自动化执行。

Owl-Listener
热度 23.45
最近更新 2026-10-19 04:18:29
分类:协作依赖:纯提示词应用场景:任务管理 / 工作流 / 日程安排

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add owl-listener/designer-skills/team-workflow
Metadata
name
team-workflow
description
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use `design-sprint-plan`.

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