backend-development-feature-development
Orchestrate end-to-end backend feature development from requirements to deployment. Use when coordinating multi-phase feature delivery across teams and services.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill backend-development-feature-developmentOverall
score
70%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%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 has good structural completeness with explicit 'what' and 'when' clauses, which is its primary strength. However, it relies on abstract orchestration language rather than concrete actions, and the trigger terms could be more comprehensive to capture natural user queries about backend development workflows.
Suggestions
Add specific concrete actions like 'Creates API specifications, coordinates database migrations, manages service dependencies, tracks deployment pipelines'
Expand trigger terms to include natural variations: 'backend API', 'microservices', 'service integration', 'release coordination', 'feature rollout'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('backend feature development') and mentions phases ('requirements to deployment'), but lacks concrete actions. Terms like 'orchestrate' and 'coordinating' are somewhat vague without specifying what actual tasks are performed. | 2 / 3 |
Completeness | Clearly answers both what ('Orchestrate end-to-end backend feature development from requirements to deployment') and when ('Use when coordinating multi-phase feature delivery across teams and services') with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms ('backend', 'feature development', 'deployment', 'multi-phase'), but missing common variations users might say like 'API development', 'microservices', 'sprint planning', 'release management', or 'feature rollout'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to backend orchestration, but could overlap with project management skills, deployment skills, or general development coordination skills. The scope of 'multi-phase feature delivery' is broad enough to potentially conflict. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
63%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive orchestration framework for feature development with excellent workflow structure and clear phase sequencing. However, it suffers from verbosity (especially the extended thinking block and repetitive prompt templates) and lacks concrete executable examples. The content would benefit from being split across multiple files and including more specific, actionable guidance rather than abstract prompt templates.
Suggestions
Remove the extended thinking block and condense the introductory content - Claude doesn't need the rationale explained
Add concrete example outputs for at least one phase (e.g., a sample requirements document structure or API specification format)
Split detailed phase instructions and configuration options into separate reference files (e.g., PHASES.md, CONFIG.md) with SKILL.md as a concise overview
Replace abstract prompt templates with more specific, executable guidance including example inputs and expected output schemas
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some unnecessary verbosity, particularly the extended thinking block and repetitive prompt templates. The configuration options and phase descriptions could be more condensed. | 2 / 3 |
Actionability | Provides structured guidance with specific subagent types and prompts, but lacks concrete executable code examples. The prompts are templates rather than copy-paste ready commands, and expected outputs are described abstractly rather than with concrete schemas or examples. | 2 / 3 |
Workflow Clarity | Excellent multi-phase workflow with clear sequencing across 12 steps organized into 4 phases. Includes explicit validation checkpoints (security validation, performance optimization), rollback strategy with specific timeframes, and clear dependencies between phases. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and phases, but everything is inline in a single monolithic document. Complex configuration options, detailed phase instructions, and rollback strategies could be split into separate reference files for better navigation. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 13 / 16 Passed | |
- 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.