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.
74
Quality
64%
Does it follow best practices?
Impact
89%
2.22xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/backend-development-feature-development/SKILL.mdQuality
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 main strength. However, it relies on abstract orchestration language rather than concrete actions, and the trigger terms could be more comprehensive to capture natural user language variations.
Suggestions
Add specific concrete actions like 'Creates API specifications, coordinates database migrations, manages service integrations, tracks deployment pipelines'
Expand trigger terms to include natural variations: 'new feature', 'API development', 'microservices', 'release coordination', 'cross-team development'
| 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 misses common variations users might say like 'API development', 'microservices', 'release', 'sprint planning', or 'feature rollout'. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on 'backend' and 'multi-phase feature delivery across teams' provides some distinction, but could overlap with project management skills, deployment skills, or general development coordination skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive orchestration skill with excellent workflow structure and clear phase sequencing. Its main weaknesses are verbosity (especially the extended thinking block) and lack of concrete executable examples - the prompts are templates rather than actionable code. The skill would benefit from trimming explanatory content and either providing more concrete examples or splitting detailed phase content into referenced files.
Suggestions
Remove the extended thinking block - it explains orchestration concepts Claude already understands and adds ~100 tokens of no value
Add concrete example outputs for at least one phase (e.g., sample requirements document structure, sample API contract) to make the skill more actionable
Consider splitting the 12-step phase details into a separate PHASES.md file, keeping SKILL.md as a concise overview with the workflow summary and configuration options
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some unnecessary verbosity, particularly the extended thinking block which explains obvious orchestration concepts Claude already understands. The configuration options and phase descriptions are reasonably lean but could be tightened. | 2 / 3 |
Actionability | Provides structured prompts for each subagent and expected outputs, but lacks concrete executable code examples. The instructions are more template-like than copy-paste ready, with placeholders like '$ARGUMENTS' and '[include X from step Y]' requiring interpretation. | 2 / 3 |
Workflow Clarity | Excellent multi-phase workflow with clear sequencing across 12 steps organized into 4 phases. Includes explicit validation checkpoints (security validation, test coverage thresholds), rollback strategy with time estimates, and success criteria that serve as verification gates. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but the skill is monolithic with no references to external files for detailed content. The extensive configuration options and 12-step workflow could benefit from splitting into separate reference documents. | 2 / 3 |
Total | 9 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
9c177eb
- 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.