x-team

Use when the user asks for parallel team-style execution of multiple features in one project — orchestrates a team lead + N dev workers, one feature per worktree, each gated on x-qa E2E tests, with blocker escalation to human via SendMessage. Hard requires `plugin.omc` (TeamCreate/SendMessage primitives) and `.x-skills/x-qa/profile.json` (E2E gate).

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, highly actionable orchestration playbook with concrete payloads and an explicit phased workflow including validation and feedback loops. Its only real weakness is a broken reference to a missing gotchas.md file.

Suggestions

Add the missing gotchas.md bundle file referenced in the Bootstrap section (step 3) and the Gotchas section, or remove the references if the content belongs inline.

Consider moving the lengthy bootstrap/isolation-prerequisite checks (steps 4-5) into a references file so the overview stays scannable while keeping the hard-refusal behavior explicit.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence — it uses TeamCreate/SendMessage/Task primitives directly with no explanation of what they are, and every section earns its place with concrete code blocks rather than padded prose.	3 / 3
Actionability	Provides copy-paste-ready JSON payloads for TeamCreate, TaskCreate, TaskUpdate, and SendMessage, plus concrete script invocations (e.g. `scripts/feature-map-init.sh --team-slug <slug> ...`) and exact slug formats.	3 / 3
Workflow Clarity	A clear 8-phase sequence with explicit validation checkpoints and feedback loops — the MANDATORY bootstrap, "If any worktree provisioning fails: abort the wave, run TeamDelete," idempotence guards on feature_done, and the 30s shutdown timeout with explicit error handling.	3 / 3
Progressive Disclosure	The body is a well-signaled overview pointing one level deep to real references (decomposition-rules.md, monitor-loop.md, worker-preamble.md), but `gotchas.md` is referenced twice (bootstrap step 3 and the Gotchas section) yet does not exist as a bundle file, leaving a broken navigation pointer.	2 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: third-person voice, concise, concrete actions, an explicit "Use when..." trigger, and a distinct niche with hard prerequisites stated. It hits the top anchor on every dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "orchestrates a team lead + N dev workers, one feature per worktree, each gated on x-qa E2E tests, with blocker escalation to human via SendMessage" — plus explicit hard requirements, matching the score-3 anchor.	3 / 3
Completeness	Explicitly answers both what it does (team lead + N workers, worktree-per-feature, E2E gate, blocker escalation) and when to use it ("Use when the user asks for parallel team-style execution"), satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	Opens with the natural trigger phrase "Use when the user asks for parallel team-style execution of multiple features in one project," using terms a user would actually say (parallel, multiple features, team-style execution).	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (parallel team orchestration with worktree isolation and x-qa gating) with distinct triggers unlikely to fire for other skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: quangtran88/x-skills
Commit: 6381b15

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.