CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dev-lifecycle

AI DevKit · Orchestrator for structured SDLC phase skills. Use when the user wants to run the full lifecycle or choose the next phase across requirements, design, planning, implementation, testing, and review.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 highly actionable, well-sequenced orchestration guide: exact CLI commands, explicit validation checkpoints with failure recovery, a phase routing table, and well-defined backward transitions. Its only weaknesses are minor redundancy (skill loads stated twice, lint commands repeated in three sections) rather than any structural problem.

DimensionReasoningScore

Conciseness

The body is imperative and free of concept explanations Claude already knows, but has trimmable duplication: skill-load instructions appear both as bullets ("Load `tdd` with your skill tool before writing code in phase 5") and again in the Required Skill Loads table, and "npx ai-devkit@latest lint --feature <name>" is repeated across Startup Validation, Resuming Work, and Rules. It is not 3 because there is no unnecessary explanation, and not 5 because that redundancy means not every token earns its place.

4 / 5

Actionability

Guidance is fully executable with copy-paste commands throughout ("npx ai-devkit@latest skill list --global", "npx ai-devkit@latest init -a -e claude --built-in --yes", "<skill-dir>/scripts/check-status.sh <feature-name>"), a concrete config resolution rule (".ai-devkit.json `paths.docs`, falling back to `docs/ai`"), and an exact output format ("Skills loaded: <skills>"). Even failure paths carry recovery commands, so there are no gaps versus anchor 4.

5 / 5

Workflow Clarity

The multi-phase process is clearly sequenced ("setup -> 1 -> 2 -> … -> 9") with explicit validation checkpoints ("Then rerun both lists", "Do not run a phase without its skill", "Do not claim completion without fresh verification evidence") and genuine feedback loops in Backward Transitions ("Review finds blocking issues: return to `dev-implementation` or `dev-testing`"). This matches the anchor-5 pattern of clear sequence, explicit validation, and error-recovery routing.

5 / 5

Progressive Disclosure

Structure is good: clear section headers, routing and load tables, and one real, well-signaled bundle reference resolved explicitly ("Resolve `<skill-dir>` as the directory containing this `SKILL.md`. Run `<skill-dir>/scripts/check-status.sh`") that is one level deep. It is not 5 because the supporting-skills bullet list and the Required Skill Loads table duplicate each other — a minor organization gap — and not 3 because references are clearly signaled and content placement is otherwise appropriate for an every-run orchestrator.

4 / 5

Total

18

/

20

Passed

Description

73%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.

A well-formed description with an explicit "Use when…" trigger clause, natural phase-related keywords, and a distinct orchestrator niche. Its main weakness is that the capability statement is a single abstract role ("Orchestrator") rather than a list of concrete actions, which limits specificity and completeness.

Suggestions

Replace the abstract "Orchestrator for structured SDLC phase skills" with 2-3 concrete actions, e.g. "Routes each SDLC phase (requirements, design, planning, implementation, testing, review) to its phase skill and validates required skills are installed".

Add natural trigger synonyms such as "software development lifecycle", "SDLC workflow", or "resume feature work" so users phrasing the need differently still match.

DimensionReasoningScore

Specificity

The description names its domain ("Orchestrator for structured SDLC phase skills") and two actions ("run the full lifecycle", "choose the next phase"), matching the domain-plus-1-2-concrete-actions anchor. It is not a 4 because the stated actions are coordination-level rather than several specific concrete operations, and not a 2 because the actions are specific to this skill rather than generic.

3 / 5

Completeness

Both parts are explicit: what ("Orchestrator for structured SDLC phase skills") and when ("Use when the user wants to run the full lifecycle or choose the next phase…"). It is below 5 because the "what" is a single abstract role statement rather than the multiple concrete actions in the anchor-5 example, and above 3 because the "when" clause is explicit with concrete trigger phrasing.

4 / 5

Trigger Term Quality

Natural phrases like "run the full lifecycle", "choose the next phase", and the six phase names ("requirements, design, planning, implementation, testing, and review") give good keyword coverage a user would plausibly say. It falls short of 5 because common synonyms such as "software development lifecycle", "SDLC workflow", or "start a new feature" are absent.

4 / 5

Distinctiveness Conflict Risk

The "AI DevKit" branding plus the orchestrator niche ("run the full lifecycle or choose the next phase") gives a clear trigger niche with minimal conflict risk — requests for a single phase map naturally to the phase skills, not this one. It is not a 4 because no meaningful overlap with a closely related skill's triggers is evident from the description alone.

5 / 5

Total

16

/

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

codeaholicguy/ai-devkit

Path

skills/dev-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.