Skip to main content
affpapa.org
RU EN
skill CX Codex

team-workflow — Claude Code skill: what it does, how to install

Designs an operating cadence for design teams, covering task tracking, regular rituals, and developer handoff. Helpful when day-to-day design collaboration lacks structure.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add Owl-Listener/designer-skills --skill team-workflow -a claude-code
Open on GitHub

What team-workflow does

This skill sets up a design team's operating rhythm across task management, team rituals, communication norms, tool selection, and developer collaboration. It structures work around six sequential phases: discovery, exploration, refinement, developer handoff, visual QA, and post-launch iteration.

The instructions guide the agent to define concrete tracking states, feedback rules, and meeting cadences such as weekly critiques or milestone reviews. If you need a time-boxed framework for a fast sprint, this skill intentionally steps aside: use design-sprint-plan instead.

What it helps with

  • Define task statuses, priorities, and boards in Jira or Linear
  • Schedule design critique and milestone review rituals
  • Standardize developer handoff and visual QA procedures
  • Set expectations for sync and async communication channels

Example prompts for the agent

  • Set up a weekly design critique format and review checklist for our team
  • Define our Figma-to-developer handoff process and design QA steps
  • Draft task statuses, priority levels, and async communication norms for Jira

How to install team-workflow

1Skills CLI (Vercel)

npx skills add Owl-Listener/designer-skills --skill team-workflow -a claude-code

2Manually: put the files in place

~/.claude/skills/team-workflow/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/team-workflow/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about team-workflow

How do I install team-workflow in Claude Code?

Run npx skills add Owl-Listener/designer-skills --skill team-workflow -a claude-code. The skill file will be stored in ~/.claude/skills/team-workflow/SKILL.md.

When should I use team-workflow instead of design-sprint-plan?

Use team-workflow to establish ongoing operational habits, tool stacks, and daily collaboration routines. If you need to run a time-boxed sprint, use design-sprint-plan instead.

Which workflow stages does this skill cover?

It covers six stages: research and problem framing, concept exploration, detailed design refinement, developer handoff, visual QA, and post-launch iteration.

Source text

SKILL.md · MIT 
---
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

© Owl-Listener · MIT · Owl-Listener/designer-skills

Similar skills

Everything for Design →
release-notes phuryn Creates user-facing release notes from tickets, PRDs, and changelogs. Use it when announcing updates or summarising shipped work. CX Codex +1 2,900installs log davila7 Writes a finished task's report into your tracker or notes: time spent, status, commits. Useful when the coding happens in Claude but the record lives in Linear or Obsidian. 351installs track-findings official OpenAI Routes verified Codex Security findings into Linear, Jira, GitHub issues, and draft advisories. It prevents duplicate tickets and previews payloads before filing tasks. CX Codex GP ChatGPT 26installs leanspec codervisor Teaches the agent to run development through specs: capture intent first, write code second. Works with markdown, GitHub Issues, Azure DevOps and Jira. CX Codex +1 1,000installs project-session-manager Yeachan-Heo Automates creation of separate git worktrees for each task, PR, or feature, with optional tmux session orchestration. Work on multiple branches in parallel without conflicts. CX Codex +1 866installs resume-intelligence rahulbsw This skill turns career evidence from LinkedIn, GitHub, Jira and Confluence into resumes, cover letters and interview material. CX Codex +1 805installs

From the same set111

click-test-plan Turns a findability question into a test plan: where users click first and whether they locate items in your navigation. Useful when a design is ready but untested. CX Codex +1 2,000installs design-sprint-plan Plans structured design sprints to move from a challenge statement to a tested prototype in days. Ideal when you need to compress discovery work into a single week. CX Codex +1 2,000installs design-system-adoption Builds an adoption strategy and enablement materials when teams are bypassing an existing design system. It helps plan education, migration support and measurement. CX Codex +1 2,000installs summarize-interview Turns a single interview transcript into themes, quotes and follow-up tasks, in a format you can hand to stakeholders. CX Codex +1 2,000installs opportunity-framework Turns a pile of possible improvements into a ranked roadmap using impact-effort and RICE. Handy when ideas outnumber capacity. CX Codex +1 2,000installs design-review-process A skill that sets four review gates for design work, from concept to implementation QA. Useful when things ship without a consistent review step. CX Codex +1 2,000installs north-star-vision Articulates a long-horizon product vision across 1-year, 2-3 year, and 5+ year horizons. Useful when a team lacks a clear strategic direction. CX Codex +1 2,000installs test-scenario Writes usability test scenarios with realistic context, success criteria and facilitation notes. Useful once the study is planned and the tasks are still missing. CX Codex +1 2,000installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor