Skills backend-development-feature-development
📦
backend-development-feature-development
Content revision r2 Safe
Orchestrate Complete Backend Feature Delivery
Complex backend features often fail when requirements, architecture, testing, and rollout work remain disconnected. This skill coordinates twelve delivery phases with defined outputs, controls, and handoffs.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "backend-development-feature-development" from https://skillstore.io/skills/sickn33-backend-development-feature-development.md and its manifest at https://skillstore.io/api/skills/sickn33-backend-development-feature-development/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "backend-development-feature-development". Plan a payment retry feature using TDD and a canary rollout.
Expected outcome:
- Requirements define retry eligibility, customer outcomes, acceptance criteria, and payment risk controls.
- Architecture covers retry scheduling, idempotency, event contracts, failure handling, and audit records.
- Testing includes unit, integration, end-to-end, performance, and payment security checks.
- Rollout starts with limited traffic and monitors recovery rate, duplicate charges, latency, and errors.
Using "backend-development-feature-development". Coordinate account deletion across identity, billing, and analytics services.
Expected outcome:
- The delivery plan assigns service ownership and defines deletion contracts, retention rules, and dependency order.
- Migration and testing stages verify authorization, data removal, legal retention, and failure recovery.
- Operational gates include audit evidence, monitoring, staged activation, and a tested rollback procedure.
Using "backend-development-feature-development". Prepare a feature-flag rollout for a new recommendation API.
Expected outcome:
- The rollout begins with internal users, then expands through measured traffic stages.
- Dashboards track latency, error rate, recommendation quality, feature usage, and business outcomes.
- Automatic stop conditions and flag disable procedures provide immediate recovery.
Security Audit
Safev5 • 8/14/2026 Open versioned report
The only static finding is a false positive because SKILL.md line 35 requires approvals and rollback plans before production changes. No evidence of reconnaissance, prompt injection, exfiltration, or malicious intent was found.
1
Files scanned
189
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-backend-development-feature-development/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-backend-development-feature-development?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-backend-development-feature-development?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-backend-development-feature-development/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-backend-development-feature-development.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). backend-development-feature-development security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-backend-development-feature-development/audits/5BibTeX citation
@techreport{sickn33-sickn33-backend-development-feature-development-2026,
author = {sickn33},
title = {backend-development-feature-development security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-backend-development-feature-development/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "backend-development-feature-development security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-08-14"
url: "https://skillstore.io/skills/sickn33-backend-development-feature-development/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-backend-development-feature-development:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
69
Community
91
Spec Compliance
What You Can Build
Plan a Cross-Service Feature
Turn a product request into requirements, architecture, ownership, dependencies, risks, and measurable delivery criteria.
Coordinate Technical Implementation
Align backend, frontend, and data work through shared contracts, staged outputs, and integrated testing.
Prepare a Controlled Rollout
Define deployment gates, feature flags, observability, rollback actions, and operational documentation before release.
Try These Prompts
Create a Feature Plan
Plan a medium backend feature for [feature]. Use TDD and feature flags. Define requirements, architecture, tests, rollout, monitoring, and rollback outputs.
Coordinate Multiple Services
Coordinate delivery of [feature] across [services]. Identify dependencies, API and data changes, ownership, security checks, acceptance criteria, and a canary deployment plan.
Design a Domain Workflow
Design a DDD workflow for [feature] in [domain]. Define bounded contexts, aggregates, contracts, migration stages, testing layers, observability, and rollback controls.
Orchestrate an Epic Rollout
Orchestrate an epic for [feature] across [teams and systems]. Include phased ownership, compliance gates, performance budgets, data migration, canary metrics, incident thresholds, and rollback decisions.
Best Practices
- Provide current architecture, owners, constraints, and measurable success criteria before starting discovery.
- Review each phase output before passing it to implementation or deployment agents.
- Validate migrations, feature flags, monitoring, and rollback procedures in staging before production approval.
Avoid
- Do not use the complete workflow for a small isolated fix.
- Do not deploy generated changes without environment-specific testing and human approval.
- Do not proceed when scope, permissions, safety boundaries, or success criteria remain unclear.
Frequently Asked Questions
What features fit this skill?
Use it for complex features spanning requirements, architecture, implementation, testing, deployment, monitoring, and documentation.
Which development methods are supported?
The workflow supports traditional delivery, TDD, BDD, and DDD.
Can it handle small bug fixes?
It can, but the full workflow adds unnecessary overhead. Use a focused specialist skill for small fixes.
Does it deploy directly to production?
No. Production changes require explicit approvals, validated rollback plans, and environment-specific checks.
Which rollout strategies are included?
It supports direct, canary, feature-flag, blue-green, and A/B test strategies.
What information should I provide?
Provide the feature scope, methodology, complexity, constraints, architecture context, success metrics, and preferred deployment strategy.