- Home
- Skills
- Catlog22
- Claude Code Workflow
- Team Skill Designer
team-skill-designer_skill
- TypeScript
1.3k
GitHub Stars
1
Bundled Files
3 weeks ago
Catalog Refreshed
2 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstart where the catalogue uses aiagentskills.
npx veilstart add skill catlog22/claude-code-workflow --skill team-skill-designer- SKILL.md13.0 KB
Overview
This skill generates a unified team skill package that routes role-specific execution from a single entry point. It collects team requirements, analyzes patterns, and outputs a complete skill folder with per-role execution files and shared infrastructure. The coordinator can spawn teammates by invoking the single skill with a role argument, enabling consistent multi-agent workflows.
How this skill works
The meta-skill runs a 5-phase pipeline: requirements collection, pattern analysis, skill package generation, integration verification, and validation. It produces a skill entry file that parses a --role argument, reads the matching role file from roles/{role}/, and executes that role's five-phase logic while reusing shared messaging and lifecycle infrastructure. Outputs include team-config.json, pattern analysis, integration and validation reports, and a preview of the generated skill package.
When to use it
- When you need one entry point that dispatches work to multiple team roles via a --role argument.
- When you want consistent shared infrastructure (message bus, task lifecycle) across roles.
- When generating multiple role files in a single batch to ensure coordination and unique task prefixes.
- When converting many separate command files into a single maintainable skill package.
- When you need verification and validation reports before delivering a team skill.
Best practices
- Always run the mandatory specification study step before generation to internalize patterns and quality standards.
- Collect all roles in one batch including coordinator, responsibilities, task prefixes, and capabilities.
- Keep per-role files self-contained: include toolbox, five-phase implementation, and message types in the role folder.
- Use templates for the skill router, role files, and command files to ensure consistent structure and error handling.
- Run integration verification to detect role name or task prefix conflicts before final delivery.
Example use cases
- Create a cross-functional team skill where planner, executor, tester, and reviewer are invoked through --role.
- Migrate five separate team command files into a single team skill to reduce duplication and centralize message bus logic.
- Auto-generate a preview package for stakeholder review that includes role files, commands, and validation reports.
- Generate coordinator logic that spawns role-specific agents and orchestrates task chains across the team.
- Enforce organization quality standards by embedding pattern specs and quality checks into the generation pipeline.
FAQ
Yes. Coordinator is generated by default and orchestrates team role spawning and pipeline flow.
What happens if a role name or task prefix conflicts?
The integration step flags conflicts and prompts for renaming or suggests alternative prefixes before finalizing.
Which artifacts are delivered for review before final placement?
A preview folder is produced with the skill entry file, role folders, commands, and team-config.json plus integration and validation reports.