Saltar al contenido
Marketplace

team-workflow

de owl-listener

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`.

Resumen

SKILL.mdLeída en 9a6930c

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

Archivos 1 archivo

Instálala a mano

Deska ejecuta esto por ti, para cada agente que elijas. Para ejecutarlo tú en una terminal:

npx skills add owl-listener/designer-skills --skill team-workflow

Más de owl-listener

  • presentation-deckowl-listenerStructure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use `case-study`; for the written argument use `design-rationale`.2,800 instalaciones en skills.sh0
  • typography-scaleowl-listenerCreate a modular type scale with size, weight, and line-height relationships. Use when establishing typographic structure. For line length only use `readable-measure`; for judging type on an existing screen use `critique-typography` (visual-critique).2,300 instalaciones en skills.sh0
  • visual-hierarchyowl-listenerEstablish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order. Use when composing new work. For judging an existing screen, use `critique-visual-hierarchy` (visual-critique).2,300 instalaciones en skills.sh0
  • color-systemowl-listenerBuild a product colour system — tonal scales, semantic roles, and contrast compliance. Use when defining or rebuilding colour from scratch. For dark-mode adaptation use `dark-mode-design`; for chart palettes use `data-visualization`; for multi-brand token architecture use `theming-system` (design-systems).2,200 instalaciones en skills.sh0
  • dark-mode-designowl-listenerAdapt an existing palette to dark mode — surface elevation, contrast rebalancing, and desaturation rules. Use when you already have a light palette to translate. For building the base palette first, use `color-system`.2,200 instalaciones en skills.sh0
Todas las skills de owl-listener