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.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/backend-development-feature-development/SKILL.md

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced orchestration workflow with concrete Task-tool prompts for every step. Its main weaknesses are absent inter-phase validation gates and a monolithic single-file structure with some prose padding.

Suggestions

Add explicit validation checkpoints between phases (e.g., 'Confirm requirements doc is approved before starting architecture') since the workflow drives toward production deployment.

Remove the 'Extended thinking' prose block and collapse the redundant per-step 'Context:' lines to tighten token efficiency.

Move the detailed per-step prompt templates and configuration catalogs into reference files (e.g., phases.md, options.md) and link to them one level deep from SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly actionable prompts, but the 'Extended thinking' prose paragraph and the repeated 'Context:' lines on every step are explanatory padding that could be trimmed.	2 / 3
Actionability	Each of the 12 steps gives a concrete Task-tool invocation with an explicit subagent_type and a copy-paste prompt template, providing specific executable guidance.	3 / 3
Workflow Clarity	Four phases and 12 numbered steps are clearly sequenced with cross-step context references, but there are no explicit validation checkpoints between phases for a workflow that includes production deployment, capping clarity at 2.	2 / 3
Progressive Disclosure	The body is well-sectioned but is a monolithic single file over 180 lines with no bundle references; the detailed per-step prompts and configuration catalogs that could live in separate files are inline.	2 / 3
	Total	9 / 12 Passed

Description

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.

A concise, third-person description that satisfies the what-and-when requirement with an explicit trigger clause. It is somewhat held back by abstract, single-action phrasing rather than enumerating concrete capabilities.

Suggestions

Enumerate 2-3 concrete capabilities (e.g., 'design APIs, implement services, write tests, configure rollout') instead of one composite 'orchestrate' verb to lift specificity.

Add more natural user-facing trigger phrases (e.g., 'building a new backend feature', 'rolling out a multi-service change') alongside the abstract coordination language.

Sharpen distinctiveness by signaling the multi-phase/cross-service scope explicitly so it does not collide with single-task backend skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('backend feature development') and a single high-level composite action ('Orchestrate end-to-end... from requirements to deployment'), but does not list multiple discrete concrete actions like the score-3 anchor requires.	2 / 3
Completeness	Clearly answers both 'what' (orchestrate end-to-end backend feature development from requirements to deployment) and 'when' via an explicit 'Use when coordinating multi-phase feature delivery...' trigger clause.	3 / 3
Trigger Term Quality	Relevant terms appear ('backend feature development', 'coordinating multi-phase feature delivery across teams and services') but they lean corporate/abstract and miss common natural variations a user would actually say.	2 / 3
Distinctiveness Conflict Risk	The end-to-end multi-phase cross-team niche is somewhat specific, but 'feature development' is broad and could overlap with general backend-dev or project-coordination skills.	2 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/backend-development-feature-development/SKILL.md
Commit: a3068b7

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.