team-lifecycle-v4
Full lifecycle team skill with clean architecture. SKILL.md is a universal router — all roles read it. Beat model is coordinator-only. Structure is roles/ + specs/ + templates/. Triggers on "team lifecycle v4".
56
46%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.codex/skills/team-lifecycle-v4/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description reads like internal implementation notes rather than a functional skill description. It fails to communicate what the skill does in concrete terms, uses jargon instead of natural user language, and relies on an artificial trigger phrase rather than describing real usage scenarios. It would be nearly impossible for Claude to correctly select this skill based on a user's natural request.
Suggestions
Replace jargon with concrete actions: describe what 'full lifecycle team skill' actually does (e.g., 'Manages team projects from planning through delivery, assigns roles, tracks progress, and generates status reports').
Add a 'Use when...' clause with natural trigger terms users would actually say, such as 'team management', 'project planning', 'role assignment', 'sprint coordination', or 'status tracking'.
Remove implementation details like 'SKILL.md is a universal router', 'roles/ + specs/ + templates/' structure, and 'beat model is coordinator-only' — these are internal architecture notes, not user-facing description content.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract, jargon-heavy language like 'full lifecycle team skill with clean architecture', 'universal router', and 'coordinator-only' without describing any concrete actions the skill performs. No specific capabilities are listed. | 1 / 3 |
Completeness | The 'what' is extremely vague — it never explains what the skill actually does. The 'when' is limited to the artificial trigger phrase 'team lifecycle v4' with no real-world usage context. Both dimensions are very weak. | 1 / 3 |
Trigger Term Quality | The only explicit trigger is 'team lifecycle v4', which is not a natural phrase any user would say. Terms like 'universal router', 'beat model', and 'clean architecture' are internal jargon, not user-facing keywords. | 1 / 3 |
Distinctiveness Conflict Risk | The highly specific but artificial trigger 'team lifecycle v4' would unlikely conflict with other skills, but the vague domain description ('full lifecycle team skill') could overlap with any team management or project coordination skill. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured orchestration skill that serves as an effective router for a complex multi-agent system. Its greatest strengths are actionability (concrete API call templates, exact file paths, step-by-step wave execution) and workflow clarity (explicit validation checkpoints, error handling, supervisor lifecycle). Minor conciseness improvements are possible by deduplicating some patterns and trimming the model selection guide, but overall the content density is justified by the complexity of the orchestration task.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly dense and information-rich, but includes some redundancy (e.g., the supervisor spawn/wake/shutdown pattern is explained twice across sections, and the delegation lock table restates what could be a simpler rule). The ASCII architecture diagram and model selection guide add bulk but are mostly justified for a complex orchestration skill. Some tightening is possible. | 2 / 3 |
Actionability | Highly actionable with concrete spawn_agent/followup_task/close_agent call templates, specific JSON-like API invocations, exact file paths, named agent targeting examples, and a complete delegation lock table with explicit ALLOWED/BLOCKED verdicts. The wave execution engine is a step-by-step executable algorithm. | 3 / 3 |
Workflow Clarity | The Wave Execution Engine provides a clear 10-step sequence with explicit validation checkpoints (skip failed deps, handle block verdicts, timeout cascades). Error handling table covers failure modes with resolutions. The supervisor lifecycle (spawn -> wake -> shutdown) is clearly sequenced with feedback loops for checkpoint block/override/revise/abort. | 3 / 3 |
Progressive Disclosure | SKILL.md acts as a clean router/overview pointing to one-level-deep references: roles/<name>/role.md for each of 8 roles, specs/pipelines.md, specs/quality-gates.md, specs/knowledge-transfer.md. The Role Registry table provides clear navigation with linked paths. Content is appropriately split between the router (orchestration logic) and referenced files (domain-specific instructions). | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- catlog22/Claude-Code-Workflow
- Commit
227244f
- Reviewed
Table of Contents
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.