team-workflow
Connects non-technical product managers with development teams by classifying tasks and enforcing standardized workflows.
Install
mkdir -p .claude/skills/team-workflow && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17400" && unzip -o skill.zip -d .claude/skills/team-workflow && rm skill.zipInstalls to .claude/skills/team-workflow
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Orchestrates a structured software development workflow for product managers who are non-technical. Automatically classifies incoming messages as requirements, defects, or consultations, then guides the user through the appropriate process — requirements analysis, defect tracking, or technical consultation with plain-language explanations and options comparison. Use this skill whenever the user is collaborating on software development tasks like discussing features, reporting bugs, asking technical questions, or planning a project. If the user mentions requirements, features, bugs, defects, issues, technical questions, architecture, project setup, or wants to start developing something, use this skill to coordinate the workflow.Key capabilities
- →Classify incoming messages as requirements, defects, or consultations
- →Guide product managers through requirements analysis
- →Facilitate defect tracking with root cause analysis
- →Provide technical consultation with plain-language explanations
- →Ensure project adherence to `CLAUDE.md` specifications
- →Identify and process implicit defects discovered during consultations
How it works
The skill classifies incoming communications, then guides the product manager through a structured workflow for requirements analysis, defect tracking, or technical consultation, ensuring adherence to project rules and proper documentation.
Inputs & outputs
When to use team-workflow
- →Create a bug report from a user complaint
- →Analyze feasibility of a new feature request
- →Document technical consultation outcomes
- →Manage project lifecycle
About team-workflow
Classifies incoming communications into requirements, bugs, or questions. It forces defect analysis before development and ensures projects follow defined rules.
>
When not to use it
- →When skipping defect analysis before development
- →When merging multiple independent issues into a single defect file
- →When the user is not a non-technical product manager
Limitations
- →All analysis, reports, and communication with the product manager use Chinese
- →Code, commit messages, and technical identifiers use English
- →The skill absolutely prohibits proceeding to development before creating a defect document and completing root cause analysis
How it compares
This skill enforces a structured software development workflow for non-technical product managers, ensuring explicit classification, mandatory defect analysis, and consistent documentation, unlike informal communication channels.
Compared to similar skills
team-workflow side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| team-workflow (this skill) | 0 | 2mo | No flags | Advanced |
| team-routing | 1 | 8mo | Review | Intermediate |
| linear-ticket | 1 | 7mo | No flags | Intermediate |
| design-to-issues | 0 | 6mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
team-routing
WellApp-ai
Detect domain from context and find appropriate team member
linear-ticket
useautumn
Refine rough engineering thoughts into structured Linear tickets with GitHub permalinks
design-to-issues
cloverich
Creates a GitHub epic and child issues from a design document's implementation plan. Use when a design doc has a reviewed plan section ready to be converted into trackable work.
task-execution-engine
davila7
Execute implementation tasks from design documents using markdown checkboxes. Use when (1) implementing features from feature-design-assistant output, (2) resuming interrupted work, (3) batch executing tasks. Triggers on 'start implementation', 'run tasks', 'resume'.
agent-project-board-sync
ruvnet
Agent skill for project-board-sync - invoke with $agent-project-board-sync
agent-issue-tracker
ruvnet
Agent skill for issue-tracker - invoke with $agent-issue-tracker