Team workflow

Skill Infrasity-Labs/dev-gtm-claude-skills/.claude/skills/team-workflow

Design team workflows covering task management, collaboration rituals, and tooling.From its SKILL.md

Install

npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill team-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.1 KB, 426 tokens by cl100k_base, as published. Nobody here has run it

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

Discovery: Research and problem framing
Exploration: Concept generation and evaluation
Refinement: Detailed design and specification
Handoff: Developer delivery and support
QA: Implementation verification
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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most automation workflows skills give in 426 tokens

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-07

Write conventional commit messagesin 36 of 745, across 35 files
Delete branches after mergein 30 of 745, across 21 files
Make atomic commitsin 25 of 745, across 15 files
Write minimal code to pass testsin 22 of 745, across 10 files
Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
Use try-catch for error handlingin 20 of 745, across 8 files
Run tests before committingin 20 of 745, across 12 files
Write tests before implementationin 20 of 745, across 8 files
Configure branch protection rulesin 19 of 745, across 5 files
Explain the why in commit messagesin 19 of 745, across 9 files
Refactor code while tests remain greenin 19 of 745, across 6 files
Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

document the workflow and make it visible
review and adapt the workflow regularly
optimize for the team's actual needs
balance structure with flexibility

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.