CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lifecycle

Use when a project spans multiple phases with review gates between them — architecture then implementation then integration, for example

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/lifecycle/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

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 well-sequenced, highly actionable orchestration pattern with genuine review-gate feedback loops, held back by dangling references to files that are absent from the bundle (reference/dependency-waves.md, reference/phase-gates.md, and worker prompts living in another skill) and by repeated re-explanation of the gate convention.

Suggestions

Add the referenced files (reference/dependency-waves.md, reference/phase-gates.md) to the bundle, or remove the pointers and keep the inline explanations as the sole source.

Inline or bundle the architect/reviewer prompts instead of deferring to another skill's ./workers/architect-prompt.md, so the dispatch steps are copy-paste ready.

Consolidate the [Gate] convention — currently explained in Step 2, the Phase Gates section, and the State section — into a single authoritative section.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no basic concepts are explained, and the verdict table and code blocks carry real information. However, the [Gate] convention is explained three times ("Gate tasks block subsequent phases until the reviewer approves", the Phase Gates section "Subject starts with `[Gate]`; Blocked by all tasks in the current phase", and the State section "Gates: `[Gate]` prefix tasks"), and the Example re-illustrates the same wiring, matching 'Efficient; minor instances of over-explanation that could be trimmed'. Not a 5 for that redundancy; not a 3 because nothing explains what Claude already knows.

4 / 5

Actionability

Concrete, executable guidance dominates: exact task subjects ("TaskCreate: \"[Phase 1: Foundation] Set up project structure\"\"), explicit dependency wiring ("addBlockedBy: [gate-task-id]"), and a verdict table mapping each verdict to an action. It is not a 5 because the dispatch prompts are placeholders, not copy-paste ready ("prompt: [Use ./workers/architect-prompt.md from orchestrating-work]", "[Use reviewer-prompt.md with phase acceptance criteria]"), deferring the actual prompts to another skill's files. Not a 3 because the commands that are given are real and specific, not pseudocode.

4 / 5

Workflow Clarity

A clear five-step sequence (plan → create tasks → execute waves → review gate → advance/complete) with explicit validation checkpoints: gates block phase transitions and require reviewer verdicts, and error recovery is a genuine feedback loop — "On NEEDS_CHANGES, create new tasks for the fixes, add them as blockers to the gate, and re-run the phase" and REJECT sends work back to the architect plan. This matches 'Clear sequence with explicit validation steps; feedback loops for error recovery' for a batch orchestration operation.

5 / 5

Progressive Disclosure

The in-body structure is good and references are clearly signaled and one level deep ("See `reference/dependency-waves.md` for the algorithm", "See `reference/phase-gates.md` for the gate pattern"), but scored against the actual bundle these files do not exist — there is no references/ directory, and the referenced worker prompts also live in a separate skill. The navigation points to dead ends, matching 'Some structure but could be better organized'. Not a 4 or 5 because well-signaled references must resolve to real files; not a 2 because the body itself is well-sectioned and doesn't inline what should be separate.

3 / 5

Total

16

/

20

Passed

Description

40%Weight 40%Scale 1-5

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 a strong, explicit 'when' clause with a concrete niche, but it is missing the 'what' entirely — a reader cannot tell from the description what the skill does. Adding a short statement of the skill's actions would raise both completeness and specificity.

Suggestions

State what the skill does before the trigger, e.g., 'Orchestrates multi-phase project execution with architect-led planning and reviewer-approved gates between phases.'

Add natural trigger synonyms users would actually say — 'stages', 'milestones', 'sequential phases', 'review before moving to the next phase'.

Distinguish the skill from the closely related orchestrating-work/`/orchestrate` skill in the description (e.g., 'use this instead of single-pass orchestration when phases need sign-off').

DimensionReasoningScore

Specificity

The description names the domain ("project spans multiple phases with review gates between them — architecture then implementation then integration") but never states what the skill actually does (orchestrate execution, plan with an architect, gate transitions). It describes properties of the target project, not actions the skill performs, matching 'Names the domain but actions are minimal or generic.' It is not a 3 because no concrete skill action (e.g., 'orchestrates', 'plans', 'reviews') is stated anywhere; not a 1 because the domain language is concrete rather than pure abstraction.

2 / 5

Completeness

The 'when' is explicit and well-formed ("Use when a project spans multiple phases with review gates between them"), but the 'what' is entirely absent — the description never says the skill orchestrates phase execution or reviewer-approved transitions. This matches the anchor 'only "when" is present without "what"'. It is not a 3 because that anchor requires a clear 'what' with a weak 'when' — the inverse of this description; it is not a 1 because the 'when' clause is concrete and specific.

2 / 5

Trigger Term Quality

Relevant keywords are present ("project", "multiple phases", "review gates", "architecture then implementation then integration") but common variations users would naturally say — "stages", "milestones", "sequential", "multi-step", "gated" — are missing, and "review gates" is skill jargon more than user vocabulary. This matches 'Some relevant keywords but missing common variations or synonyms'; it is not a 4 because a user describing a staged project with sign-offs would likely use terms the description does not cover.

3 / 5

Distinctiveness Conflict Risk

The trigger niche (multi-phase projects with review gates between phases) is fairly distinct and unlikely to fire for generic single-pass tasks, matching 'Mostly distinct; minor overlap risk with closely related skills'. It is not a 5 because the skill wraps and closely relates to `orchestrating-work`, and the description gives no cue for choosing between them — a plain 'orchestrate this project' request could plausibly match either.

4 / 5

Total

11

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

tslateman/bach

Path

skills/lifecycle/SKILL.md

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.