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.

2.22x

Quality

52%

Does it follow best practices?

Impact

89%

2.22x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/backend-development-feature-development/SKILL.md

Quality

Content

42%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 skill lays out a thorough, well-sequenced multi-phase orchestration with concrete subagent assignments, but it is verbose, relies on templated rather than fully executable prompts, and inlines everything instead of offloading detail to reference files. Destructive deployment and migration steps also lack explicit validation checkpoints.

Suggestions

Add explicit validation gates between phases (e.g. 'Only proceed to Phase 2 when the requirements doc is approved') and before production rollout to satisfy the destructive-operation feedback-loop requirement.

Move the repetitive twelve-phase agent scaffolding and the configuration parameter tables into reference files (e.g. phases.md, config.md) and link to them from a leaner SKILL.md overview.

Replace bracketed template placeholders with concrete, fill-in instructions or example prompts so the guidance is copy-paste-ready rather than pseudocode-like.

Dimension	Reasoning	Score
Conciseness	The 175-line body repeats near-identical phase scaffolding twelve times and pads with a long Extended Thinking paragraph restating intent Claude could infer, making it noticeably verbose with several padded sections.	2 / 5
Actionability	Each phase gives a concrete subagent_type and a prompt template with placeholders, but the prompts are templates with bracketed context ('[include business analysis from step 1]') rather than fully executable, copy-paste-ready instructions, leaving key details implicit.	3 / 5
Workflow Clarity	Phases are clearly numbered and sequenced and the Rollback Strategy gives ordered steps, but destructive/production operations (deployment, migrations, feature flags) lack explicit validation checkpoints before proceeding, which caps workflow clarity at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	Content is organized into clear sections, but everything is inlined into SKILL.md with no references or bundle files to offload the large phase-by-phase scaffolding and configuration tables; structure exists but content that could be separate is inline.	3 / 5
	Total	11 / 20 Passed

Description

62%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 cleanly answers both what the skill does and when to use it in third person, but its actions remain abstract and it lacks the natural, varied trigger terms a user would speak. It is distinct from single-task skills yet could sharpen its trigger vocabulary.

Suggestions

Add concrete action verbs and specifics, e.g. 'plans architecture, coordinates implementation, runs security validation, and drives staged rollouts'.

Broaden trigger terms with natural user phrases such as 'feature delivery', 'rollout', 'cross-service feature', or 'backend feature from spec to prod'.

Tighten the 'when' clause with concrete trigger contexts (e.g. multi-service changes needing deployment and monitoring) to push completeness to 5.

Dimension	Reasoning	Score
Specificity	Names the domain ('backend feature development from requirements to deployment') and the orchestration action, but the action is high-level and abstract rather than a list of concrete actions, matching the anchor for one-to-two concrete actions with gaps.	3 / 5
Completeness	It states a clear 'what' (orchestrate end-to-end backend feature development) and an explicit 'when' ('Use when coordinating multi-phase feature delivery across teams and services'), though the 'when' could be more specific about trigger contexts.	4 / 5
Trigger Term Quality	It includes 'multi-phase feature delivery across teams and services' but lacks the natural short phrases a user would actually say (e.g., 'feature delivery', 'rollout'), missing common variations and synonyms.	3 / 5
Distinctiveness Conflict Risk	The phrase 'coordinating multi-phase feature delivery across teams and services' carves a fairly distinct niche that is unlikely to collide with single-task skills, with only minor overlap risk against general project-management skills.	4 / 5
	Total	14 / 20 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/backend-development-feature-development/SKILL.md
Commit: 57c135b

Reviewed: 5 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.